Destroyer Not Spawning Properly in Multiplayer on the New Update

[kindred cloud]

Playing a world with a friend, we recently completed the available bosses and reopened the world today to check out the new update content and give Boss Rush a try. We were progressing just fine, but when the Destroyer was spawned, it automatically de-spawned instantly over and over, thus not allowing the Boss Rush to continue. After giving up on fixing it and stopping the Boss Rush, I looked in this discord for anyone reporting a similar issue and came across this person (#calamity-mod-talk message) saying it did not work for them in multiplayer. Sure enough, it does not work when summoned standalone outside of Boss Rush either. The Destroyer exists for roughly a second or two, and then promptly de-spawns.

I can only assume this is a new bug, as we completed the Destroyer fight prior to this just fine.

Destroyer Not Spawning Properly in Multiplayer on the New Update

misunderstood the guidelines, my apologies, but here is the client and server logs

@dusky lodge unsure if i'm supposed to ping or not but you're the only one who reacted, just wanted to make sure someone sees that i've got the logs here and this does not remain flagged for deletion

[dusky lodge]

Cooldown and sepulcher errors

And a boss checklist one

And several Census errors on loading

And Magic storage had one

[dusky lodge]

Relevant ones are these

[kindred cloud]

cooldown for what, exactly?

the sepulcher doesn’t seem to have any errors visually that i could note, besides it not appearing for the other player when summoned

[dusky lodge]

Yes and thats spamming errors on the log

[kindred cloud]

well that does make sense i suppose

[dusky lodge]

Seems to be ascendant insignia

[kindred cloud]

ah

i forgot i had that equipped as vanity

i’m a little surprised that’s messing with the destroyer though but i can test without either in a moment if you’d want

[dusky lodge]

Multiplayer gets fucky when theres errors being spammed

[kindred cloud]

i see

[kindred cloud]

loaded the world again just now with my friend to test, did not summon the sepulcher, put away both of our ascendant insignias, destroyer still despawns exactly the same as before

relevant logs again

loaded it just now once more to be sure now that the ascendant insignias are put away and weren't on our characters at any point and it still did not work properly

[kindred cloud]

if you pick out any other relevant errors on our end it's going to be a few hours before i can troubleshoot again as i'll be away, so this is about all i have for now

[dusky lodge]

Same cooldown issue spam + a destroyer one

[kindred cloud]

i'm not sure why cooldown issue would be present this time

[dusky lodge]

Idk, maybe log into single player with your characters and then into the server?

[kindred cloud]

sure, it will be a few hours before i can try that though

i will report back here when i do

[weary geode]

Hello, we had the literal same issue trying to spawn the destroyer

I loaded into singleplayer and it spawned completely fine

then I went into multiplayer again

with only me on the server

and it instantly despawned again

uhh to be sure I'd like to mention that it has spawned before in server mode before this update like a day ago r smth and it worked fine it's only now that it's doing this

[urban sequoia]

This all seems to be linked to the cooldowns as i was having this issue with the destroyer too

[tulip prawn]

Can vouch this is happening to my friend and I as well.

[kindred cloud]

oh hey nice to see i'm not alone

[kindred cloud]

did this, didn't work either unfortunately

[dusky lodge]

:(

[kindred cloud]

spawned the destroyer in singleplayer just fine but back on multiplayer and still not working

[dusky lodge]

Just kill destroyer in singleplayer til we fix it I guess

[kindred cloud]

i mean we have for the record

we beat everything prior to the update dropping, we logged on today to try boss rush and that's when we noticed this

because it literally makes the boss rush uncompletable

so it's not the end of the world

for us anyway

[urban sequoia]

actually this gave me an idea for the other multiplayer issue

[weary geode]

there's no way to revert to last version right

[dusky lodge]

Question: does this happen if Rev is disabled?

[kindred cloud]

i’m not sure, we’ve had revengeance mode on in all of our playthroughs

we did actually start another world to kill time while this gets fixed but we’re already sort of close to the destroyer, so i suppose we could test this on that world

[orchid dragon]

^^^^^

[kindred cloud]

tested just now, same thing happens

went ahead and beat it in singleplayer for the sake of our progression, revengeance mode on it works fine