
Cost of Continuance is recruiting revshare collaborators for a PC-first systems game built around persistent consequences, altered world states, and player decisions that carry forward.
The game tracks prior player action across later content. Damage, trust, access, routes, environments, quest states, and available outcomes can change based on what happened earlier. We are looking for collaborators who can work within that kind of production structure across design, art, writing, implementation, testing, audio, and documentation.
Current project state:
Team of 15 collaborators across development, art, writing, production, and composition
Developed under Irrevia Studios
Project reference:
https://irreviastudios.com
Current roles we are open to:
3D Modelers
Level Designers
Narrative Writers
Environment Artists
Animators
Unity Developers
Technical Artists
UI / UX Designers
QA Testers
Production support
Documentation support
Other game-development roles may also apply if there is a clear fit with current production needs.
Priority gaps right now include modelers, level designers, and writers.
Modelers can contribute game-ready assets such as props, structures, environmental pieces, machines, creatures, or character-related models.
Level designers can contribute spaces built around traversal, encounter flow, quest routing, readable layouts, and decision points that affect later state.
Writers can contribute scenes, dialogue, quest states, VN-style sections, and consequence-aware story material that remains coherent after the player has changed the world state.
For other roles, the useful application is direct: what you do, what part of the pipeline you can support, and what level of weekly availability is realistic.
Compensation:
This is revshare only.
There is no salary or contract pay attached to this post. Revshare terms will be discussed clearly before onboarding. Revenue is not guaranteed.
To apply, send a DM with:
Your role
What you can contribute
Weekly availability
Portfolio or samples, if available
Prior game or interactive work, if available
Any constraints that may affect fit or availability
A portfolio is preferred, but not required. If you do not have one, send a short description of what you can make, what you have worked on before, and any small example you can share, such as a screenshot, test piece, document, asset, prototype, or playable sample.