This is the original version of this post
While we do have (Future Release Plans) for planning the roadmap of the next series of releases and what overall direction we want to go with them, I think it’s important that we also have a central thread for planning all the work and progress directly for the next update. Here we can also discuss outreach related to this update (something like Oliver did for 0.3.0).
I think these should be the major goals of this upcoming update cycle:
- Gameplay. Now that we’ve implemented new GUI, removed the cell hexagons, added compound clouds, and overall made the game more polished and presentable, I think it’s time we move on to an update to add a lot more gameplay and features to the game. I think we should really try to nail down some of the features/changes suggested on this thread (Improving Thrive’s Fun).
- Outreach. With a more polished and presentable game I think it’s nigh time to start more outreach to expand the team and community.
- Organization. I think in this release cycle, both for the sake of increasing the team’s work efficiency and in preparing for the arrival of more developers, we should reflect on the current workflow and if we can improve it.
For each of the overall goals for this next update, I’ll also list some sub-objectives that will help achieve that goal. Ideally we can take each of the sub-objectives on the page below and make separate threads for them to discuss them in more depth, and I can add links to those threads here to make this the central hub for this new updat.e
Gameplay is the foundation of the game, and as many of us have said so far, we need to create a good and fun game first, because that’s what will attract people to the project, and that will serve as a foundation to develop the game around. The following are features that will add to the gameplay.
All of the following are explained in this thread (Improving Thrive's Fun).
- Improved tutorial and tooltips
- Species mortality (Risk of extinction)
- Predatory NPCs
- Compound cloud changes
- Fluid mechanics
- Cell generation changes
- Organelle upgrades
- Combat improvements
- Agent system
- Predatory pilli
I think now is a ripe time to try to grow the team. If we can expand the group of developers while maintaining a good focus and organization it can be a huge boost to developing this stage and the stages to come, and will greatly help the project become self sufficient and not dependent on individual schedules. Ideally, the following three tasks should bring in more people to the team.
- Advertising. We have a template advertisement (Link will be on Slack). Included in the document is also a list of sites to advertise to. The plan is that this will be the primary means to recruit new developers to the team.
- This thread is currently discussing the outreach plan for September: September Outreach
- Contacting old members. We’ve done it before and we ought to try it again. I recall it did work with a few people last time. We just need to be careful not to contact members we’ve already contacted several times before. There’s a document of all the old members and their contact infos here (Link will be on Slack).
- Checking up on recently old members. There’s a good number of users who’ve joined recently, but then disappear soon after, and often all it takes is just a quick reminder to get them to come back and stick. This we have no list for so we should make one.
- Regular social media updates. There have been a few suggestions that we post more to social media. We should find people who have the time and interest to do so. I was thinking we could get some of the mods from the forum to help on that front.
- This thread is currently discussing this: Social Media Activity
- More dev forums, less Slack. There’ve also been a few suggestions from people in and out of the team that we should try to avoid having too much of the conversation on Slack. Let’s try to focus more of our discussions onto the forums, especially since Slack deletes older messages (though I’ll admit it’s a lot handier sometimes to use Slack’s instant and less formal messaging).
Assignees: NickTheNick, Naggorath
I’ve thought a lot about the workflow of the team in the past few months and I think we have a fantastic atmosphere and team dynamic. However, I think we could improve a lot on the focus and coordination of completing tasks, to try and create more of a clearer plan with mini objectives that we set along the way, and a sense of who is working on what. This one is really open to interpretation and I’m interested to hear what you guys think about it. My suggestions for how to accomplish this with are the following:
- Efficient workflow. I don’t want to compromise the free and voluntary nature of the project, because I think that’s what is one of the best parts of working on it and makes it enjoyable instead of stressful. At the same time, I want to try and integrate some sort of system of setting objectives or milestones, like with this thread, that we can aim for and complete so that we don’t get releases or features delayed by months or years.
- This thread is currently being used to manage workflow on GitHub: GitHub Workflow
- Self sufficient documentation. A clear, informative, and well designed wiki would be awesome. I think the wiki has huge potential to be able to fill newcomers in on most of the information that they need to know when joining the project. It can even greatly help current developers who want to learn more about the work of a different team or what have you. This could ideally save so much time for developers from having to explain things to other people by just pointing them to the wiki first. Again I don’t want to overload people with all these objectives I’m throwing out there so this is something that certain people should specifically focus on (For example I will work on this among other things since I cannot help on the development side).
- Team lead supervision. Maybe it’s just my perspective, but I feel like we could use the role of team leads more to its full potential. Some sort of habit of having team leads check up on people working in their team and then updating their progress on a central hub thread like this could help create an effective communication between our overall planning and the individual tasks people work on. Obviously we don’t want to overload team leads with the work they already have to do, but I think this can be done very effectively with minimal effort.
This thread is the central thread for planning version 0.4.0. The overall roadmap can be found here.
These are the main goals of this upcoming release cycle:
- Engine Switch. A reworking of the engine into one that is better understood by hhyrrylainen, and then through documentation and practice the rest of the programming team as well.
- Gameplay. Some updates to the gameplay to accompany the engine switch, so that the release is not too similar. This will also be a chance to test the waters before the upcoming gameplay update.
- Organization. To increase the team’s work efficiency and prepare for the upcoming outreach we want to do, we should work to improve the current workflow and documentation of the project (i.e.the wiki), as well as any media presences.
- Switching Engines Thread - A thread to discuss the engine switch.
- Guide to compile leviathan - A tutorial to compile the new engine.
- https://github.com/Revolutionary-Games/Thrive/issues - The list of all issues regarding the engine switch (and the other programming tasks as well)
- Separate compound storage
- Health separated from reproduction
- Rebalance movement
- Control scheme change
- Removing O2 and CO2, adding hydrogen sulfide and phosphate
- Add chemoplast organelle
- Melee organelle (Pilus)
- Life/Population tracking system with possibility for extinction, as well as a win condition (15 generations)
- Diminishing abundance of free floating compounds
- Basic AI
- Implement Compound Rebalance and Blurred Background mods
- Template Advertisement - We should update the template advertisement to have the up to date information on the project so that we can use it for outreach.
- Draft a list of old members of the team to contact and see if they are interested in returning. Make sure not to contact people we’ve already tried before.
- Regular social media updates, such as mini development updates. --DONE–
- Finish updating the wiki.
- Establish a clear workflow. --DONE–
- More dev forums, less Slack.
- Team leads keep tabs on their teams.
- September Outreach - A thread to discuss how to prepare for the upcoming outreach we want to do after this update (September Outreach is probably not the greatest name for it anymore).
- GitHub Workflow - A thread to discuss the workflow of the project.
- Thrive Organization Issues - Basically all the issues on this page are relevant.