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


    Nope. It is version: '1.6'

    You got a ETA on a new version or download link?
  3. Offline


    @Smokie23 ^^ but read the note under the download links in the top post. Important info.
  4. Offline


    Are you talking about " So I recommend you grab the 1.6.1 alpha official here (rename to Waypoint.jar)."?
    If so, I did read that and try the link but the link is broken or down too? That's why I asked. Is that link suppose to work?

    "The server at is taking too long to respond."
  5. Offline


    Oh yeah, I forgot..My server is down. It won't be back up until around 5:30 PM CST (sorry for the inconvenience...)
  6. Offline


    oh prob's. Ill try later.
    Also do you have a readme or doc? What is the difference between /warp set and /warpadmin set?
  7. Offline


    /warp set only allows you to set warp properties if you own the warp.
    /warpadmin set lets you modify the properties of any warp (only if you have the permission)
    And there is no readme or documentation. I've been meaning to write some stuff, but I never got around to it.
  8. Offline


    I can't seem to DL if from any browser that I try.
  9. Offline


    I am having an issue when traveling to another world with waypoint or through a portal. When i try to teleport to another world with waypoint or a portal, the client freaks out and constantly flashes the "simulating world for a bit" bar and also crashes the server. I uninstalled every plugin except for waypoint and permissionsbukkit to try to isolate the issue. This has been tried with and without the "*" permission node. waypoint_error.PNG

    Attached Files:

  10. Offline


    Server is down until around 5PM CST

  11. Offline


    Means I gotta wait another hour before I can dl it D:<
  12. Offline


    Sorry :/
  13. Offline


    Haven't tested in 1.6.3, but in 1.6.2 buffs go away after using /world <differen't world>
  14. Offline


  15. Offline


    potion effects.
  16. Offline


    That's most likely a minecraft problem, not a Waypoint problem.
  17. Offline


    Tested with netherportals....

    Hate when you're right.
  18. Offline


    :) <3 just because it's something i can't fix :3
  19. Offline


    Waypoint beta 1.6.3
  20. Offline


    Good news everyone! My server is back alive!!

    Strange...I'll do some more testing.
  21. Offline


    Just DL'ed the new build (been building crap and on my server with a friend. I'll see if anything goes wrong.
  22. Offline


  23. Offline


    I tested /world with both PEX and PermissionsBukkit and could not re-create that error.
  24. Offline


    I can't really tell much from your paste. I need the actual tracebacks, not just the console saying it caught an error.
  25. Offline


    As suggested before; Make an accept command when someone tries to use /tpto or /tph (/tp <player1> <player2> could require both people to /accept?)

    Along with the above make an admin command to bypass the acceptance requirement (/tptoadmin or /admintpto?)

    (kind of like essentials?) add a /back to where you warp to your location before you warped/tp'd. (instead of having to create a new personal point before warping somewhere if you're at a place you want to go back to)

    A plugin reload command (instead of having to use /reload which can bug out other plugins sometimes.)

    Idk if these are hard to do or not, just suggestions, they don't have to be implemented, but server owner's will prolly like them :p
  26. Offline


    So all I do is download the 1.6.3 and swap that with the old jar? if so, I get errors in 1.6.3. When I try to "/warp add <warpname>" I get this error.
    1.6.3 error (open)

    2011-12-22 10:45:55 [SEVERE] null
    org.bukkit.command.CommandException: Unhandled exception executing command 'warp' in plugin Waypoint v1.6.3
    at org.bukkit.command.PluginCommand.execute(
    at org.bukkit.command.SimpleCommandMap.dispatch(
    at org.bukkit.craftbukkit.CraftServer.dispatchCommand(
    at net.minecraft.server.NetServerHandler.handleCommand(
    at net.minecraft.server.NetServerHandler.a(
    at net.minecraft.server.Packet3Chat.a(
    at net.minecraft.server.NetworkManager.b(
    at net.minecraft.server.NetServerHandler.a(
    at net.minecraft.server.NetworkListenThread.a(SourceFile:108)
    at net.minecraft.server.MinecraftServer.w(
    Caused by: java.lang.NullPointerException
    at me.pirogoeth.Waypoint.Util.WarpLimits.playerReachedLimit(
    at me.pirogoeth.Waypoint.Waypoint.onCommand(
    at org.bukkit.command.PluginCommand.execute(
    ... 12 more

    The commands "/warp list" seems to be working as it says no warps to display. Can't test other commands as I can't even add a warp yet.
    Downgraded to 1.6.2 and "/warp add <warpname>" works.

    Also, is your TP signs working in 1.6.2? I can't seem to get it to work.

    SUGGESTION: Color/confirmation for teleport signs. Color line 1 or line 2, green text for successful TP sign and red text for failed sign or have the sign pop off and say to the user "invalid sign" or some kind of confirmation that the sign worked or failed.
    If line1 =/= [WP:WARP] or [WP:WORLD] it should fail and pop off or at least tell the maker wrong syntax
    If line2 =/= valid warp is should fail and pop off or at least tell the maker invalid warp name
  27. Offline


    That would be awesome!
    Or just have 2 different permissions for the same command. (/tp and /tphere) So people with waypoint.teleport.teleport can send tp/tph invites and with waypoint.teleport.admin bypasses the invite and tp's instantly.

    Also, I use 1.6.2 and I have the permission node*. But when I try to warp to a warp I created, I get the message: [Waypoint] You are not allowed to warp between worlds.
  28. Offline


    In your config.yml, set warp.traverse_world_only to false.
    thernztrom likes this.
  29. Offline


    This is true. /warp add <warpname> doesn't seem to be working. Warping in general still works properly though. As for the signs, no the ones listed don't work in 1.6.2, that's only 1.6.3 and above I believe.
  30. Offline


  31. Offline


    Still doesn't work. Tested with diff perms just in case it was a perms problem.

    /wp add doesn't work either.

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

Share This Page