0.4.3 Features Discussion Thread

Gameplay
3

In addition to Future Release Plans thread there are the issues on github that could be used as a list to pick stuff from: https://github.com/Revolutionary-Games/Thrive/issues

Also some fan favorites we could prioritize:

  • pilus
  • options menu (with fullscreen option)
  • saving
    Those are probably the most requested things I see. There’s also mac support, but that’s not really something that could be planned.

Here are the things I have planned to work on that are thrive related, they’ll be done when they get done. In the (approximate) order I plan to do them:

  • write a git LFS api to ThriveDevCenter and move Leviathan and Thrive assets to use it. It would easily allow any team member to create git commits that have changes to the assets. This would also allow different branches.
  • Move the engine to use variable rate ticks and not use interpolation with local games to help with the lag that Oliveriver feels when playing
  • Add physics constraints to the engine and then do the pilus as an example of that
  • Investigate if we can use the bsf forward rendering mode (and add a way to toggle it, maybe in the launcher + a dialog popup telling people that intel is bad) to fix crashes for intel people
  • Create a sound source component and replace the microbe one off playing sounds with the sound components, which hopefully will make the audio nicely 3D spatialized.
  • Try to track down any crashes that get reported
  • Maybe get started on binding agent stuff to also test out the physics system (basically a button which you can press when you have the binding agent organelle to just become attached to any cell of your species that you touch)

Here are then some things I dream about doing once the git lfs stuff is done:

  • make a new type of dev build option, I’ll probably name it dehydrated which doesn’t include any git lfs contained files in the zip. Instead just a list of file identifiers and paths + a script that would download the files.
  • With the majorly reduced disk space requirements I’d then configure CircleCI and Appveyor to make dev builds that are uploaded to ThriveDevCenter. This would make dev builds automatically for every commit and pull request.
  • Add a way to link the launcher to a ThriveDevCenter account, and allow playing dev builds with the launcher. Allowing login to ThriveDevCenter with a community forum account that was in a specific group, like supporter or something for patrons, would then allow those people to use the launcher to play the dev builds.
  • Add some controls to ThriveDevCenter to promote certain builds to be “build of the day” to make it be sent to the people who have linked their launchers.

So basically I’ll be busy with a bunch of stuff even without attempting to do much gameplay stuff

And finally I’ll suggest some issues that could be included in 0.4.3 (for other programmers to work on):

  • The new GUI (of course)
  • pilus (I’ll work on this)

That’s quite a few issues but many are pretty fast to do (if I did them). I also included some harder ones. These are mainly ones that don’t really affect gameplay, so I still haven’t really suggested other gameplay stuff than the pilus to be included.

5 Likes