mojira.dev

Tim L.

Assigned

No issues.

Reported

MC-84682 Graphical glitch when shooting between the gap between End Rods Duplicate MC-46124 Target selectors grab things in the wrong area without radius. Works As Intended MC-45197 @p arguments not working with cubic areas. Duplicate

Comments

@Ezekiel perhaps it was only the @p selector then? But what Anon Ymus said makes more sense. It wasn't listed in the change logs, so i didn't thing it changed.

@Ezekiel As I stated in my comment before the last, the behavior worked without a given radius in 1.7.4, therefore this is a bug. Unless it was added that a radius was required and not put on the changelogs.

@Ezekiel But why doesn't it work without a radius in the snapshots like it does in 1.7.4? I've tested this so much I know I'm not wrong on this...

@Anon Ymus I tested the same behavior in 1.7.4, and without setting a radius, it worked correctly. It found me in the block when i set just @p[x,y,z]

@Anon Ymus No, that's not how it works. At the point i provided, it should look for someone AT that point. Like there is a radius of 0. And either way, it would be a bug that it finds everyone at every point without a radius given.

I had this same problem. Except instead of running into unbalanced quotation, i had mine run into an unbalanced brackets error when doing lore. I hope this is fixed before thursday.

@CubeTheThird so it was just a noobish mistake... i figured the dx etc. were the coords to go to, like in my example, I went from -6 to -1, but instead i'd do 5 there, etc.

Thanks for the help, man.

@CubeTheThird But wouldn't that be a bug then? I read the comments in the other report and I see that I could replace -1 with 1 in dx, but that's not the same area. I actually wouldn't be able to define that area because of something in the map.