Nano Factory Not Halving Upgrade Costs?

[The Plucky Terraformer]

I'm running Yitzi's 3.5d and saw that in his 3.4b patch he fixed the upgrade cost bug. However, I'm still having this problem, costs are not being reduced.

Anyone else having this problem?

[DrazharLn]

It's useful to attach a save for these kinds of things so that other people can test it easily.

[The Plucky Terraformer]

All's good now, I did a wipe and clean re-install of Yitzi's, no additional PracX updates, and everything seems to be working!

 

[DrazharLn]

It would be very surprising if pracx broke nano factory logic :/

I might have a look.

[The Plucky Terraformer]

I have no idea what my specific combination of patches was, so I'll just ping again if I see the bug come up.

[The Plucky Terraformer]

Hello again! The upgrade cost bug has happened again. I've included a save file this time with the Nano Factory built.

[DrazharLn]

This may be a bug in yitzi's patch. I can reproduce on yitzi version 3.5d but not on the GOG version or scient v2.1.

Costs with GOG version and scient v2.1:

With nanofac cost of upgrading to silksteel trance sentinels: 30
Without nanofac: 60

Costs with yitzi: both 60

I tested by loading your save, looking at the upgrade costs then using the scenario editor to set the nano factory to unbuilt.

Recommendation:

Use an older Yitzi patch version or don't use Yitzi.

I attach two saves for easy testing. Costs with deletednanofac should be 60.

[The Plucky Terraformer]

I've been trying to narrow down the cause by editing in the Nano Factory right at the start of a fresh game with 3.5d.

The upgrade halving works in those cases, so that suggests to me that something in the course of the game is triggering the bug.

That's all I've been able to determine right now.

[DrazharLn]

Yitzi has been away for a while and no one is maintaining their patch, so narrowing the cause is unlikely to help :/

I suggest that if you don't need yitzi features, just use another patch; if you do need yitzi features, try a different yitzi version.

[Induktio]

Yeah, binary patching has some significant maintenance issues. If some other person looks at the file afterwards, there's no easy way to list what changes have been made. I would guess, in these kinds of situations, one would have to run a binary diff between a patch version that didn't have this problem and one that has it, and then try to figure out which one of those changes *might* relate to the problem. But it is very time consuming to do anything with binary patching, let alone try to deal with multiple versions patched in a way one does not know about.

[The Plucky Terraformer]

Yes, it's a shame, but this isn't a game breaking bug that's worth going into much more effort for. Thanks for looking into it.