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


    Can you paste the errors from the console?
  3. Offline


    for what ever reason it started working.
  4. Offline


    I'm currently horribly busy with band camp, I've got 8AM to 8PM days full of marching and saxophone sectionals. I'm sorry I havn't responded much, but practice is exhausting. If you have a bug of any kinda, please file an issue on github, as I don't always get notifications from the forums about posts. If you have a very very /very/ *severe* issue, email me at shaun - at - and I'll respond as fast as I can.
  5. Offline


    So the plugin has it's own internal set of permissions that need to link to the permissions config? I don't get the point.. and I'm not able to give anyone permission to use it.. Here's my config.yml, and my permissions config. I think I must be doing something wrong.

        set_home_at_bed: 'false'
        case_sensitive_tp: 'true'
        - gatherer
        - builder
        - mod
        - admin
        list_world_only: 'false'
        traverse_world_only: 'false'
    version: 1.5.0
    autoupdate: 'false'
            default: true
                prefix: ''
                suffix: ''
                build: true
            - waypoint.home.gatherer
            - waypoint.home.set.gatherer
            - waypoint.warp.gatherer
            - waypoint.warp.list.gatherer
            - commandbook.say*
            - commandbook.clear
            - commandbook.msg
            - commandbook.who
            - commandbook.motd
            - commandbook.intro
            - commandbook.rules
            - commandbook.spawn
            - mcmmo.skills*
            - mcmmo.ability*
            - mcmmo.commands*
            - deathcontrol*
            - creativegates.use
            default: false
                prefix: ''
                suffix: ''
                build: true
            - Gatherer
            - waypoint.home.builder
            - waypoint.home.set.builder
            - waypoint.warp.builder
            - waypoint.warp.list.builder
            - waypoint.warp.create.builder
            - waypoint.warp.delete.builder
            - waypoint.warp.access.builder
            - commandbook.whereami*
            - commandbook.whois*
            - commandbook.mute
            - commandbook.time
            - commandbook.warp.teleport
            - commandbook.give
            - commandbook.give.stacks*
            - goldtools.*
            - creativegates*
            - residence.create
            default: false
                prefix: ''
                suffix: ''
                build: true
            - Builder
            - waypoint*
            - commandbook.time*
            - commandbook.kick
            - commandbook.bans*
            - commandbook.debug*
            - commandbook.clear*
            - commandbook.broadcast
            - commandbook.teleport*
            - commandbook.locations*
            - commandbook.warp*
            - commandbook.return
            - commandbook.give*
            - commandbook-more*
            - mcmmo.*
            - vanish*
            default: false
                prefix: ''
                suffix: ''
                build: true
            - '*'
  6. Offline


    How I can do to users can use warps? In my server only admins can use warps.
  7. Offline


    The permissions are only used for warp access. Not for the home and stuff. waypoint.warp.access.<Insert permissiom group name here>

    You have to setup permissions correctly to do it. See above.
  8. Offline


    Ehh it's too hard for me :( Can you say me step by step what I must do? There's my config.yml:

    set_home_at_bed: 'false'
    case_sensitive_tp: 'true'
    - Default
    - Mod
    - Admin
    list_world_only: 'false'
    traverse_world_only: 'false'
    version: 1.5.0
    autoupdate: 'true'
  9. Offline


    Yeah I don't get it either. I got rid of the group names in my permissions yml, and it still doesn't work for the "Builders".

            default: false
                prefix: ''
                suffix: ''
                build: true
            - Gatherer
            - waypoint.home
            - waypoint.home.set
            - waypoint.warp
            - waypoint.warp.list
            - waypoint.warp.create
            - waypoint.warp.delete
            - waypoint.warp.access
  10. Offline


    I will be posting a tut on how to set it up in permissions soon just wait guys.
  11. Offline


    Thank you thank you thank you thhank you. I'm at lunch on my phone right now and I just checked my email and saw this. I havn't had much time this week.
  12. Offline


    Bug: /warpadmin only allows you to delete warps, not change the owner/permission of a warp. If you try to /warpadmin set <warp> owner <name> it just gives the standard you do not have permission to modify this warp.
    But if you do /warpadmin del <warp> it deletes it.

    Video is done, trying to find a good compressor so it doesn't take 5+ hours to upload.
    Decided not to compress it. Video will be up in 2-3 hours.
    Raskull likes this.
  13. Offline


    Awesome man, I look forward to seeing the vid!
  14. Offline


    Derp. Sorry about the clicking sounds, the mic is in my laptop/sensitive.
    Edit: 480p for standard view, 720p for Fullscreen works best.
  15. Offline


    Thank you for doing that :) I appreciate it alot. I'll take a look at the warpadmin set stuff in a while.
  16. Offline


    Got it working thank you!
  17. Offline


    If you can post the video in op. Would help others instead of having to search through the thread.
  18. Offline


    Would it be possible to add a number after the node to set the amount of points they can set?
    That would allow 15 points
  19. Offline


    I don't think so. At the moment there isn't any warp creation limit. Maybe in future versions.
  20. Offline


    could you update it so you can sett the spawnpoint
  21. Offline


    You can already do that with /spawnadmin set
  22. Offline


    If you could add a cooldown timer then this is perfect for what i need [pig]
  23. Offline


    I'm going to work on a total setup video after I shower. It'll cover setting up Waypoint with Permissions v2.7 from the ground up, and I'll post a link to a basic Permissions file. I also added a /tploc command to version 1.5.1 that I'm still working on.

    Sample Permissions 2.7.4 conf:
  24. Offline


    More specifics on /tploc would be helpful :eek: I'm curious as to what this is.

    Scrub, you set up your nodes wrong. Nodes are on the same column as your "permissions:, info:" etc etc.
  25. Offline


    Actually, I'm going to argue that :p The way I did it is the *correct* way, because of how code and such is typically indented (see also: python syntax/formatting)
  26. Offline


    Every other Permissions setup I've seen says otherwise >_>
  27. Offline


    :< either way, my format works :p

    I wish I could get a general consensus of how many people are using my plugin. Do you guys mind if I add a little code to do an HTTP post to a little script that tracks how many setups are performed?

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


    In English pl0x.
  29. Offline


    Have Waypoint send a request to my server so I can keep track of how many people use it.
  30. Offline


    Nah, I don't really mind. It'd have to wait for tomorrow for me to apply it though.
  31. Offline


    I'm not doing it tonight xD

Share This Page