-
Couldn't load subscription status.
- Fork 22
Matthew Danielson - Final Project Proposal #7
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
Mnd2126
wants to merge
2
commits into
CPRO-Session1:master
Choose a base branch
from
Mnd2126:master
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
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,99 @@ | ||
| Matthew Danielson | ||
| Final Project Notes and Info/Project Proposal | ||
|
|
||
| ------------------ | ||
| Project Proposal | | ||
| ------------------ | ||
|
|
||
|
|
||
|
|
||
| Overview: | ||
|
|
||
| My project will be a simulation that allows for users to customize their apocalypse scenario, | ||
| and survive in it, designed around the user making strategic decisions to manage resources and a | ||
| group, while dealing with scenarios that result from both their choices and random elements. This | ||
| apocalypse is of a more fallout-esque nature rather than any other(i.e. surviving after a nuclear | ||
| fallout). | ||
|
|
||
| In terms of customization, a user will be able to set the following when commencing a game: | ||
| - Population of affected area | ||
| Main industry of the region | ||
| Alters effectivity and odds of success of certain actions | ||
|
|
||
| - Size of group | ||
| Talents and abilities of individual group members* | ||
| Name individual group members | ||
|
|
||
| - Additonally, they can change how far into the apocalypse the game begins | ||
| This affects... | ||
| Availability of supply items/Successfullness of scavenging | ||
| Availability of power | ||
| General dangerousness of the area | ||
| * Look at game mechanics in order to understand how this affects gameplay | ||
|
|
||
| Within the game itself, the player will be working on a day by day basis; each day, they | ||
| will be presented with what they have. For instance, for food, they will be shown how many days | ||
| they can feed their population with their current food. Below is an example of this graphic. | ||
|
|
||
| Remaining Supplies | ||
| ------------------ | ||
|
|
||
| Food: x days | ||
| Fuel: z units | ||
| Weapons: a units | ||
| Electronics: y units | ||
| Construction Supplies: b units | ||
|
|
||
| Note that there are no specific items - considering the time span given to work on this project, | ||
| that would be too time consuming. However, to take weapons for instance, if there are enough weapons | ||
| for everyone in the group, then in any potiential combat scenarios, they will have a higher chance | ||
| to win the diceroll that determines the winner. Fuel determines whether the group can use a vehicle, | ||
| which decreases the odds of being attacked and increases general safety. Construction allows for | ||
| improving the safety of the group's base, decreasing odds of being attacked, and making it easier | ||
| to defend. | ||
|
|
||
| On a daily basis, the player can choose to do 2 of the following actions: | ||
|
|
||
| - Fortify the base(construction): Decreases the odds of being attacked and gives the group an advantage in | ||
| future assaults. | ||
|
|
||
| - Scavenge: The player will have the choice of what they want to look for, | ||
| within the five supply groups. This is risker than most of the other actions. | ||
| [] | ||
| - "Farming": This is general category in which food production and preparation falls. While | ||
| this is not really farming, it is attempting to focus on getting more food and is not as risky as scavenging. | ||
|
|
||
| - Tinker: This allows for growth of the group members. This, depending on the successfullness, can give your group members | ||
| permanent upgrades. Additionally, it can allow for weapon fabrication or car repairs. This element is entirely random - otherwise | ||
| it would be too strong - except when the car is broken. Then, all tinkering actions are dedicating to attempting to repair it. | ||
|
|
||
| - Assault: This is BY FAR the riskiest action in the game. Group members will almost certainly die. That being said, | ||
| it is definitely the strongest way to get a lot of resources. | ||
|
|
||
|
|
||
| Game Mechanics & Daily Events: | ||
|
|
||
| An important element of this game/simulation will be random, daily events. One such mechanic will | ||
| be the base assault, which can be safeguarded against by improving the group's base. Other daily events | ||
| include dice rolls on being assaulted while scavenging, varying success rates for actions - especially | ||
| when said action is done many times in succession. As time progresses, each turn the user takes being counted | ||
| as one day, loot becomes scarcer and attacks become more frequent. Even if players play exceedingly well, unlucky dice rolls | ||
| and daily events can ruin even a seemingly stable situation. Members of the player's party will die, and new party members are | ||
| probably among the rarest encounters. There are no win conditions for this game, as the point is to see how long you can survive. To quote | ||
| Project Zomboid's developers, "These are the end times. This is how you died." | ||
|
|
||
| In terms of game mechanics, there are 4 skills: Scavenging, Combat, Construction and Tinkering. | ||
| At party creation, each character is allowed to have a speciality in any one of these 4. This will give a bonus to that character. | ||
| These stats are used, in the case of combat, to roll against enemies, whose strength increases as the game progresses. If every member has a weapon, | ||
| then the bonus from weapons is maximized; if not enough weapons are present, advantage is given on a percentage-based system. For all other skills, | ||
| a success multipler is given. These are calculated by adding together all the current group member's deviation from the norm. There are very rare events | ||
| that can give permanent stat upgrades, but do not rely on these. | ||
|
|
||
| The game is lost if every party member dies. If there is not enough food, every action that the group takes has a -5%(subject to change) to every action per day | ||
| that they have not eaten. If that modifier drops below 50%, the group will starve. | ||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
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,16 @@ | ||
| Matthew Danielson | ||
| Started: 7/10/16 | ||
| Finished: | ||
| Documentation for Final Project | ||
|
|
||
|
|
||
| Customization Settings | ||
| Modifying start time - between days 1 and 999 - will increase the difficulty of the game by changing the probability of loot being found and the frequency of raids against the player. The game is balanced around starting on day 1; starting later adds an increasing difficulty curve. | ||
| Modifying difficult will affect the RNG elements of the game; the game is set, by default, to 2, which gives no modifiers to the player. A difficulty of 1 will give a modifier for the player, while difficulty 3 takes away from the player. The game is balanced around difficulty 2, and chaning this will lead to a respectively easier or more difficult experience. | ||
|
|
||
|
|
||
| Gameplay: | ||
| This game does not require any files other than the code itself; it will run within terminal, and uses only default ASCII characters to display all the information the player needs. This game will error check any input the player gives - though being careful is advised, as making the wrong move will not break the game, but it could ruin the player's current campaign | ||
| Everything else that is essential to playing is detailed within the game-simulation itself. There are specifics to the game that are best for the player to find out as they play - otherwise, there quickly becomes a very apparent best mathematical way to play the game. Thus, I will not detail those numbers here, players must get a feel for the game by playing it, and not by simply plugging the game into a formula. However, the game also does serve as a simulation in this regard; by disregarding the game aspect of this program, users can run this program by making the same choices repeatedly in order to simulation survival of a small group in a theoretical post-apolcalyptical scenario. | ||
|
|
||
|
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a hefty (and impressive) project! Be sure to implement it in pieces such that you have a working project at any given stage. While most of your concept implementations are able to be inferred, you should be sure to use arrays/strings and structures/enums in a useful and significant way.