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


    That would mean everyone has to move their privatewarp files to the plugin directory. Not sure if the rest of the user base wants to do that. It does clean up the bukkit directory a little (less clutter).

    A small change I can compile in the next build (upcoming weekend). So if no one objects I'm putting that in for you.

    I'll come up with some solution this weekend one way or the other. I'll do my best. I'm trying out my own plugin first, because of the configuration stuff I have in mind.
  3. Offline


    Permissions integration would be nice too, and a way to limit warps by group/user.
  4. Offline


    I'm fine with moving the files to the plugin dir it seems all plugins are doing this now anyway. maybe offer support for both ? Its apprently really easy to intergrate all the code is supplied u just whack it into your plugin.
  5. Offline


    I'm not going into the trouble of supporting both options since the folder is variabel data given to the plugin. And because the configuration for the plugin is in that directory which can be configured it would be messy.

    I'm not too good at explaining things tonight, but I'd like to say that the move has been succesful. One less todo for the next version.
  6. Offline


    I would donate a fair sum if you could do a couple things:
    • Permissions integration and a way to limit warps by group and maybe even user.
    • Some sort of zone system where you mark cuboids where warps can not be set. Better yet leave the cuboid work up to WorldGaurd and just let us specify region ids you can not set warps in or warp to (incase people already have them set there.)
    • Allow commands to be configured so I can change: /pw goto warpname to /pw warpname, /pw set to /pwset, /pw del to /pwdel, etc.
  7. Offline


    I'm doing some programming work right now.

    Not sure about the commands, maybe that should be more modular. Gotta think about that one.
    The cuboid/worldguard idea sounds cool. Maybe a nice addition to support it natively or through this permission thing I'm working on.
  8. Offline


    I like the import of the hmod private warps. It seems to have imported them but I can't figure out how to use them. When I have the warps listed, it always shows like "0 (5)" or "0 (3)"... seems they are there somehow but I can't "/wp goto WARPNAME" that I used in hey0.
  9. Offline


    What do you mean? What did you do? I don't exactly follow. Did you use the converter?

    The format hasn't changed (hey0 vs bukkit) as far as I know. So I'm not sure what problems you have. Can you explain a little more?

    Just to be sure the Converter is built for the waypoints plugin in hmod!
  10. Offline


    yes, I used the converter and it seems to be fine... if I do a cat on my username file I get some binary data... if I open the file in midnight commander, it is clear text with three warppoints.

    However ingame it looks like the screenshot below. I don't know how to access the warps.

    Attached Files:

    • pw.png
      File size:
      154.5 KB
  11. Offline


    the privatewarps folder needs to be in the craftbukkit.jar folder not the plugins folder.
  12. Offline


    ah... I'll try that... thx

    yey, we got our warps back :) thx
  13. Offline


    I'm glad it's working again for you!
    Please note that the next version probably forces you to move the warps again. The folder is moved to the plugin folder.
  14. Offline


    :) it's fine... now I know
  15. Offline


    Great! I can disable commands and enable them again with a textfile. Now to test out the groups and the Properties. The properties file has been moved as well to another plugin. It completely handles it together with the groups.

    I still have a little thingy to work out, but it looks like I can keep my promise about a basic release tomorrow.
    --- merged: Jan 30, 2011 1:32 AM ---
    Groups work as well. A player can be assigned a group in the textfile. Another player can be in another group and have a different command set.

    Right now my PrivateWarp plugin only gets the default group to store it's properties (like the amount of warps), but it works and properties are nicely written to the PluginControl plugin. Now onto userbased group selection.

    It's all very basic for now, but that 'll change soon enough.

    Just to let you know how I now check if a player can use a command:
    PermissionPlugin.getPermission().canUse(input[0], playerentity.getName())
    Looks simple enough right (future devvers) ?

    Don't be fooled by the naming convention though. It's totally my code (I know I named the class PermissionPlugin, but I'm not naming my plugin that). I just had a lack of imagination at the time.
  16. Offline


    So this works fine with Craftbukkit 167+?
  17. Offline


    I'm not sure, I'm using 140 right now, but I'll build against 167 later when I release a new version. Or latest anyway.
  18. Offline


    seems to work fine on 166
  19. Offline


    I got some stuff working. I'm testing again. I modified the PrivateWarp plugin so it uses the PluginControl API. It get's it's settings from there. I have no commands for the PluginControl yet. It's basicly editing the textfiles... for now.

    I'm getting the latest bukkit version(173) and I'll be building a release for u.
    --- merged: Jan 30, 2011 4:11 PM ---
    The new version is up (1.2.7).

    I expect it to have some rough edges and it could do with some more userfriendlyness, but it worked on my system. You have to edit the txt files yourself at the moment (which is likely to change). The per group limitation is a nice addition I think. Let me know what your experiences are.
  20. Offline


    does it still work with older bukkit version (166?)
  21. Offline


    It propably will. I did not need to change my code, can't guarantee that though. So backup the old jar to be sure....

    You could always upgrade to a newer version of bukkit though, but I guess you're using other plugins which might not work on the newer.
  22. Offline


    Do you HAVE to use to this mysteriouse PluginControl, Is that some sort of official groups plugin, I would perfer to just use "Permissions plugin" until an official one is out and EVERYONE uses it.

    Our server is up again if you feel like stopping by we are taking are usual crew back to start with via whitelist then later guests.
  23. Offline


    @ledhead900, yes you have to use the mysterious plugin. It's used for the main configuration setup of the plugin and possible future plugin's. You can set different maximum amount of warps per group.

    The main reason I didn't integrate the permissions plugin by 'Nijikokun' is because you'd have a third(or fourth when you count Bukkit) dependancy. If any one of those change my plugin could break. So I try to avoid them if possible. As for the integration that would be done in the mysterious plugin anyway and not the PrivateWarp one and I tried to keep it a lot more simpler as well.

    I can understand your question though. Why run multiple plugins when you could just have 1. Well in the end I expect to have just that. Through the bukkit system. Time will eventually tell though.

    I would also like to note that this mysterious plugin can be used together with the permissions plugin. I don't expect them to bite eachother.
    --- merged: Jan 30, 2011 8:25 PM ---
    Maybe I'll remove the hard dependancy and revert to basic when the mysterious plugin isn't there.... I'll have to see how that turns out.
    --- merged: Jan 30, 2011 11:08 PM ---
    I found out about a memory leak. And did some other tweaks. I highly recommend you redownload both the PluginControl and PrivateWarp. V1.2.8 will be up in a few minutes.
  24. Offline


    yea righto, Re downloaded, I'm debating on just not even setting a group as all our groups have the rights to use /pw and since u removed the admin /pwa and /pwv I dont really see a need for permissions support at all. At least not for us. I still think this will play nice with Niji permissions.

    Unless you hardcorded it to only accept that plugin thingo, But with Niji it is working fine now using just the /pw command not using a node system so at this time I understand u dont support for using '' or 'privatewarp.*' as they are the node system commands that only work when you support the permissions plugin.

    But so far every plugin we have regadless if it is supported or not we have managed to get working via niji's using / commands in place of the nodes.

    Do you see any reason why this won't work, I mean if worst comes to worst I could just run your required plugin thingo and but can you add a way in you config at all so it you don't even need a permissions system if you don't want one.

    Like for my example above default group always gets the rights to use /pw so why cant we just have /pw function with out group control via a toggle option in its config maybe.

    I was also thinking of some way to improve this and I think we need an alternative option on viewing pw lists. like maybe the way it is now should be th short list but say if you type /pw listhomes or something like that it could just show a flat list unorganised with numbers like /pw listhomes 2, /listhomes 3, ect

    To explain this a little better to get more of a visual image of the idea, User types /pw listhomes

    It just spews out a list of all there homes like how the MyWarps Plugin shows its warp list, with page numbers.

    Just thought that since some people dont care about sorting the list into categories.
  25. Offline


    Just a small note,

    the /pwa and /pwv are re enabled... Just thought to let you know... Since we have some form of permissions... That was the idea, so I could enable them again.

    Hope it helps.
  26. Offline


    Is there also an option to make "public" warps?

    I would to give mods and above the ability on my server to create "public" warps that can be used by anyone. right now I run this plugin and the mywarp plugin to have achieve that goal. However I'd rather prefer only one plugin to be loaded as privaewarp and mywarp are quite similar.
  27. Offline


    Hmmmm it would help but I don'think this will play nicely with niji's I mean I could dupe the groups but thats kinda running two permissions plugins, not exactly a good idea, I liked it how it was before tbh wrecker as goup support worked fine with niji but now since we are forced to use that plugin thingo I can't even assign /pw to niju groups and make it work.

    I understand why you waitied to do it but you basicly just made yet another permissions system see what is going on right now is everyone is eathier support niji or just not making permissions. When you Don't support niji but dont have permissions you can just assign the / commands inside niji's permissions and it will pick it up just fine.

    so really all we would have had to do to get this working with /pwa again would be to give our mods group /pwa and presto it will work fine since nji's uses herichial structure it would give the command to any group above the group the command has been given to.

    I truely think you should just allow us to eaither use your plugin manager thingo or at least make it not rely on it so we can still use / commands in niji as this current release broke that support we already had for the Permissions plugin.

    Eaither that or you have not updated for the 183+ carftbukkit build that recently re designed the command hooks.

    I hate to be a pain but adding your own groups kinda made it worse lol. You did not support niji by using his code but this plugin still ran perfectly when added as a / command.

    See Supporting permissions plugin only gives the ability to use nodes like I showed in my above post with no support but no other depedency's you can simply add the / command and it will follow niji's permissions system.

    It's how we had it working up until now but now I have no idea what to do with it. As im not about to write up new set of permissions to work with your plugin manager.

    I know nothing about the manager for one and secondly its bound to cause issues when the other permissions plugin handles everything else inc promotion of rank. since other plugins we use suppoer niju rank system it all work along side eachother.

    But with yours in the mix I now have no way to give /pw to every single group in a hirachial structure.

    so please please please, just bring it back to how it was before you can still add the /pwv and /pwa they all work along side niji just fine.

    Like I said you just can add things like Pluginname.command unless you support his permissions but it dont matter if u dont as u can still add the / on there own to groups u desire and it works.

    Damn I repeated my self to much, maybe its how much I prefer the old method of using this.
  28. Offline


    Got it, will look into it this evening.
    Sorry I'm a little short of text. I'm working right now.

    The PluginControl is actually an addition to basic permissions. I'll most likely let PluginControl talk to 'Niji's Permission plugin (by detecting it if you have it). I needed to have groups because of the propertiesFile becoming group dependant.

    I'll fix something up...

    Right now when you set this in groups.txt (just this one line):
    and leave the users.txt empty

    It should create a default config under the Plugins/PluginControl/PrivateWarp with basic settings. While everyone can use the commands (/pw, /pwa, /pwv). Basically disabling PluginControl in some way. Little bit how it worked before, except the configuration is now handled by PluginControl. You can actually see that PrivateWarp shrunk in size because of that.

    Than you can keep your permissions settings and groups as usual and give out the /pwa /pwv only to the admins from the permissions plugin. They should not get in the way as far as I know.

    Try that out for now. I can't cuz I'm not at home.
  29. Offline


    oh I see ok so basicly just let your plugin tell the game that anyone can use the commands, then let niji's permissions detect the commands are avilable and sort it from then on. I thought about it that way as well as not sure how it would have went down tho, Guess Ill give that a go, I was just suprised coz i did not setup the config for plugin handler you used, I installed the plugin as private warps had a bitch with out it :p.

    But yea no commands showed up in game with it just added to niji's it did even give me a you dont have this command messege, thats what made me think u missed update of bukkit as I know the later lot broke every plugin and they had to re do there command hooks.
  30. Offline


    Nijikokun's Permissions support is -absolutely- necessary before I, or also the majority of other users, will decide to actually use this plugin.
    It's a very useful, and in my opinion, necessary plugin, but as everything else out there is following Niji's standard and making their plugins compatible, it's hard to decide to use the one plugin out of the many that I use, that does not.
    Edit: I would suggest just releasing the code, and allowing someone else to make it support Permissions. Then pick it back up where you left off, once it does.
  31. Offline


    Fair enough that you think a permission(in this case Nijikokun's) system is necessary. That is your opinion and possible that of other users as well. As for the PluginControl plugin. That's where the bind to Nijikokuns plugin is going to be made. So not directly through the PrivateWarp plugin. This allows me to get extra hooks for multiple plugins. And on top of that support for the new bukkit permission system (if all goes as planned anyway). So the best of most worlds in my opinion and less likely to break when changes are made.

    Wait before jumping to conclusions... it's just all in my head here. And just for the record, as stated before. I don't release the code. I was planning API support for The PluginControl though.

    to recap:
    So it's true that I do not support Nijikokun directly in the PrivateWarp plugin, but the support will eventually be in the PluginControl one. And as the plugin relies on the PluginControl it'll eventually have the support as well. Hope it makes sense now. When it occurs that the Permission plugin does not work (for whatever reason), the basic stuff can kick in.

    This gives another advantage. When you want to migrate to the bukkit system later. I hope it all makes sense. I have seen too many stories that things don't work because of another bukkit version and so. As said before, I want to prevent that. I could also add support for even more control/permission systems this way, making things even more usable.
    --- merged: Jan 31, 2011 9:55 PM ---

    I got the Permissions thing written into PluginControl. Except I keep getting a nullpointer return (my plugin tries 10 times before reverting to basic functions). I got it working just once and the config worked that one time.
    When I browse through the topic I can see that more people are have similar problems. Could it be that it's broken with the latest 187 build?
    You should browse through that topic and read about the errors. There are a lot of them.

    Anyway, I put up the new build. It reverts back anyway so it keeps loading the old way if things don't work out. Maybe you guys have better luck with it than I do.
    The config should be something like this in Permissions:
    /pwa PrivateWarp.pwa
    /pwv PrivateWarp.pwv

    Plugin test = this.getServer().getPluginManager().getPlugin("Permissions");
    if(test != null)
    PermissionHandler p = ((Permissions)test).getHandler();
    In the code above p == null. Which if not handled will crash plugins... I haven't seen it any other than null.

Share This Page