Inactive [TP] PrivateWarp 1.7.4 - Private Warping suite [1.4.4-R0.1]+

Discussion in 'Inactive/Unsupported Plugins' started by The_Wrecker, Jan 14, 2011.

  1. Offline


    PrivateWarp - The Private Warping plugin

    Warping since Dec 2010 ! Proven to last.
    Current Version: v1.7.4
    Download PrivateWarp
    Download PluginControl (v1.2.8)
    Compatible with:
    Tekkit (1.3.2) (Bukkit for minecraft 1.2.5)
    Bukkit 1.3.2-r1.0
    Bukkit 1.4.4-r0.1
    Other stuff:
    Download Waypoint Converter (to convert and maintain warp files)
    Download Full zip (Including PublicWarp 0.65!)
    Current, all downloads page (Includes instruction videos)

    I made one of the apps I have compatible with the format.
    It's a gui which lets you peak inside of the private warp files. Some parts are not yet finished, might not finish it completely, but you'll have a way to get the contents.
    Download here: GUI Editor

    The converter can read your waypoints.txt (former hmod plugin) and create PrivateWarp database files. Those database files can be copied/moved to the privatewarp player directory to once again have your old warps back.
    You can use my plugin to create private warps. Every player can have his or her own set of warps. You can also set categories so you can divide your warps in a logical list. For example: you can list builds other people have built in a separate category (ie "Other_Builds).
    The PrivateWarp plugin has a dependency with PluginControl. PluginControl is a plugin which handles not only permissions, but also plugin configuration (flatfile) based on groups. PrivateWarp now has per group based limitations (maxwarp and so on). This is not another Permissions system since it can use multiple Permission systems.

    This plugin has also been ported from the hmod mod. You can find the old thread here: hmod forum. The old plugin can still be used as a Canary plugin, you can find the link in the Canary forums. The plugin is also mentioned on my website here: Wrecker Technologies.

    Supported Permissions:
    -Vault (support for bPermissions and several others indirectly)
    -Built-in permission system (Groups.txt, built in PluginControl)

    • Ability to create personal private warps
    • Divide your warps into categories
    • Admin can access other warps through the /pwa command
    • A vault system with the /pwv command
    • Some other stuff not yet mentioned
    • Limit the amount of warps a user in a group can have
    • Group manager compatible
    • Permissions compatible
    • Built in fall back permission system
    Commandlist (in chat):
    • /pw
      Display your currently set private warps and categories. Only displays warps in the current category selected.
    • /pw set <name>
      Set/add/overwrite a private warp in your selected category
    • /pw del <name>
      Delete a private warp in your selected category
    • /pw goto <name>
      Use the warp , goto the location where you have set it (warp has to exist)
    • /pw catselect <name>
      Select the category (has to exist). Leave empty to return to default
    • /pw catcreate <name>
      Create categorie with given name
    • /pw catdelete <name>
      Delete the categorie (including the underlying private warps)
    • /pw help
      Displays usage and commands
    • /pwa
      All the commands of /pw except you can pretend to be another player. For example /pwa <name> set home. Sets the warp home to the player <name>. Should be an admin/mod command on most servers.
    • /pwv
      An admin can create a template(or set) of warp categories and names. These cannot be used(del, set) by the players. An admin can set a warp in the template to a player which the player can use. Should be an admin/mod command on most servers.
    • /pwv put "player" "warp"
      Set the templated warp to the player
    • /pwv rem "player" "warp"
      Removes the warp from the player
    The rest of the commands for /pwv are the same as /pw except they don't store any coordinates and it functions as a template for the vault system.

    • /pwr <nr>
      Recall previous used warps. Start at 0 (0 is the most recent)

    Configuration of the plugin(s) is done in the PluginControl data directory.
    For example:
    • bukkit/plugins/PluginControl/PrivateWarp/<groupname> (properties for that group)
    Following 2 files are only there when the built-in permission fallback is used:

    • Users.txt contains the users
      A user is defined like so: The_Wrecker=admingroup
    • Groups.txt contains the groups (first line is the default group)
      A group is defined like so: admingroup=pw;pwa;pwv <- changed due to onCommand()
      A new line is for another group or user.
    Permissions nodes :
    • PrivateWarp.pwa
    • PrivateWarp.pwv
    • PrivateWarp.pwr
    Configuration file:

    Private warp configuration file (under the PluginControl data directory)
    • max_warp=10 Maximum of total warps
    • max_categories=3 Maximum categories a player can create
    • max_warp_categorie=3 Maximum warps in a category (excluded the main/default category)
    • max_cache_minute_timeout=30 Amount of time data is considered useless (0 not ecommended)
    • cleanup_cache_minute_timeout=5 Amount of time between cleanup runs (0 not recommended)
    • Warp_timeout // configurable timeout before warping
    Todo (featurelist)
    • DynamicMap warplocations
    • Sharing warps with other players (/pws)
    • TimeStamping warps (create/modified)
    • Add comments/descriptions to warps
    • Data dir cleanup (--fixed useles creation of files, just needs a cleanup run)
    • Initial starting warp list (a list you get when you first enter the server)
    • Calculate distance to a warp from current position (possibly including height)
    • Changing on the fly config with a new plugin
    • Zones where warps cannot be set (PluginControl feature actually)
    • Cool down function for commands (suggestion from ethood1999)
    • Warp maintenance tool
    • Fix up warp count versus vault warps (partly coded)
    • Add fully qualified warp names (category/warp) Suggested by Ture
    • Warpname Template
    • Redo configuration (add warmup message)
    Having problems?
    try this:
    Loading error 1
    Loading error 2
    Try to pay attention to what the log says when starting Bukkit. Might contain some important hints.


    Version 1.7.4 RC
    • Built against 1.4.4 R0.1
    • Fix when using /pwa (out of bounds error in thread)
    Version 1.7.1 RC
    Missing some versions because those were officially released as unstable. Below changes sums up some of the changes.
    • Built against 1.2.5 R0.1
    • Upgraded permission detection (direct support, PEX and Essentials)
    • Vault Support
    • Message that you'll warp when using a warmup - timeout
    • Some internal structure changes
    Changelog (open)

    Version 1.6.4 RC
    • Built against Bukkit 1370
    • Use of new Event system
    • Beware of Permission systems (I expect a few problems due to changes/breaking of the other plugins)
    Version 1.6.3
    Does not exist (skipped)

    Version 1.6.2
    • Fix to get material type from block
    • A way to force the built-in permission system regardless of other systems installed (checks for existance of groups.txt under the PluginControl directory)
    Version 1.6.1
    • Built against #1578 for 1.0.1 support
    • JDK7 support update
    • Fix for the race condition when warping/teleporting
    Version 1.6.0
    • Fixed crash due to multi byte character reading
    • Added multithreading for every command passed through PluginControl (Meaning the whole set of commands currently available for PrivateWarp)
    • Fixed the error message when you have no rights to use the command
    • Java JRE 7 supported
    • Updated building path to create new Jar
    • Better code to read configuration property readings
    • Support for Permissions updated (bPermission, PermissionEx, SuperPerms)
    • New detection system to detect Permissions (1.5.1 fix)
    • Splitted code for handling commands
    • Player cache managing code reorganized
    • Better file handling (should disable the creation of empty PrivateWarp files)
    • Removed seperate quick and dirty warmup code
    • Refactored AbstractPlugin OO layer
    Version 1.4.9 > 1.5.0
    • Fixed default warping timeout
    • Fixed bug where warpname was passed to permissions
    • Added softdepend loading to yml
    Version 1.4.8 > 1.4.9
    • Added warping delay (default 5 seconds, adjustable in config)
    • Added rename command (/pw ren <old> <new>)
    • Added move command (move warp to another category /pw mv <warp> <cat>)
    • Added shorter aliases for known commands (see help)
    • Refactored the code base a bit for future changes
    • Built against CraftBukkit 953 (minecraft 1.7.2)
    Version 1.4.7 > 1.4.8
    • Added configbit to config files
    • Built against CraftBukkit 818 (minecraft 1.6.6)
    Version 1.4.6 > 1.4.7
    • Fix on help sub command
    • Check for blocks before warping
    • Check alternative warp location
    • Warn and notices when your warp is not quite right (warping yourself half into a step stone for ex.)
    Version 1.4.5 > 1.4.6
    • Updates towards the latest Bukkit releases
    • Fix for built-in permissions (AGAIN!)
    • Smarter cache system
    • Update for Public Warp
    Version 1.4.4 > 1.4.5
    • Updates towards the latest Bukkit releases
    • Fix for built-in permissions
    • Added Essentials Group Manager plugin
    Version 1.4.2a > 1.4.4
    • Updates towards the latest Bukkit releases
    • Still has a known issue with built-in permission system (PluginControl)
    • Seems Bukkit changed the way namespacing works... This threw errors around (IllegalAccess Exceptions)
    Version 1.4.1 > 1.4.2a
    • Built with PluginControl(0.52a)
    • /pwr change
    • Recommended build #602 update and fixes
    • Previous release is revoked(1.4.2), hence the added 'a' in this release.
    Version 1.4.0 > 1.4.1
    • Built with PluginControl(0.51)
    • Fixed /pwv put command
    Version 1.3.9 > 1.4.0
    • Built with PluginControl(0.5)
    • Changed the way how the plugin(s) output text
    • PublicWarp might be independent now
    • Removed the default_world check
    • Removed Warp converting from old PrivateWarp version
    • Did an auto updating page (see link previous versions)
    Version 1.3.8 > 1.3.9
    • Built with PluginControl(0.49)
    • Compatability update for build 522
    Version 1.3.7 > 1.3.8
    • Built with PluginControl(0.48)
    • Nothing special added or fixed for PW
    • Support for PublicWarp (test-released plugin)
    Version 1.3.6 > 1.3.7
    • Built with PluginControl(0.47)
    • Fixed null when no default group in fallback
    • Added GroupManager support
    Version 1.3.5 > 1.3.6
    • Built with PluginControl(0.46)
    • Lazy warpname matching in goto subcommand
    • Code cleanup (mainly init stuff)
    Version 1.3.4 > 1.3.5
    • Built with PluginControl(0.45)
    • Update to use Phoenix permissions 2.4
    • Constructor fix
    • Shifted to onCommand
    Version 1.3.3 > 1.3.4
    • Built with PluginControl(0.44)
    • Less IO
    • Fix to /pwv put command
    • HACKY FIX considering the constructor stuff, but works for now.
    Version 1.3.2 > 1.3.3
    • Built with PluginControl(0.43)
    • Added /pwr to help
    • Redid some logging
    • Only show conversion log when it's 'interesting'
    • Teleport hook code for pwr (probably not yet functional)
    • Some more minor fixes
    Version 1.3.1 > 1.3.2
    • Built with PluginControl(0.42)
    • MAJOR Fixes to the plugin loading thing (I hope I got it nailed this time, I haven't seen errors while testing).
    • MultiWorld!!! (For conversion to new format add: "default_world=<world_name>" in config. The Plugin will ask you to do this.)
    Version 1.3.0 > 1.3.1
    • Built with PluginControl(0.41)
    • Added /pwr command
    Version 1.2.9 > 1.3.0
    • Built with PluginControl(0.4)
    • Made calls to Nijikokun's permission static
    Version 1.2.8 > 1.2.9
    • Built with PluginControl(0.3)
    • Code for Nijikokun Permissions through PluginControl
    • Fallback to basic mode when plugin can't be loaded somehow (which was the case for me)
    Version 1.2.7 > 1.2.8
    • Built with PluginControl(0.2)
    • Removed a potential memory leak
    • Better handling when dependency is not found
    Version 1.2.6 > 1.2.7
    • Added permissions with PluginControl(0.1)
    • Per group based limitations
    • /pwv, /pwa available again
    Version *.*.* > 1.2.6
    • Removed the /pwa and /pwv command (temporarily)
    findus1994 and DoomLord like this.
  2. Offline


    I don't know ibab,

    maybe check the logging. I don't use essentials so I don't know what the red name means (maybe disabled?)
  3. Offline


    I tested out the public warp and converted it seems to be taking me to correct place provided I input the correct world the warps where made on during conversion.

    On issue tho is it uses goto command and its conflicting with PW goto and PW no longer responds to goto.
    Tho I think I used the PW in ur OP I think u also posted a seperate version for WP usage ill test that one out.
    oop I think I fixed it seems I did a mistake and set Privatewarp.wp.goto instead of adding PublicWarp.wp.goto bah and hence PrivateWarp goto command no longer existed as I changed it silly me.
  4. Offline


    I got a message about /pwa not working. I don't know what does not work since I didn't see any errors.

    Maybe you know what the error is/was?
  5. Offline


    Yes I do, It was me lol putting in wrong command, I accidently changed PW's command to PrivateWarp.wp
    Instead of adding the two seperate commands.

    They look similer when skim reading so I must of just changed it with out reading it properly, anyway I fixed it by changing it back to and adding PublicWarp.wp to the appropriate group.

    Im also pleased to say that your coverter works fine and that asside for publicwarps looking kinda rubbish in the gui side "understandable" it is working as expected.

    Also both your plugins are working on CB 531!

    I would like to take this time to point out some possible things to consider for the release version.

    1. PublicWarp Gui design could be more streamlined by that easier to read so that all warps are not just thrown into the chat pane as they are now but in stead maybe catigorized like Privatewarp and the WP command used to show the catigories available.

    Then using PW cataname would then show u you a Spread sheat cell based kind of layout like Mywarp of the warps avialable in the cata u are looking in. If you do this make it so it works like Private warp so that typing the wp command brings back up the list of current catagory ur in and not the catagory list. Maybe u need to branch off from wp such as wp.cata and wp shows what is the cata I dunno thats somthing you need to work out.

    2. Intergration with PW so that its possible to move a or copy a warp in a users PW list to WP "Usefull for those private builds that endup turning it actually towns or what not and deserve adding. " prob not needed but it would save the time of going there and adding it"

    3. Fix how the WP currently displays "added PW warp" & "PW removed warp" when adding or deleting with WP

    4. In general for BOTH plugins PW and WP add ability to rename warps on the fly with out removing them, could be tied in with PWA command.

    5. Again for both plugins ability to Filter warp names for example: I wanted to filter out all warps that contain Themed and only wanted to see warps with Freebuild in its nam, Also maybe to compliment this you could allow tagging warps instead of naming them so that users would not have to added Tags to the name of the warp. Instead your plugins could do something like /wp set Name:tag the tag would not be visible be could be called by another command such as PW or WP like this /wp tags < to list avilable tags.

    These tags would be stored with the warp information and it would allows admins and other users to actually tag there work such as ThemedTown or FreebuildZone ect and then u can combine the tag with filter such as
    /wp tag to only show warps with the specified tag.

    That should give u something to think about on the way back home! :p take care!
  6. Offline


    Sweet that it works.

    And yeah, I'll got stuff to improve on. You sum things up nicely and then some. Thanks.
  7. Offline


    Confirmed working with build #556. [​IMG]
  8. Offline


    I'm getting the same thing on my server running build 556(not running essentials though) and in the console it says:
    [severe] pw: enter a default world in your default group config
    [severe] pw: for example: "default_world=world"
    [severe] pw: current default group is: default_world
    [info] pw: is not getting enable resolve issues first!
    [info] pw: Just got disabled
    [info] publicwarp got enabled
    so I went into the default file and entered in the name of my world but still gives me the issue(although previously the file is empty)
    also the private warp folder created is made inside the plugincontrol folder after I initally run the server for the first time, is that normal?
  9. Offline



    Yes that is normal. Under PluginControl you have the configuration which is per group...

    Did you enter the config in default_world? Maybe my plugin is wrong about the default group, not sure.

    if you are not able to figure it out. 1.4.0 does not have this configuration thing anymore and should work again right out of the box.
  10. Offline


    When are you going to be releasing version 1.4.0?
  11. Offline


    Released 1.4.0


    I still don't know what problem you have. Check out the logging when the server starts. Or try out the new version.

    My best guess is the default_world thing again. It seemed to be a real pain for most... Had to be done to be backwards compatible with the old warps. Is now removed in 1.4.0

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: Jan 8, 2016
  12. Offline


    Did an auto updating page (see link previous versions) ?

    also I might be getting this the wrong way but I thought WP and PW bothed used the same goto command in this case PW and WP both no longer play nice with shortnames and it appears to be case sensative!
  13. I updated to 1.4.0 and it started working just fine. Thanks.
  14. Offline


    Not with public warps its not!
  15. Offline


    Your right that public warps is not playing nicely. You probably have an old version (with the same version number , sorry about that!).

    The version number still says 0.1 , but from now on it isn't a prerelease. The version number will now be raised when a new version is out.

    One of the reasons why I made that page (previous versions link, see first post) is to keep older versions as well. It's a php script that reads the version number from the actual jar/zip file. Which means when I place a new jar it'll automatically show the version from within that file. -- I hope that makes sense.

    I didn't change the logic whith the goto command (not intentionally). And yes you are right it is the same code base for both plugins. Part of it anyway....
  16. Offline


    Um yea I did not follow much of that really sorry!
    I understand its a version issue but thing is public warps is not even listed on the OP I can't update that you need to send me a new version that works :p

    Um I think I see now you host the public warp on the Prev version section and going by what you just said its version has changed but it just is not showing it on the page.
  17. Offline


    That's about right yes. It still says 0.1 (1.0 is out of beta, just so you know). Maybe should have been 0.2 already. Except not much changed in so I kinda forgot to update that. It's only the way it's compiled that is different (+some logging).
  18. Offline


    What version did u orgionally send me via email? I will have to test this stuff out but it will be friday since thats our servers update day!.
  19. Offline


    The version you got/had is dependent upon Privatewarp. This version should not be dependent upon privatewarp. Hence why it goes wrong.
  20. Offline


    hmm Well I will fix that up on friday thanx for head up.
  21. Offline


    This may seem a stupid question to you all but can anyone give me a step by step guide how to make a prv warp (non editable) that's used for a players vault and also how to assign it for them?

    And how to limit the warps a player has and can use only to that one and nothing else.

    On hey0 we have like 50+ vaults in a complex we want to keep as vaultwarp was too old and causing problems with warping in.

    We know we will be making warps one by one on request to there vaults.

    I just find the documentation on actually using this plugin lacking as to me its a little awkward and complex to figure out.

    I tried this I don't know if this is right:

    /pwv catcreate vault
    (made a catagory called vault in pwv and selected it)
    /pwv set revenger
    (supposedly set warp revenger in vault)
    /pwv put revenger revenger
    (Warp Doesn't exist)
    (Category vault no warps defined)
  22. Offline



    /pwv set vault-name
    /pwv put Revenger vault-name

    Should do the trick (except without categories). But I'll try/test it out myself if it still works.
    It's a feature that's not used much(I think). Categories should also work btw. This is just to keep it simple.

    Just did a test and seemed to work fine this way. Vault warps are displayed in blue when you do /pw. They can't be deleted or overwritten by the user(which was the whole point).

    As for the amount of warps a player can have:
    If you just want to have vault warps only. Just set maximumwarps to 0.

    To do this you'll have to edit the config file manually.
    The config file can be found under:

    groupname is the group the player is in (th file is called like that). The file is just text so no problems to edit them.

    [Edit 2]
    When the template is set you could also do the put command for the next player and the next and the next and so on. For example:
    /pwv put The_Wrecker vault-name

    The location is taken from where you are currently standing (when doing the put command).
  23. Offline


    I tried vaults me and another admin were testing and he ended up in a tree miles away.

    I made one for myself worked fine and reassigned it.

    I think i used set instead of put for the other admin.

    We will test during the day as its 3:30am here and 5am something his time.

    I'll let you know.

    If it was properly documented it would be a more used feature.

    I think you need a few howto's and tutorials on using the commands etc like examples etc on how to make a group specific vault a vault a player warp etc.

    As the plugin is kinda a little complex to use for new people but it seems to have a brilliant set of features.
  24. Offline


    I can imagine that without any documentation it's a little hard.

    Was thinking about a video of some kind in the past, but I haven't gotten around to it.

    The start post is a bit too small to explain the plugin in great detail. Maybe I should make a PDF or a seperate wiki or something. I kinda like the wiki kinda thing with a video where appropiate.

    To be honest when working on the plugin I mostly just code (and test). But I'll look into this wiki thing.
  25. Offline


    I do a /pwv put name vault

    All it comes up with is Warp has been added to player and its not where I do the put command.

    I even removed the vault warp from the player and redid it twice.

    When doing for myself I get the Warp vault has been overridden and works fine but not for someone else.

    Worked it out.

    It doesn't add the warp to your location with the put command but to there current location.

    Can this be changed to your location? (the one doing the command)

    Or a option to do it from your location and not the players?

    For us the only way round that would be to tp everyone to us when we make there vault as its a bedrock complex with boxes.

    But we would rather set the vault for them to our location when we make it which is how vaultwarps worked.

    Also how do we create a group warp so only admins can use it?
  26. Offline


    Uhm, so the one doing the command should also be the location where he is standing.
    Not the location of the affected player.

    I thought I had it programmed that way, but since I test it with mostly 1 user (myself) that could've slipped through.
    I'll check it out.

    Yep, I had some code in there that actually looks up the 'victim' and passes that one instead of the issuer.

    When the 'victim' is offline the issuer is passed to that function (can't find the actual 'victim'). I'll release a fix for that(new version) after I have done code to rename warps. Maybe this evening (GMT+1). Otherwise it'll be tomorrow.

    Did an update to 1.4.1

    Only it does not have renaming yet (Didn't have the time).

    @Revenger can you test it out?

    Oops, reuploading the files.

    -- Should be ok now

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: Jan 8, 2016
  27. Offline


    Yep will do as soon as someone joins the test server.

    I'll also test this muliworld as we have been thinking of just one but somehow me and another admin in out half asleep stated decided to set up 4 of them and are planning 4 when we go live so we can have each type of gameplay element.

    Not fixed unfortunately the warp still is at the player.

    If you want to join my our test or me to yours to test this just ask.

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



    Just a question though. You're saying the warp stayed at the player. What do you mean exaclty? Do you mean that the location is taken from that (victim)player when doing put (which is not desired)? That's what I am reading from your post.

    I wan't to be on the same line of communication with you so we are talking about the same thing.

    Maybe I should come along to test or you come to mine. I guess I need that "a-HA" moment about what is going on. Except I'll have to travel tomorrow (12 hours). Maybe something for Sunday, not sure. I'll let you know.

    Meanwhile I'll try to test it out by starting two clients. I just hope my RAM keeps up (haven't tried that before).
  29. Offline


    Yes when you /pwv put player vault the location is taken from that player you are giving the warp to.

    Yep its definitely not a desired thing.

    Ive been testing it using /pwa player goto vault and had a couple people test also.

    Sure on the testing I'm in Perth so its +8 gmt I'm fine to test whenever as long as its not during the F1 :p
  30. Offline


    Just popping in to report that I'm back and in the office again.
  31. Offline


    Sweet just send me a msg etc when you want to test etc

    Mt timezone is +8gmt and I'm usually available between 11am and 11pm my time.

Share This Page