Java Lilith's Throne [v0.4.9.9] [Innoxia]
- Thread starter Waaifu
- Start date
-
- Tags
- adventure anal sex character creation corruption fantasy female protagonist footjob furry futa/trans futa/trans protagonist gay group sex handjob lesbian male protagonist monster girl oral sex pregnancy prostitution rpg spanking text based titfuck transformation trap turn based combat vaginal sex
- Oct 15, 2020
- 1,136
- 2,413
- Oct 26, 2017
- 1,567
- 1,267
jfgh23 has it. Just interact with Meraxis for a little bit if you meant the newly broken stuff. You should easily be able to go what while attempting to have sex and find her, so you don't have to look at the code, don't worry.
Over three years for a five-minute fix (was about to type five-second but that's exaggerating unless we just count the diff) that might have been PR-rejected multiple times because it was "too short"...?
- Apr 29, 2018
- 1,167
- 1,285
I am unaware of such a reason for rejecting actually existing. The likely explanation is the usual one: Nobody who bothers submitting PR's ranked this very highly on their personal todo list and nobody who complains about it as a pressing issue bothers to submit PR's.
Can confirm, don't give a shit about this one. It the grand scheme of things, its so minor it doesn't even matter.
This is never going to annoy me enough to bother trying to do anything about it. Soubly so when there's so much else that's wrong that gets my ire first.
- Oct 26, 2017
- 1,567
- 1,267
Thanks for clearing things up as usual. It would indeed be quite a thing if it had been rejected...
- Oct 15, 2020
- 1,136
- 2,413
Another delay, you say?
You don't have permission to view the spoiler content.
Log in or register now.
- Apr 14, 2020
- 1,822
- 4,055
*Facepalms through my skull sending my hand into another dimension*
Well... she did warn in the previous post that it could take longer than expected. And did so again in this one. The difference now is that she makes it clear there may be a delay, whereas before it was a whole bunch of
So, as I was modding, I suddenly had an epiphany regarding a complaint someone (tehlemon?) made about the status system. From what I remember, it was that it constantly evaluates a conditional for every single character on every single turn and drags down the performance of the overall gameplay.
Basically, I suggest the idea that Inno start shifting some conditional evaluations towards cell/worldmap-based situations if we're going to cut down the game lag.
You don't have permission to view the spoiler content.
Log in or register now.
Basically, I suggest the idea that Inno start shifting some conditional evaluations towards cell/worldmap-based situations if we're going to cut down the game lag.
Last edited:
- Mar 1, 2018
- 2,107
- 2,347
While I'm not surprised that the update was to say there was another delay, I am glad that Inno's communicating regularly and not just going silent like she did a while back. It's also a good thing that she's not promising dates for the new content, since her track record of meeting said dates speaks for itself.
Well, in her case those updates means nothing, there's really no difference between silence and nonsense of her "updates".
P.S. I wouldn't be so rude if she wasn't taking money.
Man, it's going to be really cool with v0.4.0 comes out!
...wait...
I wish I could take credit, but it was actually Sarkath who really found that one.
Although, like what you found, I did bring up that the game is keeping NPCs loaded and active when they really didn't need to be. Proper NPC and asset management would do wonders for this game. Trying to find a way to fix this for everything in the game is what made me go "fuck this, I'll make my own" lol
- Oct 15, 2020
- 1,136
- 2,413
There would be no need for that if she just made more realistic promises. See, she knows she can't make the goals she sets, but she sets them anyway, meaning that nobody, not even she, will have any idea when the next patch is coming out. If it's going to take a month or two, just say that, instead of all-but-promising yet another delay.
I don't know what's sadder; that you're praising Inno for this, or that it's genuinely praiseworthy.
- Mar 1, 2018
- 2,107
- 2,347
Not really praising, just commenting that I prefer the semi-regular updates to months of silence.
And the fact that Inno, or any dev for that matter, finally communicating semi-regularly is praiseworthy is definitely sadder.
- Sep 8, 2019
- 510
- 855
The only (admittedly minor) issue with this is that a resolved pregnancy can technically affect other maps. For example, if you impregnate Lilaya (or anyone living in her house) and a map-based system is used, the pregnancy will only resolve when you're in her house, and will resulting offspring will always appear in other maps. As it stands now, you can impregnate her, hang around in Submission, and there's a chance that after she gives birth, you'll run into one of your kids without having gone back to her house at any time.
My somewhat hacky solution was to simply cut back on the number of status effects that are checked. For most effects it would wait until you shared a tile with an NPC (or until the length of time between updates got close to overflowing) before it updated the status. For status effects that can impact the game globally (AFAIK, pregnancy is the only one at this time) it would always run them. This would result in substantial performance gains, albeit with little change to the memory situation.
If by maps and regions you're referring to a broader scope (such as entire cities, chunks of the overworld, etc) then that approach would be a fantastic addition to what my deferral system is doing, as it would reduce the NPC count.
Another (likely far more ideal) approach to the pregnancy problem would be to add in a scheduler for globally-impactful events. This would allow the NPC to be unloaded at will, then reloaded on demand when the event resolves regardless of where they are. I think tehlemon and I discussed something like this a while back.
Yup. And instead of actually trying to make that work for LT, I ripped it wholesale and used it in my own prototype instead lol
Honestly, that would logically require global updating, since pregnancy operates on the aspect of omnipresent time and also has multiple stages of progression that require updating. Status effects like this escape my solution, sadly, as I hadn't gotten this far down the road of the analytical process. But, I do think that instead of each pregnant character running the evaluations, that there should be a master-like hive code; a one-size-fits-all section that tracks and records all pregnancies and executes changes accordingly: having a single script running as opposed to multiple scripts of the same code running simultaneously. I'm actually experimenting with that concept in my mod and it seems to be working well enough.
Yes, this is exactly what I'm talking about when I refer to a "master-like hive code:" Some kind of overseeing mechanism that manages all pregnancies until key parts.
100%. Experimenting with this concept myself quickly showed productive results. A player could have as many characters as they wanted on any map, but none of the functions nor conditionals would see action until specific situations of engagement and it would save quite a lot of resources. There's many maps in the game already, so dividing the entire network up by chunks sorted by location would be a great way to cut down on the gluttony if we're starting to expand towards global maps and entirely new cities.
Thanks for the comment. I've included a brief explanation on my profile about my mod(s) and will remember to do so from now on.