Remote Accessor: Check for Correct Dimension

[Vlamonster]

Fixes potential exploits.

[Dream-Master]

@Vlamonster was there a reported issue ? If yes can you link it ?

[Vlamonster]

@Vlamonster was there a reported issue ? If yes can you link it ?

No, this fix is due to an exploit I found a couple hours ago that is quite severe.

[Dream-Master]

Ah ok

[Lyfts]

activateBlock already gets and activates the block in the world that the player is currently in, so what makes this extra check needed?

RemoteIO/src/main/java/remoteio/common/CommonProxy.java

Line 47 in 6b5a74a

Block block = proxyPlayer.worldObj.getBlock(x, y, z);

RemoteIO/src/main/java/remoteio/common/CommonProxy.java

Line 49 in 6b5a74a

block.onBlockActivated(proxyPlayer.worldObj, x, y, z, proxyPlayer, side, fx, fy, fz);

[Vlamonster]

In a test world I was able to bind a Remote Accessor to a block with coordinate x,y,z and then interact with a block at coordinate x,y,z in another dimension. This operation bypasses town claims on public servers.