MyWarp
MyWarp allows players to create and share warps with each other. The plugin is higly flexible: you can limit the number of warps player can create, charge for using warps, implement cooldowns or warmups, and more.
Wiki | Issues | Source | Development Builds
Note: MyWarp is compatible with every version of Spigot/Bukkit released since 1.7.10. It rarely needs to be updated for new Minecraft versions. When in doubt, try a development build.
Features
- Create public and private warps.
- Invite players or whole permission groups to warps.
- Use buttons or pressure plates to teleport to warps.
- Limit the number of warps players can create via permissions.
- Charge users for creating or using warps (via Vault).
- Use cooldowns and warmups for warps.
- Translate or change every message that your players might see.
- Store warps in an SQL-Database (H2, SQLite, MySQL).
- Supports every Bukkit version from 1.7.10 to current.
MyWarp is highly customisable, enable only what you need. Disabled functions will never impact your server’s performance.
More Information
The documentation can be found in our wiki. If you still have questions or problems, do not hesitate to contact us. To get a fast response, it is recommended to open a ticket.
The changelog can be found here.
Acknowledgements
The project was started in January 2011 by Taylor “tkelly” Kelly and later continued by Arthur “flames” Mayer and Andy “spathzilla” F. Since early 2012 it is maintained by thee.
MyWarp is available on GitHub under GPL3.
@frumple1
First, please make sure to read this article before you continue - it covers the updating process in detail and explains how you can import warps from 2.6 to 3.0.
MyWarp cannot automatically migrate the old database because 2.x lacks the infrastructure to do such a migration (3.x has it and future migrations will run automatically). To get it working, the database 'beta_mywarp' must not contain any table. You can import your old (2.x) table from a different database later as described in the article I linked above.
So in short, you should move your 'warpTable' (or whatever it is called) from 'beta_mywarp' to a different database, run MyWarp 3 once to create all needed tables and import the warps from the old table using the command.
<<reply 2508028="">>
I'm having the same problem as McOnePeace, and I'm not sure what you mean by removing the table in the "scheme". I'm trying to upgrade MyWarp from 2.6.5 to 3.0 dev build 40, and I have a MySQL database named "beta_mywarp". The MySQL portion of my config looks like this:
mysql:
enabled: true
dsn: jdbc:mysql://localhost/beta_mywarp
username: <redacted>
password: <redacted>
host: localhost
port: 3306
database: beta_mywarp
table: warpTable
The error message I get complains about a non-empty schema "beta_mywarp". If I just upgrade the MyWarp plugin only, surely it should be able to migrate the database on it's own with no manual changes to the config or database? Or, do I need to perform some extra steps here?
@McOnePeace
You are trying to use MySQL, right?
The error indicates that MyWarp tries to initialize its tables in the scheme called "MyWarp", but it fails because the scheme is not empty (otherwise there would not be a way to guarantee that the tables are created and updated as required). So you simply need to remove whatever table there is within the "MyWarp" scheme or use a different and empty scheme.
So i am still having a issue when it comes to enabling my database. If i set it to true i get this error.
http://pastebin.com/c3QG92t0
@Filmjolk
Sorry it took so long to answer you. I just updated the wiki to reflect MyWarp3 and I recommend to read the introduction article to understand how MyWarp works. To use it, you need to drop the jar from the Jenkins into Spigot's plugin folder and start your server. Than just alter the configuration to your liking and restart once more.
@Manic_Kaval
The search command has been replaced by /warp list -n <query> as the additional flags allow a far better search than the old command ever did. Warp signs should be fixed with the latest devBuild.
The facing is something I have also noticed, but for no I was unable to track it down or reproduce it. I will keep an eye on it - if you or your players notice any pattern (under which condition it occurs) please let me know.I think I fixed it with the latest commit. please let me know if you see it again. One problem through: Already imported warps will have inverted pitch and yaw. If you still have the old database around, you can easily fix this by using:Just make sure to edit mywarp.warp (new) and minecraft.warpTable (old) accordingly.
@ItIsThee
Uploaded and tested, thank you for the fix!
Right now the other issue I'm seeing is that the search function and warp sign function are broken. A minor thing too, when people warp places they are facing drastically different directions than how the person who created it was facing. Most of it is straight looking up-previously warps brought you looking the same direction as it was created.
@Nistune
@Manic_Kaval
Both errors ('/warp <name>' permission and usage with warp-names that contain spaces) should be fixed in the latest devBuild.
@ItIsThee
okay awesome thank you for being such a great help! I will give it a try when the server is not busy :)
So I'm running a 1.8 spigot server and I can't seem to get mywarps 3 working but i'm most likely doing everything wrong. I have never used the earlier versions of the plugin so I'm not very familiar with it. Any help on how to set it up?
@McOnePeace
Err, it seems like pastbin messed up the formatting. Try this one, it works for me. And are the world names correctly written? Is the case correct?
On other note, I updated the limit article for MyWarp 3.
@ItIsThee
okay some thing is not right. I used the config you sent me, but when I start the server it just replaces it with the default config. I tried doing it in game and it shows the changes but does not react to them. What should I do?
@ItIsThee
I just tried this. It successfully created the warp with two words, but when attempting to warp to it it reads:
This is when both trying the warp as
@Nistune
Warp names with spaces are still supported, they just need to be enclosed by quotation marks like so: /warp create "spaces are awesome".
The permissions issue seems strange, I will investigate as soon as possible.
Not sure if its a bug or a feature (I hope its a bug) but we can no longer make or warp to two word warp names. For example, if I type /warp create two words it says:
'Too many parameters! Unused parameters: words null'
Despite users also having the following permissions, when they try to warp anywhere, they are told 'Insuficient permission.'
These were not issues before we updated. Not sure if im missing something thats changed dramatically since we updated.
Edit: Well I added the following permissions to the group and now they can warp again, seems messed up.
@ItIsThee
Thank you so much I will give it a shot tomorrow. If i have any issues i will let you know thanks again!
@McOnePeace
I converted the custom limits and fees from your old configuration into your new one. Even if you plan to modify the values, this should clarify what syntax is needed.
http://pastebin.com/0EFHe3hZ
By the way, if a limit should cover all worlds, it is recommended to omit the affectedWorlds list altogether.
@ItIsThee
I tried that and when i touch anything in the config or change anything it does not work. I reload the plugin in game and it still goes off the default config. Then if i reboot my server mywarp stops working. can u send me a example config of just a custom limit? I will send what I have.
New config: http://pastebin.com/Rgg3VyRV
Old config: http://pastebin.com/p9hwB3Ti
@McOnePeace
Economy, timers and limits work like they did in old versions: The values defined under default apply for anybody, those defined under configuredLimits (or configuredTimers, configuredFees) for those who have the corresponding permission. The key names should be self explaining.
You can copy the actual definition from the default one and just rename it. If you need an example look at this file.
the config set up is different from the old one. where can i find out how to set up my limits and economy for it. the wikki does not have a tutorial on it
I just pushed a massive bugfix for UUID and invitation storage, I absolutely recommend to update to the latest devBuild as soon as possible for MyWarp 3 users. MySQL should now finally work.
In short, there was a massive logical bug with the the way UUIDs where experted to be stored on the database site. This rendered MySQL completely useless and SQLite only worked because it is not as type strict as MySQL (which is normally a bad thing). The issue has been fixed by an update on the database scheme which should not cause any data lose (in MySQL there was no data, in SQLite the data technically had already the desired format).
Additionally I fixed a bug that prevented proper storage of invited players and groups when importing. So maybe you want to re-import.
Please let me know if there are any errors with this version. I want to get a somewhat stable beta out as soon as I can.