Still not ready...
Once again, I'm sorry to say that the work on the race refactoring & modding support still isn't done.
The scope of what I'm implementing keeps on expanding in ways that I didn't anticipate, which is resulting in features taking far longer to add than I'd planned. I want to make sure that I get this race rework right and implemented in the way that's going to be best for the game in the long run, so rather than cut these things now only to come back to them and spend more time on them in the future, I'm trying to get it all done now, which is why it's seeming to take forever.
For an example of what I mean by this, I'd expected the implementation of arachnid lower bodies to consist of a few description changes and sex positioning checks. Instead, it's ended up needing the implementation of spinnerets and ovipositors. Spinnerets being a new sex orifice requires a lot of changes and additions to the code, and then ovipositors needs the handling of eggs being transferred to a third party, the resulting pregnancy effects, and all of the random little pieces of related code scattered about the place to be handled in relation to this.
I started encountering these extra things after I'd already announced that I was moving on to the xml framework (which should have been the final stage of race modding/rework), so just when I'd said to everyone to expect it to be finished soon, suddenly I'm running into a huge amount of extra work being encountered that's taking a lot of extra time.
Thank you all again so much for your support, and I really don't mean to sound ungrateful, but as my rate of progress over the last few months has been absolutely terrible, it would probably be best if you stopped your support of this project here on SubscribeStar until I can get back on track and start giving you regular releases again. I'm sorry about how bad my progress and update posts have been, and I'll try to get back on track as soon as I can.
Once again, I'm sorry to say that the work on the race refactoring & modding support still isn't done.
The scope of what I'm implementing keeps on expanding in ways that I didn't anticipate, which is resulting in features taking far longer to add than I'd planned. I want to make sure that I get this race rework right and implemented in the way that's going to be best for the game in the long run, so rather than cut these things now only to come back to them and spend more time on them in the future, I'm trying to get it all done now, which is why it's seeming to take forever.
For an example of what I mean by this, I'd expected the implementation of arachnid lower bodies to consist of a few description changes and sex positioning checks. Instead, it's ended up needing the implementation of spinnerets and ovipositors. Spinnerets being a new sex orifice requires a lot of changes and additions to the code, and then ovipositors needs the handling of eggs being transferred to a third party, the resulting pregnancy effects, and all of the random little pieces of related code scattered about the place to be handled in relation to this.
I started encountering these extra things after I'd already announced that I was moving on to the xml framework (which should have been the final stage of race modding/rework), so just when I'd said to everyone to expect it to be finished soon, suddenly I'm running into a huge amount of extra work being encountered that's taking a lot of extra time.
Thank you all again so much for your support, and I really don't mean to sound ungrateful, but as my rate of progress over the last few months has been absolutely terrible, it would probably be best if you stopped your support of this project here on SubscribeStar until I can get back on track and start giving you regular releases again. I'm sorry about how bad my progress and update posts have been, and I'll try to get back on track as soon as I can.
I'm too lazy to figure out how to stop supporting, let alone actually do it. (The subtle/funny way of saying I don't mind supporting still.) Therefore, I shall sit here, with my laziness, and laze around.
I know a bit about coding, not enough to save my life but I know enough to get me by, and I know that when trying to have something do something new, when you already have a base to the set, you have to label it, send it here, send it there, respond here, and tell it what to do all the while simultaneously making sure you don't break a billion different things at the same time. And with what your implementing and having done, it will take a while, so all in all, we are along the journey as much as you are so there is no rush. You got this 🐺👍
no, you will receive money for this. I refuse to unsub for just a delay in a literally game changing update.
If you're sorry about the time it takes to do stuff the only thing i could see as a proper punishment is you starting to give regular-ish progress updates like every other week type of regular so we can atleast know what is causing issues
Any update? Like at all?
The next update is going to be big. I believe in you, so keep it up, and I know it'll be awesome.