TeleportSuite
TeleportSuite
Notice! I am currently very busy with both work and school. Please refrain from feature requests and only post bug reports, as I am unable to do extra work at this time.
TeleportSuite is a simple teleportation plugin which allows players to request teleports to each other with the commands /tpa and /tpahere, and accept or reject those requests with /tpaccept or /tpreject. It offers the admin type commands /tp and /tphere to teleport immediately, without a request (assuming the user is toggled to receive requests), and /tpo and /tpohere to override any user settings and teleport immediately.
By krinsdeath
Useful Stuff
- Source Code - Jenkins 1.1. Use of the plugin builds from Jenkins is unofficial, unsupported and unapproved by BukkitDev Staff!
- Default 'config.yml' file
- Default 'english.yml' localization file
- Full Command List
Features
- Very easy and very powerful commands, reminiscent of all of your favorites.
- Accept and reject all requests easily with /tpaccept -all or /tpreject -all. Use /tptoggle to immediately reject all requests.
- New! /tpm and /tpmhere for moderators: send a request from one player to another, without giving your players access to /tpa or /tpahere.
- /tpcoords will display your current location and your currently faced direction.
- Superperms support to give users any number of commands, to your taste
- Fully customizable messages for every command, including the ability to remove them altogether.
- Additional localizations are possible. Simply copy your english.yml into another file, save it as whatever.yml, and then add the language to the available list in TeleportSuite. If your system is UTF-8 capable, you can even use foreign language characters by specifying -Dfile.encoding=UTF-8 in your command line. If you've written a language file and want it included in TeleportSuite, email me or private message me.
Permissions
- Permission Node - Description. (default value)
-
teleport.* - Balloon permission to activate all others. (no default)
- teleport.tpa - Allows this user to use /tpa, to request a teleport to a user, unless their toggle status is true. (true)
- teleport.tpahere - Allows this user to use /tpahere, to request that a user teleport to them, unless their toggle status is true. (true)
- teleport.tp - Allows this user to use /tp, to telepor to a user immediately, unless their toggle status is set to true. (op)
- teleport.tphere - Allows this user to use /tphere, to teleport a user without confirmation, unless their toggle status is set to true. (op)
- teleport.tpm - Allows a user to request a /tpa on behalf of another player. (op) (bypasses teleport.tpa permission)
- teleport.tpmhere - Allows a user to request a /tpahere on behalf of another player. (op) (bypasses teleport.tpahere permission)
- teleport.tpo - Allows this user to use /tpo, to teleport to a user immediately. (false)
- teleport.tpohere - Allows this user to use /tpohere, to teleport a user to their location immediately. (false)
- teleport.location - Allows this user to use /tploc to teleport to a location. (op)
-
teleport.world - Allows this user to teleport to a world's spawn point. (op)
- teleport.world.* - Allows this user to teleport into all worlds. (true)
- teleport.world.worldname - Allows this user to teleport into the world specified.
- teleport.back - Allows this user to use /tpback or /back, to teleport to their last known location. (true)
- teleport.coords - Allows this user to display their current location with /tpcoords or /coords. (true)
- teleport.accept, teleport.reject, teleport.toggle - Allows this user to accept, reject, or toggle whether or not they want to be notified of requests when they receive them (if a user toggles their status, they will automatically reject any requests they receive). (true)
- teleport.requests - Allows this user to display their open requests, or any requests they've made, with /tprequests (true)
- teleport.cancel - Allows this user to cancel their active request (if they have one), with /tpcancel (true)
- teleport.silent - Allows the user to toggle their stealth setting with /silent; silences any /tpo or /tpohere command used by the sender
- teleport.language - Allows a user to choose a language from the available languages list with /tplang.
Convenience Permissions
-
teleport.users
- teleport.tpa, teleport.tpahere, teleport.accept, teleport.reject, teleport.toggle, teleport.requests, teleport.cancel, teleport.world, teleport.world.*, teleport.back, teleport.coords
-
teleport.mods
- teleport.users, teleport.tp, teleport.tphere, teleport.tp.other, teleport.location, teleport.vanilla
-
teleport.admins
- teleport.mods, teleport.tpo, teleport.tpohere, teleport.silent, teleport.rewind
Noticed an issue with Multiverse and TeleportSuite that breaks the playerTeleportEvent.
http://pastebin.com/qF4E6A7Z
Not quite sure who to go to about this.
fatmarleys: Another plugin (MobCatcher, from the looks of it) is breaking the PlayerTeleportEvent by doing something invalid. Contact the author of that plugin with this stack trace.
@krinsdeath
I got this error the other day in my log...and I noticed after b104 that noclip doesnt work so well...related or not I dont know, just throwing it out there.
http://pastebin.com/6EReE9pu
Every permission issue you see with every plugin that uses SuperPerms is going to be PEX related. It is a bad plugin. It's slow, cumbersome, glitchy, and unstable. It's also the only permissions plugin that can't survive a /reload.
I have no intention to implement PermissionsEx's own (antiquated and archaic) way of doing things when there is a perfectly acceptable API presented by Bukkit.
Regarding the /tpcancel and /tprequests not showing messages, can you pastebin your english.yml file? They should output a line based on your localization messages.
Hi there, we have been having no problems with PEX. I tried a lot of permissions plugins and PEX was the only one so far that really seems to work properly when used properly. I know people say it doesn't do things properly or whatever but in my experience if you read the documentation and know how to use it properly it works great.
I also was noticing that for certain actions no messages are sent. For example if you type /tpcancel or /tprequests and you have no requests it just doesn't say anything. I feel like there were some others but I can't remember them at the moment. I don't know if its really a bug but just thought I would mention it.
It's a shame that we have to change our entire permissions system to accomodate one plugin. I haven't had a problem with PEX until now.
rustyshakelford2: PermissionsEx does a lot of very glitchy and unstable thing; as a result, it loses a lot of very simple functionality (like the ability to negate nodes effectively (and consistently)). I recommend switching to any of the other permissions managers, like bPermissions or Privileges - both of which work perfectly well with this plugin.
Regarding nodes defaulting to off, this is something multiple people have informed me about - it is inconvenient for PermissionsEx users, certainly; however, not everyone uses PermissionsEx (or even permissions in general). In the case of Bukkit + TeleportSuite (in the absence of a permissions plugin), if all nodes defaulted to off, this plugin would (essentially) be totally useless.
Cozzmy13: I'm not certain I understand. Given a proper SuperPerms handler (bPermissions, Privileges, PermissionsBukkit, etc), you should be able to do whatever you want (however you want) with any of the nodes defined by this plugin.
@rustyshakelford2
No all permissions shouldn't be off the author just wanted for us to dont do anything!
My server uses PEX for permissions, and your plugin gives all players certain permissions by default, even if i remove all teleportsuite nodes from the permissions file. All nodes should be off by default. I had to insert this to disable them: - -teleport.coords - -teleport.world.*
@krinsdeath
Thanks, currently using v2.1.2 b91. Not sure it was implemented there and just noticed b95, going to bump my rev up.
stargateanubis14: Open the jar, edit the plugin.yml and remove the associated commands (or comment them out).
Is it possible to de-register the command from the plugin?
basically, i have another plugin that uses some of the same commands/aliases. How can i ensure that your plugin doesn't override those plugin's commands (the primary one i'm worried about is Tele 2
Thanks!
pimsserver: Without some reference to what is going on in my plugin, I have no way of determining whether or not that has anything to do with TeleportSuite.
Most likely, it does not. Spout is probably overriding some object that delegates the teleport event to plugins.
Remove spout, and tell me if the error continues?
erdrickk: I do not depend on other plugins, but /silent now applies to /tp and /tpo. It is illogical to apply it to /tpa, though.
phuriosgeorge: Silent should already be persistent across reloads and restarts. It also applies to /tp now, as well.
http://dev.bukkit.org/paste/5716/
They told me it probably had to do with my teleport plugin, which is this one :)
Is there anything you could do?
(using spoutplugin 1212)
In addition, can tp silent be persistant along with applying to the /tp command?
the Silent node only seems to work with TPO, not TP
When my mods vanish and /tp to someone the other person can see So and so has teleported to you etc....
Anyway to totally disable that message?
You can remove the ability to use any command by removing the permission node associated with it:
teleport.tpa -> /tpa
teleport.tpahere -> /tpahere
...
If a user does not have the node, they cannot use the permission. With PEX, this should be achievable by negating the permission:
<<reply 780309="">>
I made the very same mistake too, in the beginning,
you should add negative permissions;
- -teleport.tp
I only want admins to be able to teleport, but as of a recent version of this mod, everyone now has access to it. I use PEX for permissions and have activated the pricing to make it prohibitively expensive, but I want to make it unavailable. Can this be done?
ray73864: Yes. teleport.world.[worldname] permission nodes.
Looks like Jenkins wasn't properly pushing the new artifacts because I forgot to use mvn clean 8-). It's fixed and uploaded as b104.