Java Lilith's Throne [v0.4.10] [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
- Feb 26, 2018
- 30
- 17
Is it ok if I copy the 'properties' file from 3.5.1 to 3.5.4? (by that, I mean replacing the file in 3.5.4 w/ the one in 3.5.1)
I'm asking because I don't really want to go through the effort of filling out the encyclopedia all over again.
EDIT: Nevermind, I looked at the property folders. That should've been fucking agonizingly obvious.
I'm asking because I don't really want to go through the effort of filling out the encyclopedia all over again.
EDIT: Nevermind, I looked at the property folders. That should've been fucking agonizingly obvious.
Last edited:
- Apr 29, 2018
- 1,167
- 1,285
In general, yeah. Saves or the properties file practically never break between versions.
Specifically though ... just don't play 3.5.4, it's a very broken, not-even-really-preview version and not suited for an enjoyable playthrough.
- Nov 26, 2018
- 657
- 1,609
Keep a backup of your saves. Others have reported that v0.3.5.4 has corrupted their saves. I'd advise just sticking with v0.3.5.1 for now until v0.3.5.5 is released.
- Feb 26, 2018
- 30
- 17
Ok, thanks for warning me. I was looking at the properties file for both versions, and I noticed a few things that were different, so I decided against it in the end. I guess there wasn't even any need to do that in the first place, though.
- Nov 26, 2018
- 657
- 1,609
I've always had copied the properties file from previous versions and haven't encountered a problem. I'm assuming the game loads the values it finds from the previous version properties file and then rewrites the file with the updated parameters.
- Feb 17, 2018
- 1,163
- 1,458
- Mar 1, 2018
- 2,139
- 2,411
Hoping for before, but not holding my breath.
- Nov 26, 2018
- 657
- 1,609
- Jul 12, 2019
- 54
- 74
5th delay in a row!
Honestly, at this point she may as well just change her entire schedule to release on a monthly basis only. Though, with our luck, that would probably mean seeing a new update every 2 months instead... Worse yet, she really seems to believe that the schedule is going to revert to "normal" after this update. Looking at her track record, I'm extremely skeptical...
I've never met a developer so much in denial about the inefficacy of their management skills, and one who still insists on underestimating how much time things need before they are ready. Either that or she's one of those who keeps adding stuff at the last minute, which leads to another thing, and another...
Honestly, at this point she may as well just change her entire schedule to release on a monthly basis only. Though, with our luck, that would probably mean seeing a new update every 2 months instead... Worse yet, she really seems to believe that the schedule is going to revert to "normal" after this update. Looking at her track record, I'm extremely skeptical...
I've never met a developer so much in denial about the inefficacy of their management skills, and one who still insists on underestimating how much time things need before they are ready. Either that or she's one of those who keeps adding stuff at the last minute, which leads to another thing, and another...
Last edited:
She is working on her own most of the time for that game, so it is random when each version are released, just have to take your time until the new versions is out on there.
- Feb 17, 2018
- 1,163
- 1,458
Come on, it's not a rare sight not only for indie but for AAA games as well. It's home-made game engine on Java and it's bound to break all the time both because it's Java and because it's home-made engine with all support you can rely on existing only in your head. Deciding against others' helping is understandable, too, since unless those people are actual programmers (and not some college kids with raw enthusiasm) code is going to get real messy real fast. And if you try to make them learn they just might not show up ever again one day just because life circumstances changed.
- Jul 9, 2017
- 189
- 740
I mean... I'm not saying that the creator isn't allowed to take longer to release another build of their game. But I will say that if the creator can't be too sure of when they can release the next one, then they shouldn't really publish a schedule. I have seen several indie game developers with a schedule that basically consists of: "Next update will drop when it's ready." And their followers are more than ok with that.
- Aug 22, 2017
- 989
- 1,042
For some, "next update when it's ready" is good and all, for other, if they don't have a schedule or something similar, they become lazy.
Not saying anything about inno here, i'm just saying some need a time limit if they want to have any work done.
Hearing you guys talk about Innoxia's code made me think her code is horrendous in some way, but looking at it now it looks pretty normal to me. Like, okay, there's that check every turn if prologue is finished or nullchecks with typechecks for characters, but those aren't the reason for major lagging. They are a sign of bad structure as you want your variables to be of proper type when you pass them, not check them for their type after they are passed into somewhere.
Game class with all those IsPlotDiscovered and IsPrologueFinished is bad to look at, but it shouldn't cause any lags, it's just a generally hard to maintain code, performance isn't affected. endTurn method there does a lot of things, but it's the same thing as for that whole 4k lines long class. MainController is worse look-wise, and I think most of the bugs come from being lost in here. EventListeners called from there check by string comparison, now that's a way to start lagging. RenderingEngine is the worst. There's a lot of StringBuilder optimisation all over the place, though.
It's from rebuilding whole interface and all text every button press, isn't it? Does Java have coroutines? I don't think I saw any sign of delayed loading of text/icons when I played, it's all simultaneous. Pretty sure that's the main reason, StringBuilder is great and all that, but it's still a lot of memory juggling, when you do this kind of rebuilding whole screen it's just faster to split execution into multiple frames.
Game class with all those IsPlotDiscovered and IsPrologueFinished is bad to look at, but it shouldn't cause any lags, it's just a generally hard to maintain code, performance isn't affected. endTurn method there does a lot of things, but it's the same thing as for that whole 4k lines long class. MainController is worse look-wise, and I think most of the bugs come from being lost in here. EventListeners called from there check by string comparison, now that's a way to start lagging. RenderingEngine is the worst. There's a lot of StringBuilder optimisation all over the place, though.
It's from rebuilding whole interface and all text every button press, isn't it? Does Java have coroutines? I don't think I saw any sign of delayed loading of text/icons when I played, it's all simultaneous. Pretty sure that's the main reason, StringBuilder is great and all that, but it's still a lot of memory juggling, when you do this kind of rebuilding whole screen it's just faster to split execution into multiple frames.
- Oct 5, 2018
- 270
- 493
Get a bunch of slaves optimized for various jobs and you'll start to notice lag on every ingame hour tick, from it processing everything.
Is Inno one of those people that become "lazy" without a schedule? I don't know. All I know is that trying to stick to one has been a futile task for well over a year now, with constant delays and delays for delays. Having a schedule doesn't means jack if she can't even -at least- abide by what she set for herself. I mean, what's the point then? I guess that's the problem when you work for herself and don't have a superior keeping tabs on you.
Think of it this way - you have a week to deliver results, manage your time and tasks accordingly and prepare yourself to release an incomplete version if necessary... but at least make the updates consistent. Alternatively, accept the fact you cannot deliver at the pace you want to and take a more deliberate pace. Using tight schedules as an "incentive" is a short way of burning yourself out sooner rather than later. The stress piles up, sleeping schedule gets screwed and your health deteriorates. It has happened to Inno before and it can happen again.
Also, I find that people tend to be a lot less salty when Inno doesn't set a fixed date. I know these -should- be treated as estimations but what really happens is that it creates expectations in folks, specially those who are new to the game and don't know her "track record". Don't give out dates, make it vague, and people will have less reasons to complain. I understand that some delays are inevitable, that shit happens, but 5 of them in a row is just bad. Doesn't matter if it's a solo indie developer or AAA company using a shitty home-brew version of X engine.
Last edited: