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.
@payonel
Yep, that works. I forgot to fix the pad null reload fix in the latest 'bugfix release', although I did fix the massive bug (blocks of the same type acting as teleport pad progressors).
As you have suggested, a one way teleport pad can be created by making the pad material something different when the second pad is created. This is the reason behind the fact that not any block can be used as a telepad. This also allows for more freedom when creating telepads. Time for a new bugfix release for that simple-to-fix null pointer exception.
@angelofdev
one solution is to create 4 pads for the purpose of 2 (i.e. one teleport path) A<->B, C<->D, but your users will only go A->B and C->D. Consider that A and D are right next to each other, as are B and C. But you'll break the link from B to A and D to C....
After creating the 4 pads, physically break the blocks of B and D, and replace them with non-pad type blocks. Your pad config still teleports you there, but the block type is wrong when you arrive so you won't get pulled back.
@The24man
That null is because you've not defined any pads yet. it doesn't crash the plugin nor the server, he needs to check for empty first. he knows about it.
I'm not sure if anyone else is having this issue, but when exiting any telepads on my server, the players always come out facing the +z (south I think?) direction. Is that a bug or is that the way it's supposed to work? It'd be nice if when naming the telepad the direction one was facing was saved.
@1oglop1
for me it is working :D using 1.1
@The24man
this is third plugin of the same type today and it doesn't work either :(
This plugin looks great, especially from the comments, but when I start my server it throws a NullPointerError when it in enabled.
Thank you for making this plugin, I look forward to using it.
This plugin runs great on my server! I have 1.4.1 btw. Suggestion: Before, on other versions, could you add on option to disable the 3 sec message? I know right now theres an option 2 config the time. Default:3 How about disabling it competely?
Thanks
Players are just teleporting back cause they can't get off the pads when chunks are loading slowly. Right now its not good for long distance teleportation. But is fantastic for short distances
@wizzledonker
I thought I read that "This plugin uses the default bukkit permissions (SuperPerms)" - and I thought that SuperPerms is now part of craftbukkit (no plugin needed). Ergo, I'm not using any additional plugin for permissions.
@payonel
Thanks for reporting all those bugs, I am most interested in the teleport timing bug, as that bug is pretty large in scale yet easy to fix. In other news, which permissions plugin are you using for permissions? I have tested this plugin with groupmanager and permsbukkit, and both the plugins supported the plugin.
Hope to get back to you soon
Also, I can only get my op to create pads. Is there special syntax to the telepads.* files?
echo payonel > telepads.create
echo payonel > telepads.link
[then in game]
/createpad test0
> You do not have permission to create a pad
[from server]
op payonel
[from game]
/createpad test0
Success ....
Is <comments> your preferred method of reporting bugs/issues/feature requests? Let us know otherwise.
I believe I found a bug. If are standing on the pad block type, but not a pad, you are still teleported. Imagine your block type is grass, you run over a real pad but continue running on grass. In 3 seconds, whoop!
how about a block protection?
only people with the perm. can break the telporter
Hey, I cant seem to get the command lph to work Other than that it works awesome. :D
And also i was wandering actually how hard it would be to make it so that mobs like creepers and zombies got teleported as well, when they were to stand on it. Cause what im trying to to do is combine a teleportation system with a monster spawner. haha.
Yay :) THX
And can you do so we can add a title to the user to? :)
For anyone having trouble with config file reloading with the new version,
@addemod
Sounds like a good idea, top of my to-do list.
/padlist and other comands doesent work. I use telepads-1.4 and CB 1.1-R1, the just appear in chat and nothing happens.
Can you do a config file per teleporter and so we can add permissions to that user that don't have these permissions? Like if I have a teleport named, Cool it will create a folder named cool and a cool.yml inside there, then we can add:
Add the permissions you want that user to get when step on the teleporter
Permissions:
- 'commandbook.spawn'
Do you get what I mean?
Great plugin!
If you destroy a telepad block it doesn't actually destroy the telepad. Replace the block and its still there. I would expect that destroying the physical block would destroy the telepad. Just an observation.