have the same issue on realms ps4. was for teleporting between main base and command room. temp workaround was have a named parrot called watcher teleporting to the coordinates constantly and for me to return home i teleported closest player to @e[name=Watcher]. have a ticking area running just to be safe.
it is definitly the command blocks are failing to target certain coordinates. for me it is currently -799 to 799 on the xcoordinate that is failing.
i think that what happens is when you put a valid command(like @p, @a etc) in it tries to process what is being asked of it, but something within that x coordinate(for me it is x) returns bogus data, and when it attempts to target, the bogus data causes the targeting to fail, resulting in it catching the error and throwing back a pre-determined response, in this case hashing the whole text input. the reason it probably needs the @a/p first is that it probably checks whether the command structure is correct first before going through the command itself.
Kyle McPherson
have the same issue on realms ps4. was for teleporting between main base and command room. temp workaround was have a named parrot called watcher teleporting to the coordinates constantly and for me to return home i teleported closest player to @e[name=Watcher]. have a ticking area running just to be safe.
it is definitly the command blocks are failing to target certain coordinates. for me it is currently -799 to 799 on the xcoordinate that is failing.
i think that what happens is when you put a valid command(like @p, @a etc) in it tries to process what is being asked of it, but something within that x coordinate(for me it is x) returns bogus data, and when it attempts to target, the bogus data causes the targeting to fail, resulting in it catching the error and throwing back a pre-determined response, in this case hashing the whole text input. the reason it probably needs the @a/p first is that it probably checks whether the command structure is correct first before going through the command itself.