-
Notifications
You must be signed in to change notification settings - Fork 287
Roundflow doc #641
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
ThatGuyUSA
wants to merge
12
commits into
space-wizards:master
Choose a base branch
from
ThatGuyUSA:roundflow-doc
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Roundflow doc #641
Changes from 3 commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
a9fcd66
umm ummm yea....
ThatGuyUSA f85228b
newline removal
ThatGuyUSA 745cb3f
Addressed, I think!
ThatGuyUSA 8cd0290
Update roundflow.md
ThatGuyUSA 2435892
well rested and written
ThatGuyUSA 9da1617
well rested and written
ThatGuyUSA f9d458e
no more designers...
ThatGuyUSA b6fa05e
remove fluff, some punctuation
ThatGuyUSA d422778
made summary good
ThatGuyUSA 686525f
forgot about abrupt endings
ThatGuyUSA 58b3b70
gamemodes isn't real
ThatGuyUSA f1a1cfd
a bit more syntax corrections and punctutation
ThatGuyUSA File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,38 @@ | ||
| # Round flow | ||
|
|
||
| | Designers | Coders | Implemented | GitHub Links | | ||
| |----------------------------------|---------------------------------|-------------|---------------| | ||
| | ThatGuyUSA, Princess-Cheeseballs | All of our lovely contributors. | ✖️ No | [Wizard's Den](https://github.com/space-wizards/space-station-14) | | ||
|
|
||
| ## Narrative structure | ||
|
|
||
| All gamemodes, like any good story, should follow a narrative structure and have story beats. | ||
|
|
||
| For the crew all gamemodes start with a simple theme; You are working your ordinary shift on a space station, but something has gone terribly wrong. | ||
| On the other hand are those who work against the crew; their stories start vastly different. But in some way, shape or form, end up being the foil to the station. In one shift the player might be one of 5 elite operatives sent to detonate a nuclear fission explosive aboard the station. In another, they could be patient zero of a zombie outbreak hellbent on spreading zombification at any cost. Despite both scenarios leading to the station's destruction, the atmosphere and energy of a round feel vastly different. Making for memorable and unique situations that are fun to recount and be told about! | ||
|
|
||
| A laying out of the gamemodes story structure gives it direction and context to those participating in its development. | ||
|
|
||
| ## Emergent story telling | ||
|
|
||
| The beats of the story for each gamemode should come naturally to the players as a result of mechanics associated with the gamemode. | ||
|
|
||
| Those who are in charge of driving the story forwards should arrive to the same conclusions by being nudged a desired direction through the use of gamemode specific mechanics. Whether it is done through flavor text, skills, afflictions, or equipment. The behavior should come as a byproduct of the mechanics. As an initial infected, your goal is to convert as many crew into zombies as possible, but you can only stave off the infection for so long before it begins to convert you. So before becoming a mindless shambling zombie you may feel inclined to bring as many people down with you as possible. Alternatively you may sabotage vital station infrastructure that plays a key role in curing the zombie virus. As a corporate rival sent to assassinate the Captain, should you take the quick and dirty method utilizing heavy-duty explosives and risk outing yourself? Or should you take a stealthier approach that takes more planning, at the benefit of keeping yourself inconspicuous to make escaping easier? | ||
|
|
||
| ## Every story has its end | ||
|
|
||
| All gamemodes should have a clear end goal and conclusion. | ||
|
|
||
| There should be no ambiguity for what players should be working towards, a clear and concise goal will keep players thinking how to approach and eventually accomplish said goal. Not all rounds end as gracefully as one another, in most cases it is from the stations defenses being overwhelmed. In some extreme scenarios the antagonists need not intervene before the stations untimely collapse. The inverse also applies, an antagonist can be done in early by another antagonist before they get a chance to accomplish anything. Which is particularly brutal for stealth focused / infiltration antagonists, as they might vanish without a trace of them having even existed. | ||
|
ThatGuyUSA marked this conversation as resolved.
Outdated
|
||
|
|
||
| ## Freedom, as a means to an end | ||
|
|
||
| Those driving the round have freedom to do what they please, ultimately for the sake of reaching their conclusion / goal. | ||
|
|
||
| Freedom of approach is encouraged and often makes for memorable round experiences. However, those in charge of the conflict must be given pressures to pursue accomplishing their goals. Even the most interesting conflicts can overstay their welcome. | ||
|
|
||
| ## Time is of the essence | ||
|
|
||
| Never have both sides be in a position where waiting is the best or only move. | ||
|
|
||
| Those accomplishing their goals or looking to resolve conflict should never find themselves waiting as the best path forward to ending conflict. Inaction should be discouraged or punished whether it be done through imposed time limits or resource management. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.