This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Findings Log

This page indexes durable technical discoveries. Detailed findings use Template — Finding. Active work and discussion belong in Forgejo Issues; evidence too large or sensitive for the wiki belongs in the preservation store with an artifact ID.

Confirmed constraints from current manager modules

ID	System	Finding	Confidence	Evidence
FND-001	Project Meteor	Server targets FFXIV 1.23b client version 2012.09.19.0001; A Realm Reborn clients are incompatible.	High	Current Meteor manifest and tests; needs independent baseline test link.
FND-002	TrinityCore 3.3.5	Required client is WoW 3.3.5a build 12340.	High	Current TrinityCore module and upstream compatibility expectation; add baseline test.
FND-003	Sapphire	Safe start requires the configured server data version to match the SqPack snapshot’s adjacent ffxivgame.ver.	High	Current Sapphire scripts/tests.
FND-004	Project Meteor	staticactors.bin is a client-derived legacy asset and can be absent after a source-only installation.	High	Current Meteor scripts/manifest.
FND-005	Sapphire	Existing retail FFXIV user data can contribute to launch crashes; a sanitized working profile is required for controlled testing.	Medium	Current module warning; needs isolated reproduction record.
FND-006	Aura Kingdom	Historical release sources contain gaps because some original Google Drive links are no longer available.	High	Current preservation profile inventory; attach availability manifest.
FND-007	Aura Kingdom	Legacy release set mixes i386/x86-64 binaries and currently relies on QEMU user-mode on the target Linux host.	Medium	Current experimental module; needs per-binary compatibility results.
FND-008	TrinityCore master	Client compatibility must be tied to a pinned server commit; “current retail” is not a durable version.	High	Moving-branch behavior and module warning.

These entries document constraints represented by the code, not proof that a complete P3 baseline has been restored. Link independent test evidence as it becomes available.

Open questions

ID	System	Question	Next experiment	Issue
Q-001	LandSandBoat	Which exact server commits have been verified with which client data snapshots?	Create first pinned baseline and capture client-data manifest.	#9
Q-002	Project Meteor	Which maps/flows require each client-derived script asset?	Controlled run with one variable changed at a time.	#10
Q-003	Sapphire	Which preserved server revisions map to which exact ffxivgame.ver snapshots?	Build compatibility matrix from pinned revisions and tests.	#11
Q-004	Aura Kingdom	Which release profiles reach the first stable handshake/login milestone under QEMU?	Per-release isolated smoke test.	#12

Entry rules

• Assign the next FND-NNN or Q-NNN identifier.
• State whether the entry is observed, inferred, or confirmed.
• Link exact artifact IDs, hashes, tool versions, experiment log, issue, and any patch.
• Never paste secrets, restricted binaries, or unredacted captures into the wiki.
• Supersede findings instead of silently rewriting history when conclusions change.