I've had issues with the Great Depth Worm ("Worm Boss") not spawning normally in my current world (1500+ days, created before 'Depths of Duplicity' update)
I have set Worm Boss spawn chance to 'Always' in world customization, and through testing, I've found that the boss only spawns if I stay underground through 2 consecutive depth worm waves in the same game session. If I go back to the surface or just exit the world, then the next depth worm wave will always just have normal depth worms.
I've had exactly 1 normal encounter with Worm Boss in this current world shortly after Depths of Duplicity was released, but it has never managed to spawn normally ever since.
This doesn't occur in a newly created world. I set Worm Boss spawn rate to 'always' in this world, and the boss successfully spawns at every periodic depth worm wave, even if i exit and reenter the caves or switch character at a Celestial Portal.
(EDIT) I've tested a few things, and here's what i have found:
-The issue occurs on ANY world, regardless of play time or when it was created
-Exiting and reentering the caves doesn't actually cause the issue, it seems to only happen after exiting the server entirely.
TL;DR Exiting the server causes the next depth worm wave to always contain normal worms, and encountering the worm boss requires sitting through at least 2 consecutive depth worm waves in one session, even with 'Always' setting on.
(You need to play for at least 2 hours in one sitting without quitting the server to encounter the Great Depth Worm. No wonder why people find this thing is so rare)
1. Play a world and enter caves, then exit and reenter the server that was created before the 'Depths of Duplicity' update/[Game Update] - 631099
2. Set 'Great Depth worm' spawn chance to 'always' in world customization settings
3. Stay underground and witness how it takes 2 depth worm waves without exiting the world, before the Worm Boss appears
4. For comparison: create a new world after 'Depth of Duplicity', with Worm Boss spawn set to 'Always', and witness how it successfully spawns every wave.
-
5
-
3
-
1
-
1
A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now