util: gen_ce_info_and_maps supports CN/KO/TC

[Souma-Sumire]

I dont know why the definitions for the KO version are incorrect, so I have hardcoded them for now.

• xivapi: The xivapi/SaintCoinach repo is still using outdated definitions, but the actual API responses are correct.
• thewakingsands (cn/tc): They have merged xivapi/SaintCoinach/pull/217, so there are no issues here.

[xiashtra]

SaintCoinach is basically abandoned and shouldn't be relied on anymore.

[Souma-Sumire]

SaintCoinach is basically abandoned and shouldn't be relied on anymore.圣科纳奇基本上已经被遗弃，不再值得依赖。

OK, then I’m lost. I have no idea how to get CSV files using Lumina (that's the one to use now, right?).

[xiashtra]

The upstream maintainers' intent is for everyone to either move to using XIVAPI calls, or write their own extractor based on EXDSchema. Lumina gives you a C# library for doing that. It's not the best answer, but they really do not want to support/maintain SaintCoinach (or by extension, Godbert) anymore.

With China now on release parity with global, and Korea catching up for 7.5, they should eventually all use the same schema, so maybe it's possible to have users from China and Korea work with XIVAPI to get the game data from those regions added.

[xiashtra]

If you have experience with Rust, you can take a look at XIVData Oxidizer and see if it can be modified to work with the non-global regions. This tool is meant as mostly a replacement for the rawexd functionality from SaintCoinach.

[Souma-Sumire]

With China now on release parity with global, 和 Korea catching up for 7.5, they should eventually all use the same schema, so maybe it's possible to have users from China and Korea work with XIVAPI to get the game data from those regions added.

I hope this becomes a reality someday.

If you have experience with Rust, you can take a look at XIVData Oxidizer and see if it can be modified to work with the non-global regions. This tool is meant as mostly a replacement for the rawexd functionality from SaintCoinach.

Thanks, I'll check it out! This looks like it could be really useful.

---

Back to the PR: What should we do now?

• Request a definition file update from @Ra-Workspace.
• Migrate to a different repository utilizing the correct definitions.
• Wait for XIVAPI to integrate the TC/KO/CN servers.
• Keep it as-is for now.
• Other

[xiashtra]

Back to the PR: What should we do now?

• Request a definition file update from @Ra-Workspace.

This is probably the most straightforward solution in the short-term.

• Migrate to a different repository utilizing the correct definitions.

If you know of another repository that is suitable and maintained, this could also be an option.

• Wait for XIVAPI to integrate the TC/KO/CN servers.

This is not a solution for now. We have no idea if and when XIVAPI might integrate non-global data; it would require someone from the non-global (CN/KO/TC) regions to approach and work with them as a starter.

• Keep it as-is for now.

We are already integrating non-global zone data, so I see no reason not to also include non-global CE data.

• Other

[Bing-su]

The raphael-rs project uses the augenfrosch API, which might be a temporary workaround.

async fn fetch_and_parse<T: SheetData>(lang: &str, schema_override: Option<&str>) -> Vec<T> {
    const XIV_API: &str = "https://v2.xivapi.com/api";
    const BOILMASTER_CN: &str = "https://boilmaster-chs.augenfrosch.dev/api";
    const BOILMASTER_KR: &str = "https://boilmaster-ko.augenfrosch.dev/api";
    const BOILMASTER_TW: &str = "https://boilmaster-tc.augenfrosch.dev/api";

https://github.com/KonaeAkira/raphael-rs/blob/5d8169ccb89ee2b4d739994512ce7c8a3aa32ada/raphael-data-updater/src/main.rs#L7

[Ra-Workspace]

• Request a definition file update from @Ra-Workspace.

Since there are other projects currently referencing my repository, I have uploaded the updates to a separate branch using the XIVData Oxidizer to avoid any breaking changes.

I’ve also updated the definitions on the main branch as well.

[xiashtra]

The raphael-rs project uses the augenfrosch API, which might be a temporary workaround.

async fn fetch_and_parse<T: SheetData>(lang: &str, schema_override: Option<&str>) -> Vec<T> {
    const XIV_API: &str = "https://v2.xivapi.com/api";
    const BOILMASTER_CN: &str = "https://boilmaster-chs.augenfrosch.dev/api";
    const BOILMASTER_KR: &str = "https://boilmaster-ko.augenfrosch.dev/api";
    const BOILMASTER_TW: &str = "https://boilmaster-tc.augenfrosch.dev/api";

https://github.com/KonaeAkira/raphael-rs/blob/5d8169ccb89ee2b4d739994512ce7c8a3aa32ada/raphael-data-updater/src/main.rs#L7

If these API forks are well maintained and updated in a timely manner, they would allow us to use a XIVAPI-style interface for all regions.

[xiashtra]

This looks fine for now, though I did notice in testing that our error handling for when XIVAPI is unavailable is not very robust and could use improvements.