RandomTeleporter
Description
Lightweight random teleport plugin.
Set up whole areas or single locations where players will randomly be teleport to/in.
Group teleports together and specify a sign for each one.
Adjust options to allow the teleport to caves or just the surface.
Avoid dangerous blocks like lava, cactus, etc or some other situations like spawning in midair.
This will also hook into Factions & GriefPrevention if you want and teleport to free non-claimed ('wilderness') spots.
You can even use WorldEdit selection to set up teleports.
This plugin was requested by danielfr789 here.
Features
- Add exact locations or whole areas for teleportation! (Supports WorldEdit selection.)
- Define chances for each area/location and determine how often it will be used!
- Set up a list with blocks, you don't want player to spawn on! (So noone can spawn in/upon lava!)
- Customizable user messages! With color support!
- Config file with comments and examples! Easy to understand & adjust!
- Supports teleport delay! And adjust, if it is canceled on movement/damage!
- Permission support! (Of course!)
- Bypass delay & cooldown permission nodes!
- Multiworld support!
- Teleport signs! Disable the command and use the sign instead!
- Configurable cooldown for the sign and the /rtp command.
- Multiple locations / areas per world! No Limits!
- Factions & GriefPrevention support! Option to just spawn in unclaimed wilderness of the teleport areas.
- Also an Option to avoid spawning below the surface.
- Chunk preload! don't fall in the void after teleporting!
- Config check! This will tell you if your config isn't up to date anymore.
- Sourcecode available! Just message me.
Commands
[] - optional statements
<> - variables (names / numbers)
quiet simple:
V1.30 + * /rtp teleport [<group>] * /rtp invite <player> * /rtp join <player> * /rtp reload [teleports|settings] * /rtp list [<group>] * /rtp add <teleportName> [<group>] [<chance>] * /rtp remove <teleport> * /rtp combine <teleport1> <teleport2>
Permissions
V1.30 + * randomteleporter.cmd.teleport - Gives access to the teleport command. * randomteleporter.cmd.join - Gives access to the join command. * randomteleporter.cmd.invite - Gives access to the invite command. * randomteleporter.sign.teleport - Gives access to the [RandomTP] sign. * randomteleporter.admin - Gives access to everything else. * randomteleporter.bypass.delay - Gives access to bypass the delay. * randomteleporter.bypass.cooldown - Gives access to bypass the cooldown.
DEV Version
If I extend or change the plugin in any way, there will be a development version. This may contain new bugs or cause errors.
However, it also includes all new features and bug fixes as soon as I can and they are noticed.
Dev versions will not be avaiable on bukkit (because they change really often), but they are avaiable at my CI and Blog.
Please note that only the versions of dev.bukkit were checked by moderators. And you use the development versions at your own risk.
Whats up next?
- >>
Ability to group multiple teleports together... DONE - >>
Suffocation bugfix... DONE - >>
ReCoding algotithms... DONE - >>
Worldedit area selection support... DONE - >>
ReCoding Commands... DONE - >>
Ability to follow a player to destination... DONE
working on other projects :)
- >> intuitive way to join groups ...
- >> Towny support ...
- >> Maybe your enhancement? Create a ticket, if you have great ideas to improve this!
Support Me
Because I do not speak English natively, there might be some spelling/grammar mistakes.
If you find some, please create a comment and tell me how it should be written. :)
I'll fix it as soon as possible.
If you want to donate, there is a button for this in the header.
@flip284
It doesnt for me either.
this doesnt even generate a folder on my server.
@InflamedSebi
I'm not sure exactly why that happens. You can see for yourself on the server. I haven't given any groups a bypass permission.
@deleted_9935739
i tested it on my local server. Only players with the "randomteleporter.bypass.delay" or "randomteleporter.bypass.cooldown" node can bypass ... works like it should.
@InflamedSebi
It's working for non ops too.
@deleted_9935739
thats why you are op on your server, so it will bypass the cooldown and delay ... but it will work for your players just fine ;)
@InflamedSebi
I mean that I have delay_for_tp 3 and cooldown_for_tp 30 but I don't have to wait at all now since I updated to 1.25.
@deleted_9935739
"Why is the cooldown and wait time 0 seconds when it isn't in the config?" - delay and cooldown are integers and the default value of integers is 0.
"Also, would it be possible to have a whitelist setting for area_avoid? I want to avoid all blocks except grass and snow. Or is that not a good idea?" - the teleport algorithm creates a random location from all areas. And then, there is a "valid"-Check ... if the location was at an avoid_block it will be canceld and a new location is generated (until the amount of maximum tries is reached). if the area contains enough grass / snow blocks it should be possible, but if not, your users will get the "unsafe: 'No valid spot could be found! Please tell this to an Admin!'" message. Whitelisting is not supported (yet)... you have to add all block (except snow and grass) to the avoid list ... maybe a future release will contain that feature :)
It works without any errors now, but why is the cooldown and wait time 0 seconds when it isn't in the config? Also, would it be possible to have a whitelist setting for area_avoid? I want to avoid all blocks except grass and snow. Or is that not a good idea?
@deleted_9935739
stupid spelling mistake xD fixed xD
1.25 gives me this error on startup http://pastebin.com/fTi045cD
@deleted_9935739
this was a known bug of 1.23 i missed to adjust the version xD just use 1.24 or 1.25 from my blog :) this should also fix the utf-8 bug ... so u can use colored messages and the prefix should work too.
@InflamedSebi
Thanks for the answers. I downloaded 1.23 and the config version says 1.23. Though when I type /version RandomTeleporter, it reports 1.21 (may be an error?).
@deleted_9935739 All blocknames can be found here: http://jd.bukkit.org/rb/apidocs/org/bukkit/Material.html
"There are a few places I don't want people to random tp into. How can I make it avoid a certain area?" - there is no avoid area yet ... u have to divide the areas in smaller parts and leave some of them out.
"Shouldn't the cooldown be cancelled if the player moves?" - should be fixed in 1.25.
"What tolerance should I set it at so players can still look around?" - 0.01 should be fine.
"What exactly do all the logging modes do?" - while coding i add a lot of messages to output in the console, like "Player rightclicked something" "object was a sign" and so on. This is usefull to find bugs, but its really annoying for server admins. so u can change the detail to few or normal and it will not spam all debug messages in the console.
"How can I disable the console prefix completely?" - it's to color the plugin name in the console. Just set an empty message there or remove the line completely to disable it.
"Configuration file config.yml may be outdated. This can break the plugin and cause erros! Please use a valid version of the config!"- at the top of the config is a "config_version: 1.24". if this number does not fit to the plugin version, the error will appear in the console. if the config is UTF-8 encoded and the config version is at least 1.23 u can set it to 1.24 manually.
Few more questions.
Where can I find a list of the block names to put on area_avoid. I can see most of them are just the name capitalized but I'm not sure what to put for all the kinds of leaves to avoid spawning on top of trees. I've tried LEAF, LEAVES, and OAK_LEAVES.
There are a few places I don't want people to random tp into. How can I make it avoid a certain area?
Shouldn't the cooldown be cancelled if the player moves?
What tolerance should I set it at so players can still look around?
What exactly do all the logging modes do?
How can I disable the console prefix completely?
@InflamedSebi
I removed the § from the console-nameprefix number and it works now but it shows this error "Configuration file config.yml may be outdated. This can break the plugin and cause erros! Please use a valid version of the config!". Would a fix be to only have the number in the config?
@deleted_9935739
seems like bukit still has no solution for the utf-8 bug ... so just open the config from ur server and check for all "§" or "�" chars they are causing the errors ... if there are any "�" u can replace them with "§" and it should work if there are only "§" than u have to remove all of them ...
Would you happen to know what's causing this to show when I try to load the plugin? http://pastebin.com/1tmp8eBs It seems to only happen on my main server and not when I copy it over to my local test server.
Edit: After some searching, I found it's related to utf-8 similar to the other problem below. I tried the 1.24 dev version on your blog but it says it cannot load the plugin.
@InflamedSebi
OK...I will check if v1.2.4 has been uploaded!!
@smallpen
This is a known problem, but its a problem of bukkit itself, i did some testing with the new bukkit versions ... this seems to fix the issues.
there will be version 1.2.4 soon, so check out my blog.