In Control!

In Control!

72M Downloads

Wither won't spawn, regardless of configs

hairlessOrphan opened this issue ยท 3 comments

commented

(Migration of CurseForge discussion)

Steps taken:

  1. On another install with a ton of other mods but not this one, I was able to spawn the Wither.

  2. Installed this and configured it to disallow ALL spawns ({ "result": "deny" }). The soul sand / skull multiblock would all disappear as soon as I completed it (expected behavior).

  3. I then added variants of "Wither," "wither," "minecraft:wither" and got unrecognized-mobname errors in the log (didn't know it was "WitherBoss") (expected behavior).

  4. I then added {"mob": ["WitherBoss"], "result": "default"} above the deny-all and the multiblock stopped responding entirely (not expected).

  5. I then did a fresh install and with the default (blank) configs.
    Curse Launcher 7.1.6249.2188 Beta
    MC 1.10.2
    forge 12.18.3.2221
    In Control 3.5.2
    CompatLayer 0.2.2.

  6. Booted up the game, Survival, "New World," only option I changed was enabling cheats. /gamemode 1, grab 64 soul sand and 64 wither skulls, put the block together (the skulls flash white when I place them), no wither.

  7. I uninstalled In Control and went back into this same save from 6) above, knocked out a skull and replaced it... No Wither!

  8. I uninstalled CompatLayer and tried again... No Wither!

  9. I took the whole structure (all the skulls and soul sand) down, put it back together... No Wither!

  10. I started a new game, /gamemode 1, put the multiblock together... and got the Wither.

commented

I cannot reproduce this and I double checked. There is no way for In Control to have any effect after it has been removed. It doesn't store any information. It just acts on events when mobs spawn. If In Control is not there then those event handlers are gone as well. So...

In any case I can still spawn withers just fine with In Control present. Can you still reproduce this problem?

commented

I'll give it a try this weekend. It seems super weird, right? My only guess was something was being left in some global file shared by multiple Curse launcher profiles. But I don't know anything about the file structure there, and they all seem isolated in the /instances/ folder.

commented

Still not working with the original versions (Forge 2221 and In Control! 3.5.2), but working with 3.5.4 against Forge 2221 and Forge 2239. So it seems like the mysterious problem is solved!