This save has the bug. It's the same bug with a different effect. You can cause it with the exact same method as last time. All that changed is that you have to end the turn to get the second tech. Your fix seemed to have pushed the acquisition of the second tech off to the following turn.Your previous save already had the bug in it (no matter what I did I received two free techs). Is that the case here too? That's not very helpful in fixing the original bug that's causing this. I'd rather have instructions on how to cause it.
Strange. It's pretty consistent on my end. The shift and enter buttons skip turns rapidly.If you hold them into a turn that you get a new tech on and continue holding through the tech pop up the turn will skip to the next before you can select a free tech. You'll then be able to select a free tech, and the next turn after that you get a second free tech.Your method of causing it never worked for me, and it doesn't now either. It's not very helpful to use a save that already has the bug triggered because how would I check if I can reproduce it?
No I understand the desire to fix bugs first and address balance concerns in a bugless environment. I was asking if this fix will be followed sooner or later with balancing to make their UHV playable, or if the next major version will be released with Babylonia being unwinnable?I am fixing bugs first, balance later. Those two things aren't really related.
You seem to be operating under the assumption that I deliberately made the Babylonian UHV unwinnable or that I deliberately introduced an exploit that I didn't know about until a few days ago to address this problem.
If that's the case, yes. I made the UHV unwinnable to spite you and every Babylonian player personally. And of course I always address balance problems with random glitches that I can't even use myself.
I've updated the mod since then so no idea, but if I remember correctly I tried to load the save on win7 and it worked perfectly so yes that was wine-only. But since then I found out that the bug (or at least the python error complaining about collapsed/newly spawned civs) can also happen on windows, albeit it's extremely rare. After playing dozens of games, I've only encountered it once: I was playing with the English, and after an Indian collapse the game crashed. I couldn't get a save before that turn, but I did save the game exactly in that turn (basically that means you open the save and after a bit of loading the game crashes). I'm not sure if you can do anything with it, I'll upload it anyways.I still want to look into this, do you know the commit this is from? I tried 1.15 and the latest commit as of the time of the post, neither of which were compatible.
Sorry, disregard this debug message. My conditions for unexpected behaviour were too narrow, I think that situation was fine. I'll update the check soon.Noticed when playing from 3000AD> 1580 dutch, this message showing about Bhopal in India. Now I saw it was 1540 and Iran appear at 1500, so likely happened in 1500-1540?
Looks related to the hindu wonder that gives food for religious buildings?
EDIT: Progress stopped at 1540, no crash it just doesn't continue and stays at 1540. Had to ALT-F4.