SOTW 0.8.24.18 - Second Act Beta!

[yayswords]

We noted previously that in battles that you can win by just killing one guy, you get marginally more exp if you bother to kill everyone. I just had the thought that you didn't go out of your way to make it so, but instead it is the bonus exp characters get for killing blows that does it. I thought this bonus exp meant they got a larger share of the exp, but I tested just now on the starting orcs, and this bonus exp seems to not be a redistribution of the points, but a pure bonus. That means each time we don't actively finish them, we lose out on exp - very marginal amounts though. For anyone wondering what "actively finishing" means... nobody gets kill credit if an enemy dies to a DoT; the game does not seem to register the source of DoT's.

So yeah for anyone looking to maximize exp gains... don't let DoT's finish your mobs

Late edit: Okay, Bramble Coat on enemies. That it triggers twice from a dual wield attack, I suppose that's okay. That it takes away 10% health instead of 5%? Not sure... but it's still another case of I'm winning and I don't need buffs. But I'm saying 10% per hit, so 20% for a DW attack. Very owie.

[jack1974]

Good news, Ren'Py coder fixed the "false hover prediction damage bug".
So on next update will be gone. Still working on ACT4 now, doing the first of the big final three scenes

[jack1974]

Fixed the Bramblecoat, 10% was definitely too much!
Coding another minigame now (can't reveal what is about since is a spoiler). I really like those, you need to decide what to do on every battle, like rescue 5 people during day taking half day with medium risk, 3 at night but with low risk, etc (risk influences the enemy strength). And you can rest between each fight but there's a time limit. Having fun already testing them, so hopefully you'll find them cool too

[yayswords]

-> rescue 250 people with a marching band announcing my arrival

[FireSeraph]

Again, not sure if reported but I'm getting the damage prediction jumping all over the place. I select one enemy but instead of having the damage prediction hover over that enemy, the number shifts over to another enemy. It's not when the other enemy is guarding my target, sometimes the damage prediction jumps to rogue type enemies, dead enemies or empty spaces too.

[jack1974]

Yes it was a bug at Ren'Py level (so not my fault in this case!), this will be fixed in the next update

[jack1974]

Sigh, apparently the new Ren'Py update breaks again all saves... I've told the coder but don't have much hopes for a solution.
It sucks, I definitely recommend everyone stop playing this version unless they like to restart again from scratch when I release next ACT. Since are all changes done to the framework core library I have no control over it so in theory on every update everything can break... hopefully it reaches a stable version soon!!!
I'm sorry, usually Ren'Py is pretty good at keeping old saves compatibility, but this latest version has been a mess. I'm not able to make progress myself, I think will revert to an old version just to keep working on the game...

[yayswords]

Lol. This is getting tragic.

But please make a release when it's fixed, even if you're not sure some other update might not break the saves again. I don't want to start from scratch when act 3 hits if it can possibly be avoided.

[jack1974]

The problem is that this beta is exactly happening in the middle of one of the biggest Ren'Py updates. You see the benefits (game running much faster now) but there are also some inevitable bugs. However coder didn't reply yet, maybe this specific bug is just a minor thing that he can fix "on his side" and keep saves. Is strange because was able to load a specific save and worked, so at this point I'm unsure about everything

[fabulaparva]

Well, whatever happens, I hope that at the time the Act 3 comes out, you'll already have it running on a steady Ren'Py version. I can understand that despite the benefit of keeping saves stable with the old version, it would be a downer to finally publish the game at the end of the year, but with an old Ren'Py and slow speed, when at that point the new, fast build would've been available "already" for 3 months. And it's still better to have the problems now than having them hit the fan between the full game barely betatested and it's official release. Right now those pouncey dmg predictions are just amusing in a nerdy-kind-of-way, but no one wants them in the final product. Anyways, thanks for the heads-up, I'll be prepared, either or.

*doodles furiously*