|
|
Post by secondcomingofzeno on Mar 21, 2020 1:18:20 GMT -6
How to test.
1:Save a turn before enemies take your land (save every turn until they do, I suppose?)
2: Let enemy take land from peace deal.
3: Reload save a turn prior when you owned the land
4: Enemy still has the land.
This bug ruined an awesome 1900-1950 Japan game for me, France now owns the entirety of asia.
|
|
|
|
Post by rimbecano on Mar 21, 2020 12:12:34 GMT -6
I'll note that this works the other way, too: you can keep territory you've gained through a reload to before the time that you captured it.
|
|
|
|
Post by williammiller on Mar 22, 2020 10:29:58 GMT -6
Thanks for the report - have posted this to our internal issue thread.
|
|
|
|
Post by Antediluvian Monster on Mar 22, 2020 11:07:31 GMT -6
This also happens with invasions and territory captured via invasions.
E.g. if you have a successful invasion battle and then reload the save before the state of having been invaded sticks to the territory. And if an invaded territory is captured in turn resolution the state of having been captured also sticks if you reload the turn before.
The game also seems to try to execute invasion battle that turn even after reloading. This is possible to exploit to invade multiple places within single turn. That is: have Place A as invasion target and execute a turn with invasion battle -> Reload the turn before and switch invasion target to Place B -> The game may* now try to execute invasion battle for Place B -> Reload again and now you have both Place A and Place B invaded without actual passage of time.
*It might also execute an invasion battle for AI, if it was working on invasion.
Backuping the save in a different folder is a workaround.
|
|
|
|
Post by williammiller on Mar 22, 2020 13:17:09 GMT -6
Ok, after looking into this (and my thanks to Beta Team member aeson ), its 'because the MapData file in the save folder is updated on the fly to reflect changes in possession ownership, invasion/rebellion status, and base capacity, rather than that being tracked in a temporary file that gets merged with the MapData file upon the game being saved. Now, this should only happen if the game is closed without being saved, but if you see it happening otherwise please let us know. |
|
|
|
Post by secondcomingofzeno on Mar 23, 2020 5:33:17 GMT -6
Ok, after looking into this (and my thanks to Beta Team member aeson ), its 'because the MapData file in the save folder is updated on the fly to reflect changes in possession ownership, invasion/rebellion status, and base capacity, rather than that being tracked in a temporary file that gets merged with the MapData file upon the game being saved. Now, this should only happen if the game is closed without being saved, but if you see it happening otherwise please let us know. If we see it happening before or after it's patched? ;v Because right now it is bugged. |
|
|
|
Post by Antediluvian Monster on Mar 23, 2020 6:25:36 GMT -6
Ok, after looking into this (and my thanks to Beta Team member aeson ), its 'because the MapData file in the save folder is updated on the fly to reflect changes in possession ownership, invasion/rebellion status, and base capacity, rather than that being tracked in a temporary file that gets merged with the MapData file upon the game being saved. Now, this should only happen if the game is closed without being saved, but if you see it happening otherwise please let us know. If we see it happening before or after it's patched? ;v Because right now it is bugged. "if you see it happening otherwise" i.e. if you see it happening in situations that does not involve quitting without saving and then reloading. Otherwise it's a funky and somewhat unfortunate feature of how the game tracks game progress that one might wish to be changed, but not really a bug. As I wrote above, a workaround is to make an occasional backup copy of the save. |
|
|
|
Post by secondcomingofzeno on Mar 23, 2020 6:52:32 GMT -6
That's...Not very helpful.
Bugs should be squashed, not left in!
ESpecially ones that can ruin runs.
|
|
|
|
Post by williammiller on Mar 23, 2020 10:15:29 GMT -6
I'll see if Fredrik W can put some sort of block in so this cannot occur even if you don't save when you reload. |
|
|
|
Post by secondcomingofzeno on Mar 23, 2020 18:58:24 GMT -6
I'll see if Fredrik W can put some sort of block in so this cannot occur even if you don't save when you reload. That would be awesome. Because some players like savescumming. XD |
|
|
|
Post by secondcomingofzeno on Apr 27, 2020 23:46:27 GMT -6
Did this end up being fixed?
|
|
|
|
Post by williammiller on Apr 29, 2020 10:27:22 GMT -6
Not as of 1.19/1.20 to my knowledge - as you might have noticed 1.19 had a lot of stuff in it, and we wanted to get it out since it had been delayed longer than expected.
|
|
|
|
Post by secondcomingofzeno on May 4, 2020 3:17:54 GMT -6
Not as of 1.19/1.20 to my knowledge - as you might have noticed 1.19 had a lot of stuff in it, and we wanted to get it out since it had been delayed longer than expected. Awww... Well, lets hope it gets fixed soon! Issues like this are truly letdowns when they happen. |
|
|
|
Post by rimbecano on May 4, 2020 13:31:18 GMT -6
Not as of 1.19/1.20 to my knowledge - as you might have noticed 1.19 had a lot of stuff in it, and we wanted to get it out since it had been delayed longer than expected. Awww... Well, lets hope it gets fixed soon! Issues like this are truly letdowns when they happen. TBH, if I were the devs, it would be a rather low priority to fix because: 1) It pretty much only happens when the player cheats by quitting without saving after something happens that he doesn't like. That, at least, is my experience, given that I cheat this way on a regular basis. 2) It can help the player as much as it can hurt him (I've gained far more territories than I've lost this way). 3) Cheating in a single player game doesn't hurt anyone, as the player only has AI opponents. I will also note that if you *do* lose territory, all of the files involved are human-readable, and notepad is your friend. :-) |
|
|
|
Post by secondcomingofzeno on May 4, 2020 19:48:40 GMT -6
Awww... Well, lets hope it gets fixed soon! Issues like this are truly letdowns when they happen. TBH, if I were the devs, it would be a rather low priority to fix because: 1) It pretty much only happens when the player cheats by quitting without saving after something happens that he doesn't like. That, at least, is my experience, given that I cheat this way on a regular basis. 2) It can help the player as much as it can hurt him (I've gained far more territories than I've lost this way). 3) Cheating in a single player game doesn't hurt anyone, as the player only has AI opponents. I will also note that if you *do* lose territory, all of the files involved are human-readable, and notepad is your friend. :-) Cheating would be inputting a special code, or hacking the game. Savescumming is something quite different, and unless the game has bugs, doesn't make the game 'easier', it just rolls the RNG again. If I wanted to cheat, I could just start with all techs and giant ships, but that would be boring. I only have as powerful ships as the enemy...Usually. |
|
