PLAYERS / CONTRIBUTORS / DEVELOPERS

Build with us.

One shared universe. A community building it together.

Arkline is an early-access Rust space sandbox and engine. This guide describes what is available today and where community work fits.

Join the official world

Use the browser client or a matching native client, select Production, and create a pilot or resume with your saved credentials. Test is a separate world with separate pilots and may be reset. Keep your pilot credentials private; clearing browser data can lose your saved resume key.

The browser is a convenient starting point. Native speech, SSH-based ship-computer connections and independent ledger auditing require the native client. Read the controls and platform notes supplied with the release.

How the official infrastructure works

P.Industries operates the official servers on its private cloud and uses Genestack Console to manage that infrastructure. The server is authoritative for movement, inventory and economic transactions.

Community participation means feedback, testing, documentation and reviewed code contributions. It does not automatically grant production access or deployment rights. Hosting our own infrastructure is an operational choice, not proof of large-scale capacity. Load, recovery and security validation remain ongoing work.

Economic audit exports support independent consistency checks. They are not proof of operator honesty, and gameplay credits are not financial assets.

DEVELOPER SECTION

Local development & server downloads

We recommend self-hosting first for testing, experiments and local development. It gives you a place to try ideas before proposing a pull request to the official Arkline repository. P.Industries focuses on one shared official universe, shaped by its players and contributors.

Matching source · SHA-256 checksums · Release license

1. Download the server archive for your platform, the matching source archive and SHA-256 manifest from the release page. Verify the archive before installing.
2. Read START-HERE.txt and the included operator documentation. Start with a local world and keep database files and credentials outside the extracted package.
3. For public connections, configure the WebSocket listener behind HTTPS/WSS. Raw TCP is intended for local or private connections; do not expose bearer credentials over plaintext Internet transport.
4. Test backup and restore before inviting players. Upgrade from a known source revision, preserve save files, and review compatibility notes.

Your server has its own pilots, saves and economy. It is not automatically federated with the official world. Rewarded nodes, shared cross-server economies and automatic community hosting payouts are not implemented.

Independent community servers and forks are welcome too. We are curious to see the worlds, tools and ideas you create, and would love you to share them with the community. Contributing improvements back is encouraged, not a condition of hosting; applicable license obligations still apply.

Contribute changes

First-party Arkline code is licensed AGPL-3.0-only. Use the matching source archive to inspect or build the release, retain notices, and read LICENSE and TRADEMARKS.md. Dependencies and bundled third-party materials retain their own licenses.

The Arkline engine is public at PIndustries/arkline-engine. Open a focused issue or submit a pull request for review. Contributions can include code, original art, documentation and reproducible test reports. Contributing does not grant administrative access to the official world.

1. Start with a focused problem and a reproducible example. Discuss changes affecting the economy, ownership or protocol before a large implementation.
2. Build and run a local world without production credentials. Follow the source archive's CONTRIBUTING.md and run formatting, Clippy and workspace tests.
3. Include regression coverage for persistence, balances, access control and reconnect behavior where relevant. Keep server rules authoritative and ledger verification independent.
4. Describe the resulting behavior, tests performed and known limitations. Do not include player saves, bearer tokens, credentials or proprietary assets.

Maintainers review contributions before merging or deploying them. For an initial private security report, contact [email protected]. Include the affected version and a concise description, not credentials or player databases. Do not post exploit details in public community channels.