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.

FFXIV 1.x — Project Meteor

Field	Value
Internal ID	ffxiv-meteor
Upstream	Ioncannon/project-meteor-server
Preserved mirror	MMO-Preservation/preservation-project-meteor, 01f76bce7af55bc4f12bc4fbd6af47dea5609989
Default branch	develop
Manager module	gsm-mod-meteor
Support status	Supported legacy module
Required client	FFXIV 1.23b, version 2012.09.19.0001
Database	MariaDB/MySQL-compatible; default ffxiv_server
Runtime	Legacy .NET executables under Mono plus PHP login service and tmux
Default installation	/opt/gsm/servers/meteor
Preservation level	P1 source captured and bundled; client/runtime unverified
Owner	Ryuu
Last documentation review	2026-07-16
Runtime verification	Not completed — #3

Preserve together

• Complete Bitbucket Git mirror and dated offline bundle.
• FFXIV 1.23b client snapshot metadata for exactly 2012.09.19.0001.
• Required client-derived staticactors.bin and related script asset provenance, retained under the appropriate access class.
• Mono/.NET compiler/runtime, legacy dependencies, PHP version/configuration, MariaDB schema, and web-login content.
• Server configuration, launcher servers.xml example, port map, and tested public-address behavior.

Compatibility

Project Meteor targets the original FFXIV 1.x client. A Realm Reborn clients are incompatible. Do not relabel another 1.x build as compatible without a recorded test.

The manager’s current reminder configures Seventh Umbral Launcher with the server address and HTTP login URL. Store launcher version and configuration as derived client metadata; never embed real credentials.

Runtime components

• Lobby Server
• World Server
• Map Server
• PHP login endpoint
• MariaDB/MySQL-compatible database
• Optional/required map script assets depending on the tested path

The manager starts legacy binaries through Mono in a tmux session and keeps Meteor stopped after installation until explicitly started.

Known constraints and risks

• staticactors.bin comes from the matching client and may be missing; absence can block map behavior.
• Legacy Mono, PHP, compiler, and database dependencies can disappear from modern distributions.
• Meteor and Sapphire can conflict over ports; safe-start checks must remain part of the baseline.
• A moving develop branch is not a preserved revision. Pin a full commit ID.
• Old web/login code must not be exposed publicly without a security review.

Baseline verification

1. Restore the pinned mirror, toolchain, PHP login content, and database schema.
2. Build all three legacy server executables under the declared environment.
3. Apply database/public-address configuration from templates.
4. Supply client-derived assets from a verified restricted snapshot where required.
5. Start the PHP login endpoint and lobby/world/map processes on an isolated network.
6. Launch the exact 1.23b client with the recorded launcher and reach the agreed login/world milestone.
7. Record port ownership, logs, checksums, and compatibility result.

Open preservation work

• Capture the Bitbucket repository, issues/docs where permitted, and all build dependencies.
• Establish a verified clean 2012.09.19.0001 client manifest.
• Determine and document the exact provenance and necessity of each client-derived script asset.
• Create an isolated, reproducible legacy build/runtime image.
• Complete an offline restore test.

Live tracking

• Legacy dependency and artifact preservation: #3
• Client-derived asset investigation: #10
• Mirror and bundle verification: #2