Problem/Bug HOW DO I HAZ COMMAND BLOCK LOCATION

Discussion in 'Bukkit Help' started by linuxfan1, Apr 10, 2016.

Thread Status:
Not open for further replies.
  1. Offline

    linuxfan1

    Ok, my friend's server has a major problem;
    We made a command block that repeats itself, and we tped away, but now we have a problem;
    The command block is too fast, it puts another msg up just as the other one has dissapeared, the problem is, we can't find the location of the block;
    1. We have checked console
    2. We don't understand the coords it gives us
    This is where you guys come in: where do we tp to find this cmdblock?
    Output (open)
    09:20 PM [INFO] CommandBlock at 9,988,75,10,001 issued server command: /broadcast Buy Premium Rank at just 7.99! Buy at http://halirealms.buycraft.net

    Thanks in advance!
    ~ HaliRealms teams
     
    Last edited: Apr 10, 2016
  2. Offline

    teej107

    @linuxfan1 Try checking if it's at 988, 75, 10
     
  3. Offline

    linuxfan1

    Did, nothing there
    Btw, nice signature
     
    teej107 likes this.
  4. Offline

    teej107

    @linuxfan1 First things first. Is it in the spawn chunks? If it is, it would be running all the time because the spawn chunks is always loaded. You can also change the spawn chunks using a command to confirm that it is inside the original spawn chunks. If you are using WorldEdit, you could replace all command blocks in a selected area to air else you might have to use this command.
     
  5. Offline

    Lolmewn

    Please note: Your donation packages are not in line with Mojang's EULA.
     
  6. Offline

    linuxfan1

    Thanks teej107, ill check that out when I get on,
    and @Lolmewn , we'll look into changing those, thank you!
     
  7. Offline

    linuxfan1

    @Lolmewn Our server actually corresponds with the EULA. All these items can be obtained by voting and getting a crate key. Which also can be handed out in drop parties
    And I changed the spawn chunks, no luck
     
    Last edited: Apr 20, 2016
  8. Offline

    linuxfan1

Thread Status:
Not open for further replies.

Share This Page