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


    yay force it to me xD ... i will get this plugin working, so i can enjoy my rest day @ office xD
  3. Offline


    Today is a very long day for me, so no Waypoint work tonight, unless I really need something to do to keep my mind in check. It's an 8:30AM-8:30PM day for me ;/
  4. Offline


    Thanks! Im looking forward to it.
  5. Offline


    You try waypoint.home.set?

    Since this morning, the count has increased to 797. I've only been tracking over about a 48 hour period :)

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


    So Waypoint does not work at all on my 1.8 server, I have been told I need to set up the superperms permissions.yml so default is OP (everyone on my server is an op) but I have no idea how to do that. Could someone post the code? My permissions.yml is empty right now...
  7. Offline


    I actually recommend old Permissions (Phoenix) v2.7.4 :) It works quite well, plus there is a sample config.yml in the OP :)
  8. Offline


    *Groans* I specifically stopped using Permissions because I hated it! Why can't this be simple and just WORK like it did in 1.7.3?!
  9. Offline


    Try PermissionsBukkit and SuperBridge, and try to snag a config from someone who uses PermissionsBukkit (I personally use Permissions v2.7.4 :p)
  10. Offline


    I suppose I could try Permissions v2.7.4, I was using v3+... which config do I drop those contents into?
  11. Offline


    <worldname>.yml where <worldname> is the name of the world you want that configuration to be for :3
  12. Offline


    Where is that .yml supposed to be located? I don't see it anywhere!
  13. Offline


    You need to create it. plugins/Permissions/<worldname>.yml
  14. Offline


    Alright, thanks, I'll try that out!

    *facepalms* Alright, so I didn't really have to change anything or install permissions, it looks like I was running an unstable build of Waypoint 1.5.9! Sorry I spammed up the topic! Everything works just fine, without any permissions!

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


  16. Offline


    no in your permissions config
  17. Offline


    That actually makes a ton of sense xD! Glad you got it working!

    So I just now started really porting the old commands to the 1.6 stuff, I've got 2/12 done as of right now.

    Currently on 11/12 :) Look forward to 1.6 very soon, my friends.

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


    I am getting a crash using v1.5.9 with Craftbukkit version git-Bukkit-0.0.0-1067-g6301507-b1185jnks (MC: 1.8.1)

    21:22:14 [SEVERE] Error occurred while enabling Waypoint v1.5.9 (Is it up to date?): null
    at me.pirogoeth.Waypoint.Core.Worlds.LoadWorlds(
    at me.pirogoeth.Waypoint.Waypoint.onEnable(
    at org.bukkit.plugin.SimplePluginManager.enablePlugin(
    at org.bukkit.craftbukkit.CraftServer.loadPlugin(
    at org.bukkit.craftbukkit.CraftServer.enablePlugins(
    at net.minecraft.server.MinecraftServer.e(
    at net.minecraft.server.MinecraftServer.a(
    at net.minecraft.server.MinecraftServer.init(
  19. Offline


    It's not a fatal error. The plugin will still work correctly.

    So , I just have to fix about 96 errors. Then 1.6 will be ready.

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


    1.6 is in its final stages. Not even joking. I've got the 1.6 final prerelease running on my server :)

    Edit: Released ;)
    Ctark likes this.
  21. Offline


    sorry, but no matter what i try, with permissionsbukkit 1.2 and SuperpermsBirdge 1.2 i still do not have permission to use this command. can someone please help?

    i've watched the video, edited whatever, even had to reinstall my permissionbukkit plugin, still doesnt work. any help is appreciated.

  22. Offline


    i like this plugin verymuch, but there is one thing that i really miss. And that is the ability to disable certain functions of this plugin. example: we use the set home function from another plugin, but now your plugin interfears with the other plugins function.

    So a feature suggestion: able to disable certain functions in the config or something? :)
    None the less this is a really good plugin ;)
  23. Offline


    Not many changes in 1.6, but they have been noticed. Props to the update stopping the error every time you start up the server. I haven't tested it, but I'm guessing everything works fine :p
  24. Offline


    1.6 was basically a ton of internal stuff. I plan on adding a lot of new stuff soon (in 1.6.1-1.6.?).
  25. Offline


    Update found. -1->160 :: Now Updating.

    Always happens on every start. :)
  26. Offline


    for some reason i cannot remove your plugin.
    I have removed the folder and the jar, but on a reload of my server your plugins reinstalls itself?
  27. Offline


    I noticed that on mine too....strange.

    Edit: Just bumped the version number. Should be fixed now.
  28. Offline


    Turn off auto updating in the config.
  29. Offline


    Uhm o_o thats like, impossible. Stop your server then delete the jar and folder.

    I just fixed it tho :0

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


    Meh. I don't feel like updating for one simple thing I already did :eek:
  31. Offline


    /setspawn did set the default Spawnpoint of a World to where i am.
    now it Sais, the Spawnpoint where saved, BUT it teleports me to the "old" Spawnpoint, and wont save the new one.

Share This Page