Uploaded image for project: 'Spigot'
  1. Spigot
  2. SPIGOT-300

Selectors ignore the worlds players are in

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • None
    • None

      Assuming the player to trigger this mechanism to be in the Overworld while the spawnchunks of all three vanilla worlds are being active due to players in those dimensions...

      Spigot 1.7.x and Spigot 1.8 upto about 06/Dec/2014:
      Nether mechanism: player not found
      TheEnd mechanism: player not found
      Overworld mechanism: player successfully teleported

      Spigot 1.8 (since shortly after 06/Dec/2014):
      Nether mechanism: player successfully teleported
      TheEnd mechanism: player successfully teleported
      Overworld mechanism: player successfully teleported

      So a CommandBlock using bukkit-tp in world A would also teleport a player that is in world B. This change suddenly happened shortly after 06/Dec/2014 - due to this, on my server I am still using an older and extremely badly performing build where the previous (correct) behaviour is still the case.

      In case you wanna compare it to latest builds:

      Compiled with Java8u25 on 06/Dec/2014 at 11:39 (GMT+1).

      On my server I'm trying to create as much as possible with CommandBlocks where others would use plugins. What this issue means: I'm using a Spawn teleport mechanism and also an objective that determines which world players are in. Both those things do not work properly with latest builds - Spawn teleport CommandBlocks interfere with each other and the world-detection thingy also just overwrites itself, permanently fluctuating. This is the world-detection thingy:

      Overworld: a clock doing /scoreboard objectives @a currentWorld 1
      Nether: a clock doing /scoreboard objectives @a currentWorld 2
      TheEnd: a clock doing /scoreboard objectives @a currentWorld 3

      These @a selectors used to only affect players in the world each CommandBlock is in. In latest builds, the currentWorld numbers just flip around like crazy due to the very same issue, because @a detects all players in every world everytime.

      Before this change happened, the one and only command I found to ignore dimensions was vanilla-tellraw - everything else didn't find a player if he was in a different world than the CommandBlock.

            Unassigned Unassigned
            ceagle2 ceagle2
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: