Possible bug: Some events always trigger during MP rehost
As most players who play this game in multiplayer know, a lot of the events ALWAYS trigger when you rehost the game. This can sometimes take on absurd proportions, as can be seen from the following screenshot:
The events that I have noticed are the lend-lease to USSR and to UK. Anybody saying this is WAD simply has not every played a MP game with frequent rehosts. I do know that the "persistent = yes" command means they can trigger more than once, but having them trigger 6 times in around 18 months of game time (average once every 3 months) is just not very realistic. This high trigger frequency is not seen in SP games, it only happens due to rehosting the game. This can at times generate unnecessary rehosts due to some people exploiting the system, for example the Soviet player simply leaving the game (so he can get that nice +30 IC and 10,000 supplies when you rehost a few minutes later).
Suggestions:
1) Fix the event trigger mechanism so that the events do not happen 100% of the time when you rehost.
2) Do nothing about the trigger, but decrease the effect of it (to say 1/3 of current)
As most players who play this game in multiplayer know, a lot of the events ALWAYS trigger when you rehost the game. This can sometimes take on absurd proportions, as can be seen from the following screenshot:
The events that I have noticed are the lend-lease to USSR and to UK. Anybody saying this is WAD simply has not every played a MP game with frequent rehosts. I do know that the "persistent = yes" command means they can trigger more than once, but having them trigger 6 times in around 18 months of game time (average once every 3 months) is just not very realistic. This high trigger frequency is not seen in SP games, it only happens due to rehosting the game. This can at times generate unnecessary rehosts due to some people exploiting the system, for example the Soviet player simply leaving the game (so he can get that nice +30 IC and 10,000 supplies when you rehost a few minutes later).
Suggestions:
1) Fix the event trigger mechanism so that the events do not happen 100% of the time when you rehost.
2) Do nothing about the trigger, but decrease the effect of it (to say 1/3 of current)
Upvote
0
