This is a suggestion.
Instead of having a separate toxin vacuole and a separate bioluminescence vacuole and all that, why not have them as subtypes, like cilia has subtypes and digestion has subtypes?
This is a suggestion.
Instead of having a separate toxin vacuole and a separate bioluminescence vacuole and all that, why not have them as subtypes, like cilia has subtypes and digestion has subtypes?
Probably because those have special functionalities while normal vacuoles are 100% storage only. And perhaps unlock conditions are not made for subvariants
sounds like unlock specifications should be made for variants, then. either way it seems like the game should be changed in this regard, someday
Not sure the developers are interested in putting effort into that currently when things have moved to a bigger picture
all that needs to be made is an issue and a planned change, the issue can be ignored as long as developers would like
I suppose so. I think it could be cool if in the future cell types and stuff were determined by not just organelles but also their variants
We have 600+ open issues… So opening a new issue for this would basically do nothing except add it to the backlog and then maybe in 5 years this might get done.
it could live on the backlog if it has to, not a very urgent change
I suppose this could be done then… So that it can then wait years to be implemented, if it’s even ever considered that such an inclusion of the special vacuoles into storage only vacuoles is a good move, which I can see might infact not be.
If somebody wants to make the change, they can. That does not require there to be an open issue for it.
Yeah but it could take a while for that somebody to arrive in the lands of our github
we can just do changes without an issue?
Pretty sure you’d still need to make a poll request. Unless you mean something in a fork
Absolutely. You make a fork from github, make changes in that fork and then make a pull request to add it into the main game. A pull request can link an issue, but that’s not required. For a pull request to be accepted, you need the sign-off from the Programming Team that it’s well implemented and from the Game Design team. Of course this comes with requirements of being well-designed, fitting into the game, being bug-free, etc.
Which those requirements are why such fork mergers from people interested in adding some specific functionality are pretty rare, unless the said people know much about coding and especially Thrive’s code to begin with