Mission Statement

Or: How The Server Should Be Ideally

The goal of Sojourn Station is to provide a fun SS13 environment for our playerbase that doesn't sacrifice fun mechanics or an individual's potential for great accomplishments for the sake of forcing interaction and/or roleplay between players, but whose rules and mechanics still encourage doing so, and will keep the players feeling excited, engaged, and invested, since their actions in-game can shape the future of the ongoing canon.

The intended playerbase:

• Is interested in or willing to tolerate ERP on the server
• Is interested in playing SS13 as a game
• Will not always eschew casual RP in general; Roleplaying as a loner or hermit is fine, and can be a fun challenge.
• Enjoys participating in the setting
• Will contribute to the ongoing in-game day

The environment and setting should be kept suitable for this intended playerbase, and as such, there is a set of criteria that the environment should be kept towards:

• Being “high roleplay.” Most interactions within the walls of the colony are fully roleplayed, and there are rules regarding escalation to mechanical combat.
• Has natural roleplay opportunities offered by the features of our particular server.
• Allows roleplay and mechanics to coexist, with rules designed not to sacrifice the fun of either.
• Allows an individual to accomplish large tasks even in isolation without much roleplaying. Some things may be difficult and/or time-consuming to do alone, but not impossible with good preparation and a good understanding of the game mechanics.
• Will eventually use a combination of persistence mechanics, staff-curated events, and a robust exploration system to ensure that there is always something new to be done/explored and that significant accomplishments/progression by the players can have a lasting impact on the game even when the game server must be restarted.

What we intend to do that is unique to our server is to preserve the progression, both in breakthroughs and in disasters, of the players between server restarts. Even if Nadezhda were partially or mostly destroyed and needed to be evacuated, mechanics will ensure that the players can build their way back up to the technological sophistication they began with from more primitive technology through a combination of a massive crafting system from stone-age level of tech all the way up to space-age, and salvaging the remains of the colony to reduce some of the workload of rebuilding. For example, setting up full-stocked outposts in the wilderness, while not required, can work to the advantage of the colonists, as such locations can serve as a valuable contingency plan in the event of a disaster.

This does not mean that every single bit of damage or the like that happens to the colony will be saved across restarts. It means that in certain situations, say the colony falls under attack or during an event such as a blob the crew collectively decides to bomb the damn thing or to evacuate, that this can be made persistent to give the colonists something big to work towards going forward, such as retaking the colony, building a new one, or finishing the some of the repairs following a successful defense that were not completed during the off-screen time. Player constructions outside the colony and additions by the engineers to the colony will generally be saved, to allow progression and reduce the amount of monotonous work that has to be repeated after a restart. As a robust buffer against griefing nothing will be automatically saved.