DFAssist icon indicating copy to clipboard operation
DFAssist copied to clipboard

Fixed files json updated to 4.2

Open easly1989 opened this issue 8 years ago • 4 comments

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

easly1989 avatar Feb 09 '18 11:02 easly1989

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.

Bwin4L avatar Feb 09 '18 20:02 Bwin4L

I used the ID I've found on the ffxiv data mining github..

Gonna check them again and update if needed

Il 09 feb 2018 9:04 PM, "Bwin4L" [email protected] ha scritto:

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 https://github.com/devunt/DFAssist/issues/4 on my and my friends' clients. We are all using English and we're all on Aether. The IDs might have become specific to datacenters.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/devunt/DFAssist/issues/104#issuecomment-364548476, or mute the thread https://github.com/notifications/unsubscribe-auth/ADuqOmfXwHfZZskSrnc-alufkdL1r_buks5tTKSygaJpZM4R_xEd .

easly1989 avatar Feb 10 '18 00:02 easly1989

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 (:

easly1989 avatar Feb 14 '18 08:02 easly1989

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

Jaehyuk-Lee avatar Mar 22 '18 09:03 Jaehyuk-Lee