Bukkit

Welcome to the next release of uHome - v1.5!

This update brings in a large list of changes, depending on your previously used version. For upgrade notes, please read on. A complete changelog follows.

This update includes anonymous usage statistics tracking provided by mcstats.org. Your server ip will not be made publicly visible by these statistics. You can view all of the data collected by the website here. I would appreciate you leaving this enabled, so I can see how my plugin is used, but you may disable it at any time by editing the config.yml in the PluginMetrics folder in your plugins directory.

Upgrade Notes

For users of v1.4.1

If you are updating from the last stable release (1.4.1), please make a backup of all your uHome files before upgrading. I strongly advise creating a new config file if you are in this situation - it has had some considerable changes, which will mean not all of your old config values will be recognised by the new version. To create a new config file, simply delete or rename your config.yml file from your uHome folder. You can find information on the new configuration options on the configuration page.

This update contains changes to the database structure. Your database should be automatically updated after first run. Again, I strongly suggest you make a copy of your database (uhomes.db, if you are using the default, sqlite). Once your database has been upgraded, it will not work with earlier versions of uHome, so if you have issues that force you to downgrade, you must have this backup copy available.

For users of v1.5b

There are very minor changes between v1.5b and v1.5. The new uHome.jar should work with your existing config.yml and database, so simply replace your old uHome.jar with the new copy.

For users of v1.5a.x

Direct upgrade from the alpha versions of 1.5 is not supported, but may still work. If you are still using v1.5a.3, for example, you should upgrade to v1.5a.4 first, then v1.5b, before moving to this version. Depending on how many versions behind you are, your database may need to be updated and your config file may need some changes.

For users of v1.4 and below

You should first upgrade to v1.4.1 before updating to v1.5. As with the above section, this may or may not be necessary, but is not supported and has not been tested at all.

Changes since v1.4.1:

• Fix a bug that meant looking around causes warmups to cancel.
• Implement economy support using Vault.
• Implement plugin statistics using metrics.griefcraft.com.
• Add importer for CommandBook homes.csv.
• Implement per-home invite limits.
• Implement dynamic config based permissions for all warmups and timers. Custom permissions nodes, with as many or as few levels as you'd like!
• Fix cooldowns to only activate if a warp was successful.
• Fix InvalidArgumentException on plugin reload.
• Stop default variable limits from being created if the user has already created some.
• Fix the /sethome command to act exactly like /home set
• Fix config InvLimit section creation.
• Fix plugin metrics graphing.
• Check bed settings when using /home set.
• Show a warning if bedsCanSetHome or abortOnDamage are set incorrectly.
• Minor improvement to invite list performance.
• Implement access time recording and matching 'home purge <number of days> command. Console only, must be enabled in config. (Potentially resource intensive and dangerous - enable at own risk!)
• Fix a bug where invites were not deleted from the database when homes were deleted.
• Check the invite table on startup to delete any orphaned invites leftover from the above bug.
• Fix missing delete variable in home set error message.
• Fix a bug where chunks are loaded on teleport even if the event was cancelled.
• Implement 'home dump' console command to dump all homes to an sql file for easy backups/exporting to new server.
• Implement import of homes from MultiHome plugin from filename 'multihome_homes.txt'.
• Change commandbook import behaviour to only import from 'commandbook_homes.csv'.
• Reduce respawn listener priority to allow other plugins to override our catch-all behaviour.
• Implement home locks - allows players to set their homes as unlocked, so that any player who knows the name of the home may warp to it.
• Add command '/home lock <home>' and '/home unlock <home>'. New permission node: 'uhome.own.unlock'.
• Add config toggle for home locks 'enableUnlock'.
• When backing up the database, copy the sqlite file if not using mysql, rather than backing up internally.
• Fix a bug where players with homes with very similar names cause an internal error on warp.
• Only show metrics message if it's enabled in the metrics config.
• Only collect invite limit statistics if invites are enabled.
• Clear internal invite list when a home is deleted.
• When searching for intended destinations, consider invited homes.
• Fix SQL errors if importing from MyHome with MySQL.
• Fix an error when deleting homes.
• Fix lock and unlock command behaviour.
• Show unlocked homes as coloured in home list.
• Implement import from MultipleHomes (very old plugin, added by request - unknown version).
• Allow respawnToHome setting to be set on and off for each world.
• Implement custom formatting of both /home list and /home info. Home list can now show the traditional list of names in a single message, a detailed overview of each home on multiple lines, or somewhere in-between. (No pagination support yet!)
• Implement notification messages when players are charged by uHome.
• Implement import from HomeSpawnPlus
• Added Russian (ru) translation - thanks linkinkov & Schmarotzer! To use the russian translation, simply set "locale: ru" in your config.yml.
• Show locale contributor in startup messages.

There are currently no known major issues with this version of uHome. As always, update with caution, and make a backup of all your uHome files before updating!

Some users are experiencing issues with teleporting into the ground when using /home over long distances. This is a bug related to chunk loading. To remedy this, you can try setting "loadChunks: true" in your config.yml. You may also try installing a plugin such as WorldGuard, which allows you to enable features that either disable suffocation damage completely (and so players have time to do /home again without dying), or teleport players out of the material they are stuck in while suffocation (no need to do /home again, but possible to be used to break into homes this way). A patch for this is on the to-do list!