Take the 2-minute tour ×
Arqade is a question and answer site for passionate videogamers on all platforms. It's 100% free, no registration required.

I set a command block to /tp. It was supposed to activate only if you had 0 time left, and to activate the command block with a hopper clock to keep giving it power.

But it is not checking if you have 0 time left, so it keeps teleporting me. I can't get close enough to the command block to break it, so I'm stuck in a neverending teleport loop.

Any ideas?

share|improve this question

4 Answers 4

up vote 7 down vote accepted

If you are running this world on a multiplayer server, you can disable command blocks completely via the server properties. Shut down the server, open server.properties with a text editor of your choice and set

enable-command-block = false

This disables all command blocks. Join the game, destroy the command block in question and reenable them afterwards.

In singleplayer, it's a bit more complicated. You have to open the world as a multiplayer* server. Open server.properties and set

level-name = [relative path to your savegame]

e.g. saves/world (use / to divide folders).


*If you haven't run a multiplayer server yet, you can download the server.jar (or server.exe) from the Minecraft website and save it wherever you want. Run it once to generate some files, including server.properties and a savegame called world.

To join your own server, connect to localhost or 127.0.0.1 in Minecraft.

share|improve this answer
    
I think that this solution works best if you're already running a server. –  Riking Jun 2 at 9:14

For situations like this, an external world-editing tool is best. Find the command block, and delete it.

A common one is MCEdit, which is available here: http://www.mcedit.net/


As @MrLemon mentions, you could be running a multiplayer server, in which case MCEdit is a bad idea -- the download time of a 60GB map is non-negligible. In that case, follow his answer.

share|improve this answer

destroy the block using a world editor, then use a command block to comparator for the test part with the /testfor command, you want the comparator to go to a command block that just puts up a message to start with to find out if the /testfor command and comparator are working properly, do not start the /tp command until you have confirmed that the first two parts are working in conjunction with each other propperly

share|improve this answer

If the command block is not at the spawn; tpye /kill. But if one is at spawn just look down real quick and break it if you can.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.