[Suggestion]: Server config option or entity NBT to prevent the Wither Storm from spawning segments
sm644me opened this issue ยท 4 comments
Guidelines
- By checking this box, I am saying that I have read the guidelines and believe to be following them to the best of my ability
Description of feature request
I think the title summarizes this well enough. A server config option, disabled by default, that prevents phase 6+ from spawning Wither Storm Segment entities. Other behavior, like the bowels tunnel in phase 7.5, would remain the same, there would just be no segments. This could also be done with entity NBT, like the OtherHeadsDisabled
NBT meant for phase 6 but that also works on other phases.
The segments and the chaos they create is iconic to both the original Story Mode and CWSM. But CWSM has plenty of features that a datapack or modpack or even just a semi-casual player can use to mess with progression in bizarre ways. For example, the /witherstormmod phase evolve @w force
command. That last argument, force
, is used specifically to move phase 5.5 into 6 by skipping the Formidibomb sequence. This indicates to me that the developers anticipate user creations that don't need the Formidibomb.
If the Wither Storm is never exploded, it might be weird to have segments exist. Or maybe a user might want to have the Wither Storm explode but say that those segment chunks were fully destroyed and that the Wither Storm needs more time to heal. I don't know exactly, but it seems like a neat option to have that (hopefully) wouldn't be too much work. Or maybe I'm wrong and this would actually be unreasonably complicated to implement. That tends to happen with programming.
Something like that, yeah. Both entity NBT and server config settings are easy to edit with commands now (thanks so much for that Crackers), so I think the method of implementing it should come down to which setting is easier to code in.
Wouldn't be hard to do. I'll probably make it an NBT tag so it's independent for each Wither Storm