@tspierer2 Thanks for this list! This is something you can work with 1. The command Shares the cooldown with the signs. Cooldown can be set in the config (but in seconds, I was too lazy. And you have a calculator ) Command warmup. Duration changable in the config. Moving cancels it. Looking around is fine. Cooldown will be added if the user successfully teleported. 2. The signs I kept the original signs. Meaning: You can change the parameters (radius for circle mode, minX, maxX, minZ, maxZ for cubic) for EVERY sign Signs share a cooldown with the command and every other sign Creation is a bit more complex (explained in one of my last posts, hasn't changed) You can also just write the first line, to use the settings from the config.yml. Makes it easier for you Signs WON'T update their parameters if you change the config. Only new ones will. The command will change after a reload/restart. Signs text is configurable and also lists the radius and stuff in the default config. You can change that too, of course. The key for the sign is typing "WILD TP" in the first line. And having the permission "wildTp.create". Using doesn't require a permission. Nor does the command. 3. Config All of your options (at least I think so, point missing things out!) and some more Blocks to avoid is not with ids. Ids were deprecated for quite some time. New system is names. The source for the names is linked in the config Signs will update their text to match the config every reload/restart. Avoid faction land is not implemented. If I find interest, I might do it. No promises though. You can change the radius and other things for the teleportation in the config. Change "teleportation object type" to the type. Explained in config.yml "teleportation object string". Format is explained in the config.yml too. The same as the signs "max iterations for block finding". The block to teleport to is chosen randomly. If the block is not valid (a blocked material), a new one will be searched. To protect the server from crashing, because no block is valid, there is a maximum of tries it will do. If it can't find a block within this number, the user will receive an error message and the cooldown won't apply. You may want to increase this, but beware of too high numbers. Not all messages are configurable. The rest should be explained sufficiently in the config.yml. If you have any questions or find any bugs, ask! Link: dropbox. Source should be packaged within it, if you are interested or somebody else wants to continue it later. It isn't that nice though, as I didn't rewrote all of it after you clarified yourself. So you might simply want to totally rewrite the plugin if it will be needed.