Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed files json updated to 4.2 #104

Open
easly1989 opened this issue Feb 9, 2018 · 4 comments
Open

Fixed files json updated to 4.2 #104

easly1989 opened this issue Feb 9, 2018 · 4 comments

Comments

@easly1989
Copy link

easly1989 commented Feb 9, 2018

Hello,
Just wanted to point out that, on my repository i've fixed and updated all the jsons in data to be compatible with Final Fantasy XIV patch 4.2

https://github.com/easly1989/ffxiv_act_dfassist/tree/master/data

You may include those updated files to your project as well.

Just one thing.

For all the language i've used the English names for the dungeons (and comments).
If you have/can find the source for the correct translation feel free to modify them.

best regards,
Carlo

@Bwin4L
Copy link

Bwin4L commented Feb 9, 2018

Hello,
Thanks!

Unfortunately, the IDs seem to be completely different on my computer (tested with several friends too) for some reason.
Sastasha, for example, is instance ID 4 on me and my friends' clients.
We are all using English and we're all on Aether.
The IDs might have become specific to datacenters.

@easly1989
Copy link
Author

easly1989 commented Feb 10, 2018 via email

@easly1989
Copy link
Author

A quick update:
Also for me Sastasha had ID 4, so I think the ID are still "global" and not related to datacenters!

The thing I've noticed is that, the event I capture while "Matching" is still using the old ID (infact i can see the right instance in the log window), while the "Matched" and "Begin Matching" events receive the updated version.

I've tried searching for another byte on the data we receive, but without results.

After work i'll try to get as much instance IDs as I can "manually" xD... but this is not the right approach imho;

If you find a better/reliable source for this datas, please keep me updated,
Thank you (:

@Jaehyuk-Lee
Copy link
Contributor

Jaehyuk-Lee commented Mar 22, 2018

Found out those new IDs are used at the moment when duty "matched". Old IDs and New IDs are both used now.
I think SE changed some network codes after patch 4.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants