Krakatoa event triggers devastation for every single player in multiplayer causing 100% devastation in all of asia.

[Shaddarhim]

Integrity​

I have verified my game files (on Steam)​

Yes

I have disabled all mods​

No

Required​

Summary​

Krakatoa event triggers devastation for every single player in multiplayer causing 100% devastation in all of asia.

Description​

this bug exists since game release. its about time to be fixed ...

Steps to reproduce​

Have a multiplayer lobby with several players and trigger the krakatoa event.

Game Version​

all of them

OS​

Windows

Additional​

Bug Type​

Other

Save Game​

View attachment autosave.v3

Attachments​

Player Pain​

10

 

[Shaddarhim]

bump

 

[Shaddarhim]

bump

 

[Shaddarhim]

bump

 

[CaesarVincens]

bump

Bumping is counter-productive for bug reports as the devs have said they go through them in oldest-to-newest order, so bumping actually keeps them from seeing it. Bumping threads is also bad forum etiquette (actual replies to older threads can be acceptable).

 

[Shaddarhim]

Bumping is counter-productive for bug reports as the devs have said they go through them in oldest-to-newest order, so bumping actually keeps them from seeing it. Bumping threads is also bad forum etiquette (actual replies to older threads can be acceptable).

Since they ignore this issue since release what do you suggest doing instead?

 

[CaesarVincens]

Since they ignore this issue since release what do you suggest doing instead?

I suggested a fix in my own report about this issue

 

[Shaddarhim]

I suggested a fix in my own report about

I suggested a fix in my own report about this issue

Good to know that I'm not the only one being ignored. I guess multiplayer isn't on their priority list.

 

[SAS]

"bumping" a thread is also a violation of the forum CoC. Like others have said it is actually counter productive since a lot of the time bug reports often get looked at oldest post first. Also no dev. comment does not mean it hasn't not been seen.

What I suggest, for a bug you feel is long standing, is after each patch, name the patch and say the issue remains, maybe a new save if you have it.

 

[Shaddarhim]

"bumping" a thread is also a violation of the forum CoC. Like others have said it is actually counter productive since a lot of the time bug reports often get looked at oldest post first. Also no dev. comment does not mean it hasn't not been seen.

What I suggest, for a bug you feel is long standing, is after each patch, name the patch and say the issue remains, maybe a new save if you have it.

okay won't bump again. it's just frustrating when bugs are being ignored that have been around for a very long time, are easy to fix hand have been reported several times. Would be nice if you could add it to the known bugs. The main mp group I play in has this event disabled with a mod so it isn't an issue there but other groups don't have a fix. So the event basically ends your game if you play as Japan, DEI or other Nations in the affected HQs. (we had to end the session early and make a save-edit) The recent changes to devastation also increased the pain the event causes by a ton.