Can confirm for 23w07a and all 1.19.4 Pre Releases so far (1, 2, and 3)
Can confirm for 1.15.X and all 1.16 snapshots and pre-releases as of 1.16-Pre5
That did fix it but ive had it work fine in older versions before with the pack.png file included like in 1.12.X and 1.13.X
Ive added the crash report
still happens in 18w03a and 18w03b
I'm confused too now i just made a new world and doesn't happen and i tried making a world in 1.12.2 and updating the world to the snapshot and still nothing vary weird...
ok then it's a valid bug was just double checking
Is this a new world or a world you had for a long time? being from alpha or beta. if so it's because the world save format change in beta and again in release meaning they wont fix it
so your saying by the full releases this shouldn't happen. or is this only happen for me?
ok I added the file i think thats the right one. also I found that this only happens in worlds updated from 17w50a but if you create a new world its fine
ok thanks! for the help.
ok how do i use this "minecraft:tick" with functions then to replace the gamerule?
ok thanks is the "minecraft:tick" placed in a advancement trigger? just to make sure im understanding it right
Confirmed for 17w50a
There are only 2 tags right now #planks and #wool but you can make custom ones for the doors and buttons
ok thanks! that seem dumb and useless then how that is.
I just test the ..5 it works but what i put up before is still true as even when i went exactly 5 blocks away it did not trigger
Change the pack_format to 4 from 1 and do /gamerule gameLoopFunction teleport as you don't have the teleport file in a folder call "custom" if you want it to be like how you have it make the files lad out like "data/custom/functions/custom/teleport"
This is how it's is in 1.13 if you hold down Shift then the chest will not connect, place a block behind or next to where you want to place it then click on the block instead of the chest on the bottom.
Thanks for the clarification on the issue. MC-101556 wasn’t mentioned anywhere in the 25w04a or later snapshot changelogs as being fixed so i wasn’t sure if it was intended or not.