-
Bug
-
Resolution: Fixed
-
Minecraft 18w03b, Minecraft 18w05a, Minecraft 18w06a, Minecraft 18w07a, Minecraft 18w07b, Minecraft 18w07c, Minecraft 18w08a, Minecraft 18w08b, Minecraft 18w09a, Minecraft 18w10a, Minecraft 18w10c, Minecraft 18w10d, Minecraft 18w11a, Minecraft 18w14b, Minecraft 18w15a, Minecraft 18w16a, Minecraft 18w19a, Minecraft 18w19b, Minecraft 18w20a, Minecraft 18w20b, Minecraft 18w20c, Minecraft 18w21a, Minecraft 18w21b, Minecraft 18w22a, Minecraft 18w22b, Minecraft 18w22c, Minecraft 1.13-pre1, Minecraft 1.13-pre2, Minecraft 1.13-pre3, Minecraft 1.13-pre4
-
Confirmed
The bug
When disabling a datapack in the nether or the end, the datapack doesn't get disabled. This happens when you either change the execution dimension with execute in ... run datapack disable <pack> to the nether or the end, or if you're are already in one of those dimensions and run datapack disable <pack>
How to reproduce
- Open a world (which has the vanilla datapack enabled) and make sure you're in the overworld:
/execute in the overworld run teleport @s 0 0 0
- Run either one of these commands and it will not disable the vanilla datapack:
/execute in the_nether run datapack disable vanilla /execute in the_end run datapack disable vanilla
- Check what datapacks are enabled
/datapack list
→ as you can see, the vanilla datapack is still enabled
- Teleport to the nether or the end
/execute in the_nether run teleport @s 0 0 0 /execute in the_end run teleport @s 0 0 0
- Disable the datapack
/datapack disable vanilla
- List all the datapacks
/datapack list
→ the vanilla datapack is still enabled
