-
Notifications
You must be signed in to change notification settings - Fork 0
Planning and upkeep
This is where future plans for the game will be discussed. There are two pages for these discussions. The first describes in detail features that will be added into the game, the second is a place to make proposals. Bug fixes are not to be listed here, but rather in the issues tab.
Before helping on this page, there are a few guidelines to keep things organized.
If you have an idea for something you wish to add to Theta the Slime, then you may edit the page Proposals. At the end of the page, add an h2 containing a brief description of your idea. Below, describe it in detail. At the end of your proposal, add two dashes, followed by your github username, and then an hr.
If you wish to comment on another person's proposal, you may add a quote tag between their signature and their hr, ending in two dashes and your username. You can also add at the start of your comment either [agree] or [disagree]. Doing this is a vote for adding or not adding the feature to the game. If you make another comment with a vote, then your newest comment counts.
You are strictly prohibited to edit another person's proposal or comment.
If 80% or more of votes are for adding the feature once five votes are given, or if enoua5 agrees with the addition, the proposal becomes a future feature.
Once a proposal becomes a feature, it is to be removed from the Proposals page, and appended to the Future Features page. From here, commenting works similar to the Proposals page, but there is no voting. The goal here is to create a plan on how the feature will be added and by who.
Additionally, once a feature is added to this page, it must also be added to the game's todo list (/Theta-the-Slime/GameElements/data/todo.js). This list is an array of strings, ordered by importance.
Once the feature is finished and pushed into the main branch, it is to be removed from both the Future Features page and the todo list.
The changelog (Theta-the-Slime/GameElements/data/changelog.js) must then be updated. The update summary will be added to the top of the string in this format:
<h3 class='menutext' style='text-align: left; margin-left: 10px'>version [version number here]<br>\
Started [3 character month] [date], [year]<br>\
Released [3 character month] [date], [year]<br>\
- Major changes:<br>\
- - [list all major changes]<br>\
- Minor changes:<br>\
- - [list all minor changes]<br>\
- Bugfixes:<br>\
- - [list all bug fixes]<br>\
</h3><hr>\
Refer to changelog.js for more clarity.