Inactive [TP] xWarp v3.1.7 - MyWarp fork (w/ prices, economy, visibility) [1.2.5-R1.0]

Discussion in 'Inactive/Unsupported Plugins' started by xZise, Jan 17, 2011.

  1. Offline


    Hello everyone,
    I forked the MyWarp project and added some functionality. In basic it is the same as the MyWarp.

    Now on BukkitDev
    This plugin is already on BukkitDev. I will transfer this post to BukkitDev.

    3.1.7 + marker (Tested: 1.2.5-R1.0)
    3.1.7 (Tested: 1.2.5-R1.0)
    2.12.0 (Tested: cb819, Should run ≥ cb691)
    All downloads

    The versions for other builds are normally only compatibly updates. So they don't provide other features. This means version “a-cb684” is the same (in basic) as “a-cb556” or simply “a”.
    Notice: With version 2.3.0, 2.6.0, 2.8.0, 2.9.0, 3.0.0 (or later) I changed the database layout. Previous versions of xWarp couldn't read this database. So backup it for sure.


    Changelog moved to BukkitDev. The full changelog is still on github.

    Since 2.8.0 it is possible to use prices for warp and creation. It uses the Permissions nodes to change define basic prices. Also it is possible to define a price for each warp. At the moment iConomy version 4 and 5, Essentials Economy (at least Dev build 2.2.104) and BOSEconomy supported.
    Global/Public/Private warps
    With the Version 2.0.0 beta 13 I introduce the new state of global warps. Every user can create warps for its own (public/private) like before and hasn't be aware of already existing one's from others. So Player “A” could create a warp named “foo” and another Player “B” could also create a warp called “foo”. Now to access these warps you have to specify which warp do you want to use.
    Therefore I added a parameter to specify the owner of the warp. To warp to the “foo” warp of Player “A” you simply type:
    /warp foo A
    You could exchange the second parameter (= A) with a B to warp to B's warp “foo”.
    Now to shorten the warps you could globalize a warp with
    /warp global <name> <owner>
    Now you don't have to add the owner of the warp. For example if somebody globalized the warp “foo” of player “A” you now can simply type:
    /warp foo
    There is one rule: “If you don't define the owner it searches the global warps.”
    But a global warp also has a owner (in our case Player “A”) so you also define the owner.
    So there is one major change: If your warp contains a space you have to escape it, otherwise it will guess the second part as a owner (to escape see the section above).
    For further information visit the wiki.
    Sign Warps
    Creating a sign warp is really easy. You have 3 layouts: MyWarp, Single Line and xWarp.
    In MyWarp your sign has two lines. In the first place only “MyWarp” and in the second the name of the warp. This works only if the warp is in the global map.
    The “Single Line” layout only needs a line with “Warp: <name>”. If there are more than one lines with this layout on one sign it won't work. The colon is optional, the W could be lowercase and the spaces between “Warp:” and the name have to be at least one.
    With xWarp layout you could place “xWarp” in the first line (case-insensitive) or “Warp”/“warp” and optional a colon.
    In the second line is the name of the warp and in the third the owner (optional)
    Upcoming changes
    Backups? (unknown)
    If possible I maybe make it possible to backup the warps with others backup plugins. It is only an idea at a moment, but maybe sometimes xWarp supports this.
    tkelly's suggestion system (Suspended)
    tkelly created a system, that can get a warp similar named if you didn't spell it right.

    Fabian aka xZise
    RazorFlint, Taranis01 and uitology like this.
  2. Offline


    Could you please force the warp list to show the full name of a warp? Mine ends up showing like this.
    As you can see, the warp names are getting cut off.
  3. Offline


    No I could see any names cut off. If I cut the name off, it will be replaces by "...".

  4. Offline


    Some of the names actually are cut off. The one titled treehous, is actually treehouse. The one called S is called something much longer, but I don't know what because it is cut off! If I try warping to S by Syndromedown, it says the warp does not exist. When I asked the player about it, he said the warp was actually called Sunrise.
  5. Offline


    Okay, I will look in the code, what is wrong there. But the only problem is, that it looks ugly if I don't cut of the names.

  6. Offline


    My suggestion is cut off the world names and owner names, but force the warp names to be full.
  7. Offline


    I'm working with extra options in 3.0.0 to hide columns (owner/location is at the moment implemented). I'm also testing the source to improve the speed of warp list.

  8. Offline


    Excellent! Thank you for this amazing plugin!
  9. Offline


    Ok, I've read through the permissions page on the wiki and tried a million different permissions combinations, but I can't get the desired result.

    I don't want users to be able to warp to all global warps, so I give these permissions:
    - ''
    - ''

    I create a global warp called "arena" he can't warp to it, as expected and wanted.

    I grant him:
    - ''

    and he still can't warp there.
    If I give him:
    - '*'

    he can warp to all global warps. not the desired result.

    I've tried a bazzillion things, but i can't give out warps on a permissions-basis denying warps by default no matter what i try.
  10. Offline


    change '' to '[YOUR WORLD NAME]'
  11. Offline


    @1n5aN1aC: The warp “arena” is global and if you don't allow the user to warp to global warps, the user can't.
    • is a invalid permission node, as there is no<warpname>.
    •* allows the user to warp to all warps, except to private warps where the user isn't invited to.
    To solve the problem, invite the user to the warp and grant “”.

    @lolzrofl: As long as the world name is “world” the permission node is valid.

  12. Offline


    @xZise: OK. thank you. So is there no way to allow people to use a warp based on a permission node? If so, how? If not, Consider this a feature Request. :p
  13. Offline


    At the moment it is not planned. Maybe 3.0 will have the ability to allow to warp to specific warps. Maybe something like:<username>.<warpname>

  14. Offline


    @xZise: Ok, thanks for the information. I guess I can manually invite all the correct people to a warp.
  15. Offline


    the help page needs to be updated for the new list commands
  16. Offline


    Yep ;) I already noticed, but thanks anyway. Will be fixed (at least) in version 3.

  17. Offline

    Jazy Lopez

    How does the
    I tried putting .100 and it doesnt charge them? and also tried puting the global and public ones too...
    Same thing thing with the
    Help please, Thanks
    EDIT: Nvm got it, Had to make a drop list in the info section thingy (Not a permission node)
  18. Offline


    Hey can you make a command that converts the database to a warps.txt? This way if we need to we can always switch between warp plugins.
  19. Offline


    What is a warps.txt? Never heard about it.

  20. Offline


    Like the warps.txt in hmod. It just makes it easy to port the list to other plugins.
  21. Offline


    Ah you mean the hmod file? Maybe in 3.0.0 I will add specific export options, but then you will loose several information (warp specific cooldown/warmup, price, welcome message, creator (not the owner), editors, visibility … and maybe more).

    At the moment you can already use a warps.txt like text file and therefore export/import.

  22. Offline


    Any chance of an update for CB1000 and Bukkit Permissions? Currently it crashes as follows when you attempt to warp:

    22:54:30 [SEVERE] null
    org.bukkit.command.CommandException: Unhandled exception executing command 'warp' in plugin xWarp v2.12.0
            at org.bukkit.command.PluginCommand.execute(
            at org.bukkit.command.SimpleCommandMap.dispatch(
            at org.bukkit.craftbukkit.CraftServer.dispatchCommand(
            at net.minecraft.server.NetServerHandler.handleCommand(
            at net.minecraft.server.NetServerHandler.a(
            at net.minecraft.server.Packet3Chat.a(
            at net.minecraft.server.NetworkManager.b(
            at net.minecraft.server.NetServerHandler.a(
            at net.minecraft.server.NetworkListenThread.a(SourceFile:105)
            at net.minecraft.server.MinecraftServer.h(
    Caused by: java.lang.UnsupportedOperationException: Unsupported operation
            at com.platymuus.bukkit.permcompat.PermissionHandler.getPermissionDouble(
            at de.xzise.wrappers.permissions.PermissionsPluginWrapper.getDouble(
            at de.xzise.wrappers.permissions.PermissionsHandler.getDouble(
            at de.xzise.xwarp.WarpManager.warpTo(
            at de.xzise.xwarp.WarpManager.warpTo(
            at de.xzise.xwarp.commands.WarpToCommand.internalExecute(
            at de.xzise.xwarp.commands.SubCommand.execute(
            at de.xzise.xwarp.CommandMap.executeCommand(
            at me.taylorkelly.mywarp.MyWarp.onCommand(
            at org.bukkit.command.PluginCommand.execute(
            ... 12 more
  23. Offline


    Ehr? Not at the moment. All permissions values (cooldowns, warmups, prices, limits (at least)) are lost. It is already working on 1000 build but with the normal Permissions 3. Maybe there will be an update with xWarp 3, but I can't promise.

  24. Offline


    Yes thats what I mean. This is just because when I wanted to try out a different warp plugin, it couldn't read xWarp's database.
  25. Offline


    Ha! I never let you change !

    Wait for an update, and it will be possible to export this at least into hmod.

  26. Offline


    Having a wierd issue where warps are saved with different name capitalization e.g. Andypandy89 and andypandy89, which causes the user to be unable to access those that have different capitalization than what his name really has. Only happened to two people, but I figured I'd report it anyways.
  27. Offline


    Hmmm, are the owners of both warps are the same: This shouldn't be possible. If the owners are different it should will select the first found warp in following chain:
    1. If there is a global warp of this name, it select this one
    2. If there are only one warp of this name, it selects this one
    3. If the executing user owns a warp of this name, it selects this one
    4. If none of this determines a warp it will show an error message.
  28. Offline


    Hello all!
    I have a question:
    I saw the permissions-node "warp.create.*" can I replace the "*" with a name the warp should have that they can create or is that only for "global", "public", "private" etc. ?
  29. Offline


    I doubt, that I defined anywhere what warp.create.* does. On my wiki about Permissions you see all permission nodes that are available. And nope, it isn't possible to restrict the available names. And I don't think that I will implement this in 3.0.0 because I have no idea at the moment what would the best way to do this. I don't like to create a quick and dirty solution, which I have to rewrite.

    If you have a nice idea tell me, and maybe in 3.0.0. By the way: 3.0.0 is pretty ready. I have to add the commands to manage warp protection areas (areas where you disallow creating warps) and then I test the complete stuff.

  30. Offline


    Is it possible to set the default warp price? When somebody creates a warp, the price is assigned to the warp so the creator will be charged when using it?
  31. Offline


    Excellent plugin :) I was wondering if you could add a command that removes all 'invalid warps'? After deleting a world I have a ton of them; it'd be kind of tedious to go through them all.

Share This Page