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

    miyoko

    Notice!

    THIS PLUGIN IS OLD AND VERY VERY OUTDATED. DOWNLOADS ARE NO LONGER AVAILABLE, AND SUPPORT FOR THIS PLUGIN HAS BEEN DROPPED. IF YOU NEED A SIMILAR PLUGIN, PLEASE USE ZPort


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

    NOT YET UPDATED FOR 1.2

    *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 :)
    [​IMG]

    For those of you that want to contribute, or even just watch progress get made on this, check this out: http://phabricator.maio.me/project/view/1/

    Phabricator: Source Code/Collaboration

    Commands:
    • /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:
    Code:
    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.save
    • waypoint.admin.spawn.load
    • waypoint.admin.warp
    • waypoint.admin.world.create
    • waypoint.admin.world.import
    • waypoint.teleport.teleport -- for general teleportation actions
    • waypoint.teleport.location -- for coordinate-based teleportation
    • waypoint.teleport.here -- 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
    • waypoint.world -- you *must* add this if you want to be able to use /world
    • waypoint.world.teleport
    • waypoint.world.list
    • waypoint.world.access.<worldname> -- more info on this below
    • waypoint.warp.access.<permission category>
    • waypoint.warp.create
    • waypoint.warp.delete
    • waypoint.warp.list
    • waypoint.sign.link.create
    • waypoint.sign.link.use
    • waypoint.sign.link.delete
    • waypoint.sign.warp
    • waypoint.sign.world
    • 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 "waypoint.world.access.<worldname>" or "waypoint.world.access.*" 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 "waypoint.world.access.*" 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:

    [​IMG]

    TODO:
    • 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?
    Changelog:
    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

    Pr0Failure

    That would defeat the purpose of not being able to cross-worlds.
     
  3. Offline

    miyoko

    Eh, I know. The point was more of you can warp around this world, but not to any other world until you get there. Waypoints are private and uncontrolled (except for in amount) where warps are public and controlled completely.
     
  4. Offline

    Tak Suyu

    I have a little problem it seems.

    As far as I can tell I have set the permissions correctly but I can't get /wp list to work. (As User)
    I only get "Does not have access to this permission"

    Tried my best to troubleshoot it but I'm stumped

    I'm using:
    • CraftBukkit Build: 1530
    • PermissionBukkit v1.2
    • Waypoint v1.6.1
    And here is the group permissions
    Show Spoiler
    Code:
    groups:
        default:
            permissions:
                permissions.build: false
        user:
            inheritance:
            - default
            permissions:
                permissions.build: true
                waypoint.basic: true
                waypoint.basic.*: true
                waypoint.home: true
                waypoint.home.*: true
                waypoint.teleport.*: true
                waypoint.spawn: true
                waypoint.warp: true
                waypoint.world: true
                waypoint.world.teleport: true
                waypoint.world.list: true
                waypoint.world.access.World: true
                waypoint.warp.access.Default: true
                waypoint.warp.list: true
        helper:
            inheritance:
            - user
            permissions:
                waypoint.warp.access.Mod: true
                waypoint.warp.create: true
                waypoint.warp.delete: true
                waypoint.sign.*: true
    

    Is it just the versions? Syntax? I can't figure it out..
    Thanks for the time
     
  5. Offline

    Pr0Failure

    Times like this I wish I knew PermissionsBukkit

    As far as I know .* doesn't work in any bukkit perms plugin. But I could be wrong considering I still use/test with just perms3.1.6
     
  6. Offline

    Tak Suyu

    Hmm but the teleportation of warp and home wouldn't work without "waypoint.teleport.*" working

    So that didn't seem like a problem
     
  7. Offline

    Pr0Failure

    Try it with writing out all the waypoint.basic.list/teleport etc nodes and see if it works.
     
  8. Offline

    Tak Suyu

    And it works.. weird considering they use * in the documentation...

    Thanks for the help
     
  9. Offline

    Pr0Failure

    Np.
     
  10. Offline

    Pr0Failure

    It's already been tested for 1597. He just needs to update the tag.
     
  11. THen a update of the links would be very good to..
     
  12. Offline

    Pr0Failure

    If you read through the posts you would've found a working one.

    1.6.2 beta Just rename it to Waypoint
     
  13. Offline

    Ctark

    Nudes First then a working release..... Thats how it works on the internetz :D (jks)
     
    Pr0Failure likes this.
  14. Offline

    miyoko

    I refuse to update the links until I get back on my feet from some...unexpected problems. If you read the main post, there's a note below the download links. Inside that note, there's a link to a *perfectly* working 1.6.1 beta. Please, please, please don't ask for me to update the main links. I will update them when I get things fixed. I'm sorry if it's inconvienient, but it's necessary for me. I'm trying to juggle benchmarks, finals, drama, and getting my company started. So please, just bare with me.
     
  15. Offline

    Pr0Failure

    Good luck :O!
     
  16. Offline

    miyoko

    Thanks :3
     
  17. Offline

    Hanyuu

    Is there a way to keep waypoints from working outside of the world they they were created in? I want to keep users from taking items from a creative world into a survival world.

    If you can't it would be a cool feature to add in the future.
     
  18. Offline

    Pr0Failure

    In the config file set 'traverse_world_only' to true. Same for 'list_world_only' they won't be able to see/use warps cross-world but if you have waypoints (personal warping) set for them they can still use that which I think is retarded, but hey it's not my plugin.
     
  19. Offline

    miyoko

    I'll make it limit waypoints too then -_-'
     
  20. Offline

    Pr0Failure

    Thank you :)
     
  21. Offline

    Ctark

    I really do hope you are serious! I still can't wait for that feature!
     
  22. Offline

    Pr0Failure

    Any chance you can find me the full version of /world create? Meaning like where to type on the string for environment and possibly seed?
     
  23. Offline

    minecraftYord

    as soon as you have time: can you please let us configure the prefix of the messages and the color? (atm it is [Waypoints])
     
  24. Offline

    Pr0Failure

    @miyoko
    Psst, is it possible to create a world with a specified seed?
     
  25. Offline

    miyoko

    Possibly. Lot's of refactoring...

    No, it is not. I've tried, I'll try again later.

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

    Pr0Failure

    Also instead of using /world import to create new worlds, could you make it so that it imports an existing world. I've got a good Single Player world I'd like to use with Waypoint but as far as I can tell I can't hook it into Waypoint.
     
  27. Offline

    miyoko

    /world create makes new worlds..
    /world import "worldname" ENVIRONMENT gamemode
     
  28. Offline

    Pr0Failure

    Touche....
     
  29. Offline

    miyoko

    ;)
     
  30. Offline

    minecraftYord

    thanks! The reason I'm asking for this is that light blue and squary brackets dont really fit our overall design on the server :D
    But no rush, do what you can/want :)
     

Share This Page