-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
None
Using the setSearchRadius function on a TravelAgent throws no errors and will return the expected values when checking but the actual behavior when finding a nether portal still follows the vanilla defaults. Tested this on 1.9 and on 1.8 CraftBukkit and Spigot builds and all have the same problem. 1.7 builds are fine however.
Eventually found the likely cause in the NMS PortalTravelAgent method findPortal(). At some point a few lines got left out of patching and remain hard-coded to the Minecraft default of 128 instead of passing the correct search radius:
BlockPosition blockposition = new BlockPosition(x, y, z); // CraftBukkit for (int l = -128; l <= 128; ++l) { BlockPosition blockposition1; for (int i1 = -128; i1 <= 128; ++i1) {