TelePads
Telepads v1.6
Description
^ Download for 1.6 while it is approved
Telepads is a tool which you can use to set up simple teleportation systems within your multiplayer world. You may create 'pads' which are linked and can be stepped over for simple teleportation. This plugin supports multiworld due to the awesomeness of bukkit, and how easy the bukkit API makes this. All permissions within the plugin default to operator status if they have not been assigned, but the use permission, which sets to 'true' by default... meaning any player can use the pads. To setup a teleport pad, follow the below instructions:
- Stand on platform material (defined in config file)
- Type /createpad <name>, replacing <name> with the name of the teleport pad
- Create another pad at your destination
- Use /padlink <pad> <otherpad> to link the two pads, replacing <pad> and <otherpad> with the names of your pads.
It really is that easy! Telepads was designed with easy-to-use teleportation features in mind, so this is really what it was made for!
Video, thanks so much BrandonHopkins!
Permissions & commands
Commands
- /createpad <name> Creates a teleport pad with the specified name
- /padlink <pad1> <pad2> links two teleport pads together
- /padunlink <pad> Sets the destination of a pad to be nowhere
- /delpad <pad> deletes a teleport pad.
- /padlist Lists all the available teleport pads and links
Permissions
- telepads.create Defines if a player or group can create a telepad
- telepads.delete Defines if a player can delete a teleport pad
- telepads.use Configures if a player can use teleport pads by stepping on them
- telepads.link Defines if a player can link telepads
- telepads.list Defines if a player can summon the telepad list
- telepads.pads Allow the player to use all teleport pads
- telepads.pads.<name> Allow the player to use a specified teleport pad
Sample Configuration
Below is a sample configuration file for telepads. Stick this in your telepads configuration file (plugins/telepads/config.yml) and configure it as necessary. Note that the configuration file will also automatically generate the first time you use this plugin.
# For type ID's, go to www.minecraftwiki.net/wiki/Data_values pads: properties: # Type ID of the telepad material (goto the wiki link above). type_id: 1 # Whether or not the message 'No Destination' when the pad isn't linked is enabled. nodestmsg_enabled: true # Time standing on the pad (seconds) before you get teleported. teleport_time: 3 messages: # Message when you delete a teleport pad delete: Teleport pad %pad% removed. # When you link pads, this message displays link: Successfully linked %pad% to %pad2% # The wait message, which shows before being teleported with the time it will take. wait: You will depart from here in %time% teleport: # Whether or not the teleport message is enabled enable: true # The message that appears on teleport. message: You have arrived at %pad%
Sample Permissions
TelePads has a Permission system which allows different users different ways to interact with the pads. Due to the complexity of this, here's a simple guide to configuring permissions for use alongside TelePads.
# A normal player default: permissions: - telepads.use - telepads.pads # A limited user, can only use the pad named 'spawn' limited: permissions: - telepads.use - telepads.pads.spawn # An elevated permissions user mod: permissions: - telepads.use - telepads.pads - telepads.create - telepads.delete - telepads.list - telepads.link
Future Plans
- Teleport pad random outcome/multiple exits
- Command simplification
This plugin uses the default bukkit permissions (SuperPerms). If you find only ops can do everything, then you are using an outdated permissions plugin. The plugin named 'Permissions' for example, is outdated. Post me a pm or comment if you have any issues.
@arriej
I know this sounds weird, but for now ignore that error. Once you have created a pad that error will dissapear on startup and you won't have any problems, but for now it is safe to simpy ignore the error. The problem is I havn't added any handlers (stupidly) for no pads being there, so when the plugin does not find any pads it spits out an error. Therefore, it is safe to ignore the error for now.
EDIT: And yes, I will fix this problem
i update the plugin but i get this: 2012-01-26 14:54:21 [INFO] [TelePads] Loading TelePads v1.4. 2012-01-26 14:54:21 [SEVERE] Error occurred while enabling TelePads v1.4 (Is it up to date?): null java.lang.NullPointerException at me.wizzledonker.plugins.telepads.Telepads.reloadprops(Telepads.java:195) at me.wizzledonker.plugins.telepads.Telepads.onEnable(Telepads.java:60) at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:231) at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:1057) at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:379) at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:191) at org.bukkit.craftbukkit.CraftServer.enablePlugins(CraftServer.java:174) at net.minecraft.server.MinecraftServer.t(MinecraftServer.java:356) at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:343) at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:175) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:407) at net.minecraft.server.ThreadServerApplication.run(SourceFile:4650
hoping for a fix.
tnx
Maybe I'm incorrect, but it seems that lph doesn't work at all let alone being buggy. Whenever I try it it shows no response (unless I get the pad name wrong) and says no destination at the pad I linked! On the latest version 1.4.
I am just about to release the next update.
Thanks for staying with me while I update this thing :)
Here's the new features you have all been waiting for:
Plus some optimisations and other things I havn't thought of quite yet. Feel free to post a comment if you have any other ideas for what should be improved and added in the new version of this plugin :)
@futhermukker
Going to be added in this next release :P
Is it possible to set up more than one type of block to be a teleporter block? I tried to add other blocktypes in the config but it did not seem to work. Thanks.
@andrewzhang
I implemented some methods in the new version to fix all this, I'm just having a bug squashing session over here :P
@mcvereor
I'm having the same problem. A small dent in his hell of an awesomeplugin.
@wizzledonker
Awesome! This plugin is great! Really makes my server what it is! Thanks!
@andrewzhang
Very easy to implement and definitely coming :)
Maybe a /pad list to list all pads?
@timmetalgod
This plugin should already work plug-n-play with multiworld support. Simply make teleport pads in the separate worlds and you're all set!
@fondelaar
I will make all the messages configurable in the plugin's next release.
Great plugin! works perfect on my server but how do I get it to work on multi-worlds?
thx Tim
well good work. realy cool. but could you add an command to see a list of teleporters? and how can i disable the "sucsesfully teleported to {name}" message?
thx, fondelaar
@wizzledonker
Oh, sorry for not answering your question. I'm using permissionsBukkit. Sorry, but I'm not using this plugin anymore. I coded a simple plugin with commands (such as /crea to get to the creative world) for my server, but if I can be to any help for you when you're fixing this issue, I will help you.
@MrSpider
Hmm the idea was kinda that people weren't supposed to change the config while the server is running, because the pads are also stored in the same config file. Usually, things work better if you stop the server, then edit the config, then start the server again.
In future versions I will do two things,
Thanks for reporting the issues guys, I'll get back on them.
It seems that you always get teleported to the top most block. So if your pad is in a building, you get teleported to the roof. Any plans to fix this in the future and get teleported to an approximate Y-Axis position?
GREAT!!! That helped my server! THANKS
I figured out why the config got reset here. In the plugin at onDisable there is a call to saveConfig(). The problem is if you change the configuration while the server is running and then restart the server, the configuration gets therefore reset. @wizzledonker: If u want I could make you a quick fix for it ... Or you do it yourself ;)
@ethosaurus
I have attempted to fix this issue, but superperms appears to be playing up. I'll assign permissions manually and register them manually in the next release. For now, use a permissions plugin such as PEX or bperms
How come only Op can use it? :S