Game Development

6300 readers

18 users here now

Welcome to the game development community! This is a place to talk about and post anything related to the field of game development.

Community Wiki

founded 3 years ago

MODERATORS

Ategon@programming.dev

LiquidityC@programming.dev

Frank@programming.dev

[Self-Promotion] A survival game should survive its creator (www.youtube.com)

submitted 6 days ago* (last edited 6 days ago) by fallalis@programming.dev to c/gamedev@programming.dev

2 comments fedilink hide all child comments

ALIS asks two survival questions: can the player survive the world, and can the world survive its creator?

The first is gameplay. The second shapes the project: a real place whose geography can be checked; public source and GPG-verifiable release checksums; modular boundaries; a pact against predatory mechanics; and a direction toward community hosting and transferable stewardship.

That is the direction, not a fake launch claim. The public release today is an early single-player Windows prototype. Community-hosted servers and open governance are still long-term work.

The 58-second trailer shows the world. The play page shows what exists and can be inspected now: https://fall.is/play/

For people who build games or infrastructure: what actually keeps a game world alive when its original maintainer, storefront, or master server disappears?

top 2 comments

sorted by: hot top controversial new old

[–] Drbreen@sh.itjust.works 4 points 6 days ago (1 children)

I honestly don't know what you're trying to communicate.

[–] fallalis@programming.dev 1 points 3 days ago

@Drbreen@sh.itjust.works — thank you. Your comment is fair, and I think you are right: I led with motivation and abstractions before explaining what ALIS actually is and why it might be relevant to developers here.

ALIS is an early single-player UE5 survival project. Its public repository can also serve as an Unreal architecture reference: developers can inspect and adapt its modular plugin boundaries, JSON-to-DataAsset pipeline, implemented inventory, vitals and loading systems, plus its build, test and release tooling.

The public tree is intended for code, documentation, review and contribution—not as an asset-complete game checkout. Contributions to code, tests, documentation and public text data are welcome in the ALIS repository.

To help me correct the message: what concrete context did you expect first from a post like this in /c/gamedev—a concise explanation of the playable build, or a focused technical breakdown with code and trade-offs, such as the plugin boundaries, data pipeline or one implemented gameplay system? If neither, what would have made the post useful to you?