Antonio Knapp
- tile
- tile
- America/Denver
- Yes
- No
MC-49621
i have a repeating command block pointing at a chain command block.
in the repeating command block set to unconditional and always active i use this command:
testfor @a[x=-617,y=57,z=-734,dx=-567,dy=57,dz=-694]and in the chain block set to conditional and always active i use this command:
say IT WORKSWhat i expect to happen, is when i step into the area within those coords, i want the chain block to say "IT WORKS!" repeatedly, but to stop saying it when im ouitside the area.
However, it seems to say "IT WORKS" whenever i am at y=57 regaurdless of what x and z coords im at. it stops saying it when i remove the minus sign from the front of the negative coords.
EDIT: additionally, it seems as though the repeater command block is detecting the player at any y coord at 57 and above which is not what i would be expecting
Negative coordinates are ignored incubic target selectioncubic target selection functions improperly
i have a repeating command block pointing at a chain command block.
in the repeating command block set to unconditional and always active i use this command:
testfor @a[x=-617,y=57,z=-734,dx=-567,dy=57,dz=-694]and in the chain block set to conditional and always active i use this command:
say IT WORKSWhat i expect to happen, is when i step into the area within those coords, i want the chain block to say "IT WORKS!" repeatedly, but to stop saying it when im ouitside the area.
However, it seems to say "IT WORKS" whenever i am at y=57
regaurdless of what x and z coords im at. it stopssayingit when iremove the minus sign from the front of the negative coords.EDIT: additionally, it seems as though the repeater command block is detecting the player at any y coord at 57 and above which is not what i would be expecting
i have a repeating command block pointing at a chain command block.
in the repeating command block set to unconditional and always active i use this command:
testfor @a[x=-617,y=57,z=-734,dx=-567,dy=57,dz=-694]and in the chain block set to conditional and always active i use this command:
say IT WORKSWhat i expect to happen, is when i step into the area within those coords, i want the chain block to say "IT WORKS!" repeatedly, but to stop saying it when im ouitside the area.
However, it seems to say "IT WORKS" whenever i am at y=57 and above, and seems to say it when im in an incredibly large area outside of the x and z coords i typed in.
When developing a data pack; I started to notice that the game was not recognizing a certain function at all. When i tried to execute the function via /function, the function was treated as though it didn't exist at all. I then copy/pastetheentire contents into another function that was working fine before- and now that function is suddenly not registering either.
What I expected: my function to execute.
what I got: my function doesn't seem to exist as far as the game knows, even though it is in the right folder, format, and spelling.
steps to reproduce:
- download the file attached
- extract it into a new world's data packs folder
- ...not sure from here. in my testing, this is actually a way to temporarily fix it- but once you add another function to the pack similar to the broken ones, it will fail again.
don't hesitate to reply with the needed questions! I've attached my data pack here- the offending functions are "waypoints" and "tick". "tick" only failed once I pasted the content of "waypoints" into it, as remarked by the comments. - before then, it worked fine.
MAJOR UPDATE: The below is mostly irrelevent- after some more testing trying to figure this out, it turns out that the scoreboard command is the culprit somehow; when used with execute run. i know because deleting those commands seems to make it work again somehow.
When developing a data pack; I started to notice that the game was not recognizing a certain function at all. When i tried to execute the function via /function, the function was treated as though it didn't exist at all. I then copy/paste the entire contents into another function that was working fine before- and now that function is suddenly not registering either.
What I expected: my function to execute.
what I got: my function doesn't seem to exist as far as the game knows, even though it is in the right folder, format, and spelling.
steps to reproduce:
- download the file attached
- extract it into a new world's data packs folder
- ...not sure from here. in my testing, this is actually a way to temporarily fix it- but once you add another function to the pack similar to the broken ones, it will fail again.
don't hesitate to reply with the needed questions! I've attached my data pack here- the offending functions are "waypoints" and "tick". "tick" only failed once I pasted the content of "waypoints" into it, as remarked by the comments. - before then, it worked fine.
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.
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.)
@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.)
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.
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....
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.