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.
@ItIsThee
I guess I had a gut reaction to seeing a 25x size increase from 2.6.5 to the latest beta. It just looks like unnecessary software bloat.
The problem is not so much performance or file size, but memory usage. Run a handful of plugins and the memory usage adds up pretty quickly. I don't want to have to be forced to pay for and run a higher-tier server instance because I'm hitting the ceiling for memory usage. A recent trend of quite a number of plugins I use has been for them to be ballooning in size. My options are either don't run plugins, or gently request plugin authors consider more use cases for their plugins, or in other words, optimise for memory usage, speed and then maybe file size.
Whilst I'm all for you using well tested external libraries, I personally am unlikely to ever need H2 support, so could this be optional for example? I get that you're trying to make it easier for less technical server owners, which is commendable, however providing more detailed options for those not afraid or those who are able to tweak to their liking would be welcome.
@TWSSYesterday
Why? From a technical point of view, I do not understand it. File size has nothing to do with performance, file-size is not application critical for plugins as it is is web-applications. Besides the requirement to manually install additional libraries might be an even higher put off than the somewhat larger file size.
@ItIsThee
I think that would be best, the large file size is a huge put off to potential users.
@Pessh
Is there a reason why 4MB are problematic? MyWarp is not a web-application that users need to constantly download and servers should normally have a fast connection. If you worry about performance, file-size and performance have nothing to do with each other.
To elaborate, the larger size of the MyWarp 3 versions is caused by the bundling of libraries that MyWarp uses. These libraries (e.g. FlyWay, JOOQ, slf4j and H2) greatly improve the code quality, reduce the source of possible bugs and allow me to implement new features much faster. Therefore, removal of these libraries is not an option.
To reduce the file-size I could either use external tools that modify the source code to take less space. While this works, the produced code is hard to understand for humans meaning BukkitDev reviews would take significantly longer, if they accept the file at all. The other option is to require that users install the required dependencies by themselves. This has been proven problematic, especially because not everyone has the technically knowledge required. Additionally some Minecraft hosters do not allow altering the start-up script, making installation of additional libraries impossible.
If requested, I can provide an additional download without the libraries on the continuous integration server.
Love your plugin - but the latest version is 4.0MB - please can you try to slim this down a little?
@TWSSYesterday
Beta-2 should work well with 1.8.x (as does Beta-1, except that the import command was not working due to Spigot's updated Guava version - that is fixed now).
Latest works with 1.8.x? Can't find any commits that suggest updating to it/support for it. If not, could it be worked on next?
Thanks :)
@mcly
The error indicates that the schema
warpTable
does not contain the tablewarp
. It seems like you got the command's logic wrong.You want to import warps from an existing MySQL database running on
localhost
, from the existing schemamywarp
into the database used by the running MyWarp instance (probably H2), right? If so, the following command should do the job, just replace username and password:@ItIsThee
Thanks, I updated and the command works. However, I encountered an error while trying to import, hope you could help:
http://pastebin.com/AQG2K9C6
I created mywarp schema via MySQL Workbench using utf-8.
@mcly
Are you using the latest devBuild? The import command changed compared to 3.0-beta1.
I typed /warp import current jdbc:mysql://127.0.0.1:3306/ mywarp username password
The correct format, however it always returns with "Please choose a sub-command"
You can now easily contribute custom localizations using the crowdin localization service. If want to use MyWarp in your language, please contribute your translations so I can include them in the official version.
@mustang_guy
If you are not very technologically-literate, I would recommend to use the build-in H2 database which is automatically managed by MyWarp. To do so make sure you are using the latest devBuild.
The command to import warps from an older MySQL database is the following:
To fill in the values have a look at your existing MySQL configuration witch should look somewhat like this:
mysql.dsn
except the word behind the last slash,mysql.username
,mysql.password
.So, given the values above, the import command would look like this:
if this does not work or you have additional questions, feel free to send me a private message with your current configuration file - just make sure to remove username and password.
Hello, I just updated to v3.0, and want to migrate my old warps. I have read the documentation, but do not understand it. I am not very technologically-literate. I know my server uses MySQL, but I don't believe my host grants me full access to it, so I don't know much about the database. If you can help me migrate the warps, that would be great. Thanks.
@ItIsThee
Thanks I will remove those extra files. Would rather have less files to look neat.
@Ironic8b49 The files you listed where created by MyWarp 2 and are no longer used. You can safely remove them.
In new MyWarp3 installations the plugin folder should only contain the
config.yml
, theprofiles.db
and, if the default H2 configuration is used, the database fileswarps.h2.db
andwarps.lock.db
.@ItIsThee
Thanks for the quick response I edited my question about files and added more.I run a backup program which backs up complete server every 30 mins.
@Ironic8b49
profiles.db
: Used to store player names and UUIDs since there is no such function in Bukkit,warps.h2.db
; The H2 database that now stores your warps,warps.lock.db
: A file created by H2 to lock/unlock the database. Should be removed automatically when you shut down the server.mywarp.db
: The old SQLite database.I still recommend to keep an backup of the SQLite database somewhere in case something went wrong.
@ItIsThee
I ran that command with correct path and it imported my warps. My question is which database file can I delete out of the MyWarp folder since there is 4 now, or do I need them all. warps.lock.db, warps.h2.db, profiles.db, mywarp.db Along with these files mywarp_lang_en.yml, mywarp_lang_de.yml, mywarp_lang.yml, en_US.txt, de_DE.txt
A note for early adopters of MyWarp3:
Starting with devBuild #83, you will need to reconfigure your database in the configuration file, as described here.
I overhauled the code that handles warp storage, made several great improvements and added H2 support. Unfortunately at least SQLite 3.8.7.2 is required - CraftBukkit bundles 3.7.2 (release in 2010). After upgrading, MyWarp will already have a configured H2 database in its plugin folder that should be used instead.
To import warps from your SQLite database use the following command:
Let me know if you have any questions or need help with the migration. Also consider voting for updating the SQLite driver at Spigot's bug-tracker.