Oh, so the system will only decrease the prices, not increase them?
thatās the intended implimentation, but to be honest with you I have gone to the auto-evo source code and to describ it , I would say a jungle with nearly no guidance and as you could expect it import other variables from other part of the code source, but first,Iāll try to make a comprehensive documentation , I think it will be helpful to the devellopers as much it is to me
Yeah, the more we know about the code the better.
At the end of the day, you just need to browse the code to find such things in any project. Because you cannot have any kind of comprehensive documentation saying where everything is as it would get super outdated fast or need constant updating. Though autogenerated documentation from the code comments would avoid this but we donāt have such a thing setup for Thrive as C# is just all around much nicer to work on in an IDE so any IDE will already handle that.
Though I admit that some general stuff could be documented better as a way to guide people to look in specific places. But here comes the issue of how much effort it is vs. how much it helps. Iāve somewhat recently written about the overall architecture of the game but no one basically finds that document and looks at it. So people just miss that and try to read the code and then ask questions that would have been answered by reading it.
I guess I can spend a couple of minutes looking up stuff in the code for you (I sort of remember most of these off the top of my head).
MicrobeSpecies class contains the definition of the species so it also has the organelles:
This is set in the organelles.json file for each OrganelleDefinition in the not very surprisingly named variable MPCost
:
Such a thing doesnāt really exist, so youād need to clarify what you want. For example thereās AIMutationMultiplier
in IDifficulty
interface, then thereās the editor discount multiplier, and also in difficulty thereās the player mutation rate variable in MPMultiplier
.
Well this is a big problem as I think itāll be quite confusing otherwise.
Perhaps have it and the amount it changed somewhere on the ābase editor screenā (how the editor looks like when you first enter it in an editor session)?

Though I admit that some general stuff could be documented better as a way to guide people to look in specific places. But here comes the issue of how much effort it is vs. how much it helps
I think it will help a lot if itās well done, I admit those it takes a lot of effort and time , and to be honest with this looks like a thing I am good at āreadingā and "documenting ", for the time being Iāll be reading and documenting the auto-evo (as it seems weāll need it soon in the road map that have been designed.
Why I think it will be helpful and a lot:
1- first understanding
2- adding new features
3-debugging
I might need to ask a lot of questions though but Iāll try to minimize it as much as possible
Weād really use having a good understanding of what is in need of being expanded not that far into the future. If you do manage to pull it off, good for you!

not that far into the future
Depending on you definition of āfar into the futureā
I might or might not succeed in my endeavor, as you may already know I have a national exam so nothing will be done realistically before summer so is this too far into the future or not?
Well, multicellular stage development should start somewhen either in july or august of this year, and there work on multicellular autoevo will likely start.
Then this is should be considered too far but there is nothing to be done yet Iāll try my best so a prototype could be ready in August
You mean a prototype of the āautoevo code explanation documentā?
Yup, believe it or not itās easy to make mistakes when youāre alone as well as to forget something, so the best I could call my own efforts is a ā prototype ā
And then either you or someone else will improve upon the prototype until itās no more a prototypeā¦
Rather then that it will be likeā oh there is something missing in the documentation please add it or maybe this information is wrong you should correct it.
but anyhow I think at least one should do a check up after me.
And probably not long after the protodocument is releasedā¦