lend lease bug in the SU ?????

[unmerged(18350)]

Last week I posted, that the SU is too strong in 1.5b (tweaks-forum)....

Now I realized the reason (Japan '36 scenario; normal):
In 1943 the SU had 3 provinces (Novosibirsk, Irkutsk and Omsk) in the far east with 62 IC each!!! I think thats a bit too serious, if you compare it with New York (IC around 50) or Tokyo. Normally the IC of these provs is 6, so I thought it was a result of the 'moving the industry to siberia event'. But after I checked several saves I realized that the IC of Novosibirsk, Irkutsk and Omsk is increased by 10 with every lend-lease-event from the US. I think these changes are much too serious for a lend lease event.... And is it wanted that lend-lease happens so often?? Is this a bug or is it normal??


Another lend lease problem (GB; '36 scen):

If you save the game after a lend-lease-event happened it is most likely that the event happens again if the game is loaded again. Its an easy way to build up the IC

 

[unmerged(14035)]

Yes, this is a bug due to the event history not being saved properly. This results in both of the Lend-Lease events being triggered every time the game is re-hosted. Read more about it in this thread.

 

[unmerged(18350)]

Yep its the same problem... But it happens in singleplayer games, too.

 

[TheDarkside]

Does anyone know how we can fix our saved games so it won't trigger next time we load?

 

[unmerged(12303)]

you should keep to one host (i.e have the same guy host the game each time) - the acts should not happen then. I have never had it happen 2 in sp though..

F

 

[jdrou]

Originally posted by TheDarkside
Does anyone know how we can fix our saved games so it won't trigger next time we load?

You can manually add the numbers of the events you know have triggered to the history list in the savegame. Search for "sleepevent" and the history list is right above it.

 

[jdrou]

Originally posted by Spinner
Yep its the same problem... But it happens in singleplayer games, too.

The event (3703) is "persistent" so it is not added to the history list when it fires. All events that could possibly fire are checked for their trigger conditions when a savegame is loaded. This event has a 30% chance of firing each time it is checked. Its persistence presumably means it was intended to fire more than once but if you never reload the game it won't and if you manually add it to the history it shouldn't fire again.

 

[Dalwin]

Seems like, persistent or not, they need to add a flag that indicates whether that event has been checked in the current time period (whether yearly cycle of checks or whatever depending on the event).

 

[jdrou]

Originally posted by Dalwin
Seems like, persistent or not, they need to add a flag that indicates whether that event has been checked in the current time period (whether yearly cycle of checks or whatever depending on the event).

I don't think they can do that without modifying the event engine. I think they just need to make it non-persistent for now. Then it would be added to the history when it fires. It would still fire when you reload from a MP client save that doesn't have the complete history so that bug still needs to be fixed.

 

[Dalwin]

So maybe rather than a persistent event just have a whole series of single shot lend lease events. ( I think I am just paraphrasing what you previously said here.)

 

[jdrou]

Originally posted by Dalwin
So maybe rather than a persistent event just have a whole series of single shot lend lease events. ( I think I am just paraphrasing what you previously said here.)

Yeah. Maybe one every 3-4 months would be equivalent to the intended effect of the existing event (30% chance checked once a month).

 

[Vulture]

Ok someone feels like scripting?