Inactive [TP/HOME/WARP] Waypoint v1.6.4(beta)- Teleportation points, home, spawn, and warp management. [1609]

Discussion in 'Inactive/Unsupported Plugins' started by miyoko, Jul 12, 2011.

  1. Offline




    Waypoint - simple teleportation point and home/spawn/warp management plugin:
    Version: v1.6.4 beta


    *New in 1.6: modular command hookins, reworked command system, SuperPerms, ????*

    Waypoint is an easy teleportation point management and home location
    management plugin. You can create teleportation points to go back to later
    as well as share privately with other users. You can also create public warps that only certain groups of users can access.

    Waypoint's Features:
    • Add/delete waypoints for later access
    • List all of your waypoints simply
    • Share your points privately with other users
    • Points are private, and only accessable by you, unless shared
    • Multiworld support
    • Permissions/SuperPerms/OP support with strict nodes.
    • Home location management
    • Home location is automatically set to the bed you last exited (only if enabled in config.)
    • Create and manage public warps
    • Control which groups of users can access these warps
    • Save/Load the spawn points for all of your worlds
    • Selective showing of warps (you only see what you can access.)
    • Teleport easily between worlds
    • Create and import other worlds
    • Create and teleportation signs to travel to warps or world spawnpoints
    Download: JAR | SRC
    Development build (bleeding edge): JAR
    Integrity (CI): Waypoint project

    If you like my work, please consider sending a dollar or two my way so my little development company can pay for a server to do work and testing on :)

    For those of you that want to contribute, or even just watch progress get made on this, check this out:

    Phabricator: Source Code/Collaboration

    • /wp add <name> -- add a waypoint to your list
    • /wp del <name> -- remove a waypoint form your list
    • /wp tp <point> -- teleport to your point
    • /wp invite <player> <point> -- send an online player an invite to your point
    • /wp accept <point> -- accept an invite to a point
    • /wp decline <point> -- decline an invite to a point
    • /wp list -- list of all of your points
    • /home -- teleport to your home
    • /home set -- set your current location to your home
    • /spawn [world] -- teleport to the world's spawn point
    • /spawnadmin <save|load> [world] -- save or load the spawn point of the specified world
    • /spawnadmin set -- set the spawn point of your current world
    • /warp [warpname] -- teleport to the specified warp, if you have access
    • /warp add <warpname> -- create a public warp with the default permissions
    • /warp del <warpname> -- delete a warp you own
    • /warp set <warpname> <owner|permission|or a custom value> <newvalue> -- set property values in the warp's metadata
    • /warp list -- list all warps that *YOU* have access to
    • /warpadmin <set|del> <warp> [key] [value]
    • /tp <player> [target] -- teleport to another player, or teleport one player to another.
    • /tphere <player> -- ejects the target from a vehicle (if applicable) and teleports that player to you.
    • /tploc <x,y,z> -- teleport to a set of coordinates.
    • /world [worldname|create|import|list] -- displays what world you are in and your current position, or if given a worldname, teleports you to that worlds spawn.
    Installation and Configuration:
    Download the jar file and drop it into your minecraft server's plugins/
    folder and reload/restart the server. The configuration will be
    automatically created for you.

    Teleportation Signs:
    To create a teleportation sign, you must format it like this:
    Line 1: [WP:WARP] or [WP:WORLD]
    Line 2: world name or warp name
    Line 3: (optional) description # maybe economy cost at some point soon
    Line 4: (optional) description
    It is case insensitive btw.

    Configuration options:
    'set_home_at_bed': set this to true if you want your home to be reset
    whatever bed you get out of.
    'autoupdate': check for updates and download upgraded jars automatically
    'warp.groups': permission groups for warps
    'warp.string': message sent to user after teleporting to a warp, %w is warpname, %p is playername
    'limits': self-explanatory.

    Permissions Nodes: (should each be self-explanatory)
    • waypoint.basic.add
    • waypoint.basic.delete
    • waypoint.basic.teleport
    • waypoint.basic.invite
    • waypoint.basic.invite.accept
    • waypoint.basic.invite.decline
    • waypoint.basic.list
    • waypoint.debug.config_node_test << debugging *ONLY*
    • waypoint.home -- you *must* add this if you want to be able to use home commands
    • waypoint.home.set
    • waypoint.home.set_on_bed_leave
    • waypoint.admin.spawn
    • waypoint.admin.spawn.set
    • waypoint.admin.spawn.load
    • waypoint.admin.warp
    • waypoint.teleport.teleport -- for general teleportation actions
    • waypoint.teleport.location -- for coordinate-based teleportation
    • -- for teleporting players to you
    • waypoint.spawn -- you *must* add this if you want to be able to use spawn commands
    • waypoint.warp -- you *must* add this if you want to be able to use warps
    • -- you *must* add this if you want to be able to use /world
    •<worldname> -- more info on this below
    • waypoint.warp.access.<permission category>
    • waypoint.warp.create
    • waypoint.warp.delete
    • waypoint.warp.list
    • waypoint.sign.warp
    • waypoint.cost_exempt.teleport -- teleports do not cost a single dime.
    Known Bugs:
    • Set home at bed is not disabling, ever. Currently looking into it. T3
    If you find a problem, report it at Github.

    Permissions Setup:
    Here is a sample Permissions 2.7.4 configfile with Waypoint's nodes already set up, and a user set up to give an example. Change it to your liking.

    << Thanks Pr0Failure :D

    World Access
    As of about 1.6.1, I added a few new things that implement a whole "world access" type schema of features. Players will NEVER be able to access a world unless they have the "<worldname>" or "*" permissions. I will add a configuration option to disable this, but for now, it's always on. If you want to effectively disable it without a config option and your permissions system supports inheritance, simply place the "*" node at the lowest level and it should filter up through everything that inherits that or its children. I only added this because I felt it would be handy in the case of servers wanting to prevent griefing in creative worlds, but leaving whitelisting off, and just spawning all new users in the spawn world, but not letting them traverse your minecraft universe of worlds. There will be a config option to turn this off soon. By the way, if you didn't catch the gist of what I was really saying, this prevents ALL teleporting between worlds (only if you don't have the permissions for that world) no matter what you use to teleport. This catches events at a low level and checks each user's permissions as they change worlds. But enough about this.

    Bugs and Errors
    If you get a "An internal error has occurred" message when you use a command, * PROVIDE A TRACEBACK PLEASE. * (hint: a traceback is the error code in the server console that shows the error and its callers)
    And for those of you that didn't read this text, maybe this image will catch your attention:


    • Fix PermissionsEx not being detected correctly.
    • Rewrite command structure again with sk89q's command framework.
    • Add configuration options to disable various things.
    • Clean up core support code (me.pirogoeth.Waypoint.Core.*)
    • OpenAuth integration in the future?
    Version 1.6:
    • Completely rewrote the command parser from the ground up.
    • Added SuperPerms support
    • Split commands apart into categories (much cleaner for anyone who works through the code)
    • (Supposedly) Fixed NPE from LoadWorlds during plugin load.
    Version 1.5:
    • Rewrote the configuration loader and put it in its own class
    • Restructured config storage
    • Added new warp limitations
    • Added an autoupdater
    Version 1.4.5
    • Fixed warp permission loading and detection
    Version 1.4.4
    • Fixed the internal errors spewed on /warp set
    Version 1.4.1
    • Removed some unneeded imports
    • Removed some unused variables
    • Now using String.format in checkperms
    Version 1.4
    • Added warp management
    • Restructured most of the config file formatting.
    • Homes-per-world (you can have one home per world now.)
    • Added spawn management
    • Added backup/restore of world spawn points
    Version 1.3
    • Added home support
    • Fixed configuration node bugs
    Version 1.1
    • Added invite support
    Version 1.0
    • Wrote all base code
    And some thanks.
    Definitely got some big thanks here, especially to Pr0Failure, who been testing the crap out of this, even during its magical beta stages. And some more thanks to all of you that put up with me not being around for weeks on end due to school. And thanks to others who at one point sent in a pull request to fix something I had missed. I love you all, you're a very supportive community :) Also, some big thanks to Ctark who's been following this like crazy and even digging through my messy code to find nodes to help others while I'm not around :) Again, THANK YOU ALL <3
  2. Offline


    I can't for the life of me figure out how to set 1 single /spawn.
    I want users to be able to use /spawn from the Nether, End, or where ever and always go back to the same starting point (In the default world).
    Also, /home to work the same... they always go to their /Home set in the default World..

    help please!
  3. Offline


    Every world has their own spawn. So you won't be able to do that with /spawn. They'll have to use /world <default world>, /home should always work (I think).
  4. Offline


    i do not get it at all, where is this permissions plugin, no such folder exists in my plugin folder, where is this group file i cant find. god damn why does bukkit plugins have to be so f%^& complicated, it would not be so bad if there was some kind of universal permissions but every single plugin does it slightly different and i think i am about to lose my mind this is so infuriating
  5. Offline


    The group plugin is separate. I suggest getting PEX.
  6. Offline


    The command "/warp list" is not useful as long only one page of warps is shown. So we have more than 18 warps in our world. Isn't possible to do implement a subcommand "page" in the list-command, p.e. /warp list <page>? It'ld be lovely :).
  7. Offline


    But the users cant use /spawn
    Whats wrong ?

    Dont working too
  8. Offline


    Add the permission commandbook.spawn - only by this it works for my users.
  9. Offline


    I plan on it. I just have to figure out how first. I'll do some research.
  10. Offline


    When the cooldown is active, it still displays the text that you have arrived at the warp / waypoint / spawn, but also says it's cooling down, would be nice if it didn't do that, since you actually haven't gone there yet...

    Also anyway to display how many seconds until you can teleport again? Maybe customizable text for the warning.... :D
    Just incase you didn't have anything to do.....
  11. Offline


    It shouldn't say that it's cooling down.
  12. Offline


    But it does, and now that you know about it, it hopefully won't anymore :D
  13. Offline


    can you give me link for the right permission plugin ? cuz i dont know which plugin to download 1!! thanks
  14. Offline


    PermissionsEx, now go search it you lazy fuck.
  15. Offline


    Just re-read that. It shouldn't say that it's taken you somewhere. I think I've noticed that before. I'll fix it right now.

    Ctark try the build here:

    Random note: I'm so happy! I got integrity (most beautiful CI server I've ever seen) running <3! Except the bad part is, I had to implement the artifacts support (integrity is written in ruby...I learned ruby last night...>_>), which was modestly interesting for me. Make sure to let me know if something goes wrong while you're trying to download an artifact for a build, is basically my point, I guess.

    I just added experimental recursive waypoint deletion support. From


    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: May 17, 2016
    Ctark likes this.
  16. Offline


    So this plugin is on a server I'm on, and I invited some ppl to check out my house with invite parameter. Now, I don't want them to keep coming and going wherever they please. I initially thought the invite was good for only one use (Which would be a fantastic update). But now, how do I (de)invite them, as it were? I've looked at in-game help parameter and all over this page, but can't find such a thing. Please respond through PM
  17. Offline


    ive been having issues wih my permissions... can you just explain it to in the simplist possible way... thanks
  18. Offline


    im having the exact same problem. im the owner of my server and I dont have the permission to use the commands... what can i do? i have permissions plugin if that makes anything easier, could someone please help?
  19. Offline


    You have to tell me what your "issues" are for me to help. And I recommend you use PEX. It generally causes no issues at all and is so much easier to work with than most other plugins.

    I have an experimental build. In it, I have implemented list paging, thanks to eisental's etCommon library. It is experimental, but as far as I have seen from my testing, it should not cause any problems.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: May 17, 2016
  20. Offline


    miyoko, no "waypoint.command.*" or something that give all acced ?
  21. Offline


    Just installed this for some basics now , but i notice as i jumped worlds via multiverse portals that waypoint spammed a bit about not having access to this world, is it possible to exclude NON "waypoint" jumps via other portals from its notice.
    ie only have it worry about the stuff it creates ??. Gets complicated don't it with so many plugins crossing over in some way :).
    At the moment ive just started using it to set up a jump home via hot key , and a return jump with another hot key using a local "macro mod" (
    , interworld is handled by multiverse-portals
  22. Offline


    hey plz help it wont let my admins or any other rank build. i user permissionsEX for my permission folder plz help
  23. Offline


    Waypoint doesn't have anything to do with building permissions. Go to PEX and ask there.
  24. Offline


    Nope, sorry.
  25. Offline


  26. Offline


    Or that. That may work. no guarentees, unless Pr0Failure can provide a testimonial that it explicitly does work.
  27. Offline


    It works.
  28. Offline


    It isn't compatible with PEX?? Because it doesn't work for me, but it works with other permissions..
  29. Offline


    Uh, it is comparible with PEX. You have to enable the compatibility layer plugin.
  30. Offline


    Seriously, or should that be a joke :confused:? Whats that "compatibility layer plugin"?
    It just doesnt work, it always says i dont have permissions but i actually have the '*' permissions so i have everything... That suck :/
  31. Offline


    is there a way to set a delay? so that somebody must wait like 30 seconds before he/she is actually teleported?
    EDIT: blah, nevermind. was too stupid to notice the cooldown thingy in the config file :D

Share This Page