Alex Rønne Petersen

We would probably use this: https://github.com/ikpil/DotRecast

Informally assigning @Foglio1024 since he's doing some investigation into topology stuff in the leaked official server files.

Following the reverse engineering of the geometry format used by the leaked official servers, I've converted that data to a custom format that's much more compact (4 GB -> 970...

The mapper tool can now take retail geometry/path data and convert it to our custom (and much more compact) formats. The next step will be to integrate path data generation...

https://github.com/dotnet/runtime/issues/90281

These sheets are unreferenced by the client: ```text AbuseLetterList AccountData AgitData AgitVillagerData AIData AIEditorHtmlHelp AiTemplate AoiStackInfo AutoWorldProfile AutoWorldProfileResult BehaviorRecorder BuffSkillList CacheAnimSoundData CacheNpcShapeData CrestCostData DailyPlayGuideQuest DailyQuest DamageMeterAbnormal DarkRiftNpcData Data DungeonRank DungeonRankCompensation...

Some of these string sheets *might* be removable. Further analysis needed. ```text StrSheet_AccessoryTransform StrSheet_Countdown StrSheet_DungeonHardModePreset StrSheet_DungeonMatchingMail StrSheet_DungeonRank StrSheet_EnchantPopup StrSheet_Event StrSheet_FloatingCastle StrSheet_GuildCompetition StrSheet_GuildMail StrSheet_HelpData StrSheet_ItemFilterInfo StrSheet_LordAchievement StrSheet_NotifyMessage StrSheet_Parcel StrSheet_RewardMessage StrSheet_TrialAccount StrSheet_VIPMail...

Assigning @Roukanken42 to make an educated guess as to whether the string sheets in https://github.com/tera-arise/arise/issues/50#issuecomment-1685253360 might be removable just based on the string contents.

Manually checking every node and attribute in the retail data center: https://gist.github.com/alexrp/462c593ce4b4c3fc8a8f20976c06c532

Another example would seem to be `GitHub.Models.ReleaseAsset.Id` which, due to being a value type, has to be used as `(int)asset.Id!`.