MC-93960LeashKnot Location Selectors are Incorrect
I summoned a leash knot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leash knot seems to be incorrect. The nbt data of the leash knot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - "The search area is being chopped up into a quarter of what it's supposed to be. See the attached image...The location of the Leash knot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are incorrect."
To test:
- Summon a leash knot. Summon it on a fence to keep it in existence.
- Walk up to it and run
/execute if entity @e[type=leash_knot,distance=..5] - Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leash knot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
- Run /data get on the leash knot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
- Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leash knot to see that it does indeed run from the correct location.
My results:
Leash knot location: 0 60 0
Leash knot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}
First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]
I determined that the position it was finding must be under y=60, however checking down below vertically from the leash_knot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
Code analysis
The following is based on a decompiled version of Minecraft 1.9 using MCP 9.24 beta.
The reason for this is very likely that the method net.minecraft.entity.EntityLeashKnot.updateBoundingBox() which overrides the method of its parent class does not set the bounding box but only sets the position. Because of this, summoned LeashKnot s have their bounding box at 0|0|0.
Attachments1
![[Mod] Skylinerw](../../../data/assets/gravatar/skylinerw.png){kind=small}
- Unresolved
Onnowhere- 22
- 12
- Community Consensus
Normal- Platform
- Commands
15w49b - 1.16.4
15w49b 15w50a 15w51b 16w03a 16w04a 16w05a 16w05b 16w06a 16w07a 16w07b 1.9-pre1 1.9-pre2 1.9-pre3 1.9-pre4 1.9 1.9.1-pre1 1.9.1-pre2 1.9.1-pre3 1.9.1 1.9.2 1.9.4 16w21a 1.10-pre2 1.10 16w39c 1.11 1.11.2 17w15a 17w16a 1.12-pre2 1.12 1.12.1 1.12.2 17w48a 17w49b 1.13.2 18w50a 1.14-pre3 1.15-pre2 1.15-pre4 1.16.4-rc1 1.16.4
Created Issue:
Leashknot Location Selectors are Incorrect
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect.
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again. In my first test, I finally was able to find it at radius = 60. I haven't been able to pinpoint the exact location the bugged selector is finding.
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again. In my first test, I finally was able to find it at radius = 60. I haven't been able to pinpoint the exact location the bugged selector is finding.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again. In my first test, I finally was able to find it at radius = 60. I haven't been able to pinpoint the exact location the bugged selector is finding.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location still.
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again. In my first test, I finally was able to find it at radius = 60. I haven't been able to pinpoint the exact location the bugged selector is finding.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location
still.
Leashknot Location Selectors are IncorrectLeashKnot Location Selectors are Incorrect
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again. In my first test, I finally was able to find it at radius = 60. I haven't been able to pinpoint the exact location the bugged selector is finding.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius findable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again. In my first test, I finally was able to find it at radius = 60. I haven't been able to pinpoint the exact location the bugged selector is finding.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius
findable while standing at 0 60 0: 60/testfor @e[type=LeashKnot,r=60]I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again. In my first test, I finally was able to find it at radius = 60. I haven't been able to pinpoint the exact location the bugged selector is finding.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again. In my first test, I finally was able to find it at radius = 60. I haven't been able to pinpoint the exact location the bugged selector is finding.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]Radius seems to correspond with y value. I determined that the position it was finding must be under y=60, however checking down below vertically from the leashknot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again.
In my first test, I finally was able to find it at radius = 60. I haven't been able to pinpoint the exact location the bugged selector is finding.4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]Radius seems to correspond with y value. I determined that the position it was finding must be under y=60, however checking down below vertically from the leashknot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
It appears that the selector is cutting y values in half, so that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leashknot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]Radius seems to correspond with y value. I determined that the position it was finding must be under y=60, however checking down below vertically from the leashknot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
It appears that
the selector is cutting y values in half, so thatif the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leashknot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]
Radius seems to correspond with y value.I determined that the position it was finding must be under y=60, however checking down below vertically from the leashknot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - The radius search range seems to be cut into a quarter of what it should be.
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leashknot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]I determined that the position it was finding must be under y=60, however checking down below vertically from the leashknot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - The radius search range seems to be cut into a quarter of what it should be. The location of the LeashKnot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are incorrect.
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leashknot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]I determined that the position it was finding must be under y=60, however checking down below vertically from the leashknot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - The
radius search range seems to be cut into a quarter of what it should be.The location of the LeashKnot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are incorrect.To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leashknot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]I determined that the position it was finding must be under y=60, however checking down below vertically from the leashknot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - "The search area is being chopped up into a quarter of what it's supposed to be. See the attached image...The location of the LeashKnot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are" incorrect.
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leashknot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]I determined that the position it was finding must be under y=60, however checking down below vertically from the leashknot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - "The search area is being chopped up into a quarter of what it's supposed to be. See the attached image...The location of the LeashKnot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are
"incorrect.To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leashknot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]I determined that the position it was finding must be under y=60, however checking down below vertically from the leashknot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - "The search area is being chopped up into a quarter of what it's supposed to be. See the attached image...The location of the LeashKnot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are incorrect."
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leashknot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]I determined that the position it was finding must be under y=60, however checking down below vertically from the leashknot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
![[Mod] redstonehelper](../../../data/avatars/users/10122.svg){kind=small}
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - "The search area is being chopped up into a quarter of what it's supposed to be. See the attached image...The location of the LeashKnot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are incorrect."
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leashknot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]I determined that the position it was finding must be under y=60, however checking down below vertically from the leashknot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
![[Mojang] Searge (Michael Stoyke)](../../../data/assets/gravatar/searge.png){kind=small}
[Mojang] Searge (Michael Stoyke)
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - "The search area is being chopped up into a quarter of what it's supposed to be. See the attached image...The location of the LeashKnot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are incorrect."
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and /testfor @e[type=LeashKnot,r=5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leashknot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]I determined that the position it was finding must be under y=60, however checking down below vertically from the leashknot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
Code analysis by Marcono1234 can be found in this comment.
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
[Mojang] Searge (Michael Stoyke)![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - "The search area is being chopped up into a quarter of what it's supposed to be. See the attached image...The location of the LeashKnot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are incorrect."
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and
/testfor@e[type=LeashKnot,r=5]3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leashknot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
I determined that the position it was finding must be under y=60, however checking down below vertically from the leashknot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
Code analysis by Marcono1234 can be found in this comment.
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - "The search area is being chopped up into a quarter of what it's supposed to be. See the attached image...The location of the LeashKnot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are incorrect."
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and run /execute if entity @e[type=leash_knot,distance=..5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leashknot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]I determined that the position it was finding must be under y=60, however checking down below vertically from the leashknot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
Code analysis by Marcono1234 can be found in this comment.
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - "The search area is being chopped up into a quarter of what it's supposed to be. See the attached image...The location of the LeashKnot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are incorrect."
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and run /execute if entity @e[type=leash_knot,distance=..5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leashknot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]I determined that the position it was finding must be under y=60, however checking down below vertically from the leashknot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
Code analysis by Marcono1234 can be found in
this comment.I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - "The search area is being chopped up into a quarter of what it's supposed to be. See the attached image...The location of the LeashKnot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are incorrect."
To test:
1. Summon a Leashknot. Summon it on a fence to keep it in existence.
2. Walk up to it and run /execute if entity @e[type=leash_knot,distance=..5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leashknot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
LeashKnot location: 0 60 0
LeashKnot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]I determined that the position it was finding must be under y=60, however checking down below vertically from the leashknot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
Code analysis by Marcono1234 can be found in this comment.
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
I summoned a leashknot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leashknot seems to be incorrect. The nbt data of the leashknot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - "The search area is being chopped up into a quarter of what it's supposed to be. See the attached image...The location of the Leash
Knot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are incorrect."To test:
1. Summon a
Leashknot. Summon it on a fence to keep it in existence.2. Walk up to it and run /execute if entity @e[type=leash_knot,distance=..5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leashknot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leashknot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leashknot to see that it does indeed run from the correct location.
My results:
Leash
Knot location: 0 60 0Leash
Knot data:{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]I determined that the position it was finding must be under y=60, however checking down below vertically from the leashknot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
Code analysis by Marcono1234 can be found in this comment.
I summoned a leash knot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leash knot seems to be incorrect. The nbt data of the leash knot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - "The search area is being chopped up into a quarter of what it's supposed to be. See the attached image...The location of the Leash knot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are incorrect."
To test:
1. Summon a leash knot. Summon it on a fence to keep it in existence.
2. Walk up to it and run /execute if entity @e[type=leash_knot,distance=..5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leash knot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leash knot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leash knot to see that it does indeed run from the correct location.
My results:
Leash knot location: 0 60 0
Leash knot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]I determined that the position it was finding must be under y=60, however checking down below vertically from the leash_knot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
Code analysis by Marcono1234 can be found in this comment.
I summoned a leash knot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leash knot seems to be incorrect. The nbt data of the leash knot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - "The search area is being chopped up into a quarter of what it's supposed to be. See the attached image...The location of the Leash knot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are incorrect."
To test:
1. Summon a leash knot. Summon it on a fence to keep it in existence.
2. Walk up to it and run /execute if entity @e[type=leash_knot,distance=..5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leash knot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leash knot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leash knot to see that it does indeed run from the correct location.
My results:
Leash knot location: 0 60 0
Leash knot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]I determined that the position it was finding must be under y=60, however checking down below vertically from the leash_knot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
Code analysis by Marcono1234 can be found in
this comment.I summoned a leash knot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leash knot seems to be incorrect. The nbt data of the leash knot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - "The search area is being chopped up into a quarter of what it's supposed to be. See the attached image...The location of the Leash knot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are incorrect."
To test:
1. Summon a leash knot. Summon it on a fence to keep it in existence.
2. Walk up to it and run /execute if entity @e[type=leash_knot,distance=..5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leash knot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leash knot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leash knot to see that it does indeed run from the correct location.
My results:
Leash knot location: 0 60 0
Leash knot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]I determined that the position it was finding must be under y=60, however checking down below vertically from the leash_knot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
Code analysis by Marcono1234 can be found in this comment.
I summoned a leash knot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leash knot seems to be incorrect. The nbt data of the leash knot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - "The search area is being chopped up into a quarter of what it's supposed to be. See the attached image...The location of the Leash knot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are incorrect."
To test:
1. Summon a leash knot. Summon it on a fence to keep it in existence.
2. Walk up to it and run /execute if entity @e[type=leash_knot,distance=..5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leash knot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leash knot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leash knot to see that it does indeed run from the correct location.
My results:
Leash knot location: 0 60 0
Leash knot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]I determined that the position it was finding must be under y=60, however checking down below vertically from the leash_knot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
Code analysis by Marcono1234 can be found in this comment.
I summoned a leash knot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leash knot seems to be incorrect. The nbt data of the leash knot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - "The search area is being chopped up into a quarter of what it's supposed to be. See the attached image...The location of the Leash knot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are incorrect."
To test:
1. Summon a leash knot. Summon it on a fence to keep it in existence.
2. Walk up to it and run /execute if entity @e[type=leash_knot,distance=..5]
3. Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leash knot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
4. Run an entitydata on the leash knot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
5. Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leash knot to see that it does indeed run from the correct location.
My results:
Leash knot location: 0 60 0
Leash knot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]I determined that the position it was finding must be under y=60, however checking down below vertically from the leash_knot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
Code analysis by Marcono1234 can be found in
this comment.I summoned a leash knot, walked into it and tested for it in a small radius, however it failed to show up. Testing it at a much larger radius, it does end up showing up. Using execute at it to summon an entity results in the entity appearing in the correct place as expected, and only the location selectors like radius or x y z dx dy dz on the leash knot seems to be incorrect. The nbt data of the leash knot shows the same location as it is visually as well.
It appears that if the knot is at 0 180 0, the location where it will search for it is 0 90 0. If you search for a leash knot at 0 180 0, the minimum radius will be the same as the y value so 180. If you search for a leash knot at 0 90 0, the minimum radius will be half the y value so 90. Any radii under 90 cannot find the knot anywhere in the world.
From Skylinerw - "The search area is being chopped up into a quarter of what it's supposed to be. See the attached image...The location of the Leash knot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are incorrect."
To test:
- Summon a leash knot. Summon it on a fence to keep it in existence.
- Walk up to it and run
/execute if entity @e[type=leash_knot,distance=..5]- Keep increasing the radius until you can find it again. This radius should correspond with the knot's y value. Use the radius you found, and drop down half that distance and then check in that exact spot for a leash knot in half the radius you found. Decreasing the radius below that will no longer yield results no matter where in the world you are.
- Run /data get on the leash knot to check the return feedback and notice that the position in its tags is still in fact correct to its actual location.
- Run an execute command to, for example, summon an entity at it or say the entity that is in a radius of 2 from it on the leash knot to see that it does indeed run from the correct location.
My results:
Leash knot location: 0 60 0
Leash knot data:
{Motion:[0:0.0d,1:0.0d,2:0.0d],FallDistance:0.0f,UUIDMost:-1629746060546258151L,Pos:[0:0.5d,1:60.5d,2:0.5d],UUIDLeast:-6959631846312418399L,Fire:0s,Invulnerable:0b,Air:0s,OnGround:0b,Dimension:0,PortalCooldown:0,Rotation:[0:0.0f,1:0.0f]}First radius searchable while standing at 0 60 0: 60
/testfor @e[type=LeashKnot,r=60]I determined that the position it was finding must be under y=60, however checking down below vertically from the leash_knot with different radius yielded ever more confusing results. r=60 only returned results while I was between y=0 and y=60, but not below y=0 nor above y=60. Checking r=30, I found it only detectable when I was at EXACTLY y=30. I could not get any results below r=30. It seems that radius check is scaled by half on the y axis and it thinks the knot is at y=30 and when you are at 0 30 0, it runs the r=30 as if it was checking r=0.
Code analysis
The following is based on a decompiled version of Minecraft 1.9 using MCP 9.24 beta.
The reason for this is very likely that the method net.minecraft.entity.EntityLeashKnot.updateBoundingBox() which overrides the method of its parent class does not set the bounding box but only sets the position. Because of this, summoned LeashKnot s have their bounding box at 0|0|0.
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
Wow, that is indeed really weird.
Try posting an image/screenshot of this bug. Need not reply.
Why would this need a screenshot? It's just a leashknot on a fence =p
By screenshot I mean if you type /entitydata @e[type=LeashKnot] {} and post the screenshot of the text in your chat after typing the command.
Sorry for late responce, but now I see that is the problem. Thanks for detailed explanations and testing!
Confirmed for
Leashknots are entities and why aren't they saved? Please help on this.
The LeashKnot is meant to be deleted if no mobs were connected to it. Seems to be a different but related bug; attaching a mob to a fencepost manually and killing the mob does not delete the LeashKnot entity (remaining until the world is reloaded). As long as there's a mob connected to the LeashKnot, you can detect the location just fine.
As far as this bug goes, I can confirm that there's an issue with targeting the LeashKnot, but not that it's Y-specific. The search area is being chopped up into a quarter of what it's supposed to be. See the attached image.
I used a /testfor on a clock, checking if there was a LeashKnot within 20 blocks of me, followed by a /setblock if the /testfor was successful. The location of the LeashKnot is correctly centered, but we're only seeing the result of a quarter of the search area, giving the illusion that the coordinates are incorrect.
No Name1 stop trolling
Ok, so where can I post my new commands? They are inportant (one of them is painting spawner).
Anyone? .
Minecraft forum for example, but the ones that crash, warn people before using them
Ok, I'll do it! Thanks! .
Please link to this comment in the description
The following is based on a decompiled version of Minecraft 1.9 using MCP 9.24 beta.
The reason for this is very likely that the method net.minecraft.entity.EntityLeashKnot.updateBoundingBox() which overrides the method of its parent class does not set the bounding box but only sets the position. Because of this, summoned LeashKnot s have their bounding box at 0|0|0.
Can confirm also for 1.12.2. This is an annoying bug, because in a command system I'm making I use leash knots for centering entities on a block.
Is this still a issue in the latest version of the game(currently 1.13.1)?
If so, please add it to the affected versions, thanks!
Confirmed up to latest snapshot 18w50a
Is this still an issue in 1.16.3 or later?
Yes this is still an issue.