karashiiro / ffxivopcodes

Opcode repository for FFXIV.

FFXIVOpcodes

Opcode/constant repository for FFXIV. Builds JSON stores of opcodes from enums.

The current opcodes file and constants file can be retrieved either from the GitHub CDN directly, or (for China) through jsDelivr (opcodes constants).

Version convention

By default, we follow the game versions (4.1, 5.57, etc.), but for hotfixes we increment the game version by 0.001.

For example, a hotfix on 5.57 would change our version to 5.571, and another would change it to 5.572.

ffxivopcodes's Issues

KR 6.4 Hot fix

There was a hot fix on November 2nd, 2023.

Could you get the new opcodes for that?

There are some opcode definitions missing here vs Sapphire. Is it intended because they are not used?

If not I'll PR an update adding missing ones from Sapphire which are still being maintained.

[Proposal] Include client version in json files

When using Ipcs.h files from sapphire, we're used to the // updated 5.4 comments and such that are giving us an important information to know when a given packet has been updated.

Having this inside the JSON files would allow for potentiel librarires or end products to read it and know if all their required opcodes are ready and updated, meaning that this could lead to proper opcodes updates without having to publish a new client update (in the case of TC).

My proposal is to have an "updated" field, parsed from ipcs.h, that contains the last version the opcode (or constant, btw) has been updated for.

This plus a proper naming convention for patches would make things easier to maintain for everyone.

My current naming convention is to follow game version (5.4 for instance) and add 0.001 when a hotfix is released which makes it easy to compare versions using semver.