mojira.dev

Antonio Knapp

Assigned

No issues.

Reported

MC-236683 Resources.zip wont load Cannot Reproduce MC-219079 World border color depends on fog color; hard to see it at night Duplicate MC-180027 Maps generate incorrectly Duplicate MC-164662 Functions permanently unload, cant be loaded again. Invalid MC-155028 flowing_water is not registered as a block correctly Duplicate MC-151266 Grass breaking sounds weird Invalid MC-145318 Minecarts cannot go around turns Duplicate MC-88339 command block gui doesnt open after death Duplicate MC-88338 cubic target selection functions improperly Invalid MC-59432 Bookshelf Has Missing Texture Duplicate MC-49623 /setworldspawn behaves like old multiplayer spawn Works As Intended MC-49621 /spawnpoint command seems to require a bed Cannot Reproduce

Comments

seems to work fine in 1.19+ but I was doing everything right in older versions, even placing resources.zip directly in the world's root folder. weird. guess that means its solved now though. 

yes, this is still an issue in 1.18.2. this site wont let me change the bug's version to any 1.18 version oddly....

i dont need any assistance. like i said, even after correcting the mistake (and again, it worked as a normal resource pack even before I fixed my mistake.)

 

its still not working when I fix it. this is a bug, not a user error.

@Little X

the issue persists even after correcting the pack.mcmeta. (worth noting again that it worked when manually loading the pack as a normal resource pack, even before "correcting" it.)

if this is intended, then explain how we're supposed to use fill commands and stuff? specifically executing if fluid?

I was trying to make a tunnels/roads data pack allowing the easy creation of roads and tunnels, but was hindered by the complete inability to replace flowing water with glass (but only normal water for some reason. that's not very consistent. that's why it is being reported as a bug. it doesn't look intentional and nobody likes that.)

why is it intended like that? it has been working in my expected way for several versions now. (actually, it's been that way pretty much since the /setworldspawn command was added, however long that is.)

i really think it would be more useful for map-making for the worldspawn to be exact, so that i don't have to build a big square area around the spawn just to make sure the players don't spawn outside my map's starting area.