fix for rare case where faction home location's world being removed or renamed (world with specified name not existing) could lead to NPE
Improved explosion handling speed
New cape system and refactored spout appearances.
Some minor fixes to the previous commit.
Fixing a few apperance bugs and stopped updating apparance if it was the same.
Now using automated help. Fixed SeeChunk issues.
Simplified the perm command.
Delete a couple of files which are no longer used
New "access" system to replace old ownership system. Access can be granted to build, destroy, and fully interact within any chunk for specific players or factions. Access can also optionally be denied to normal members of the host faction.
Some further info display to go with this feature is yet to come, and further testing for possible bugs is also needed.

Related info:

New FPerm "ACCESS" which is granted to faction leaders and officers by default. This FPerm allows you to bypass access restrictions throughout your faction territory, and (along with the "factions.access" Bukkit permission below) allows you to change access settings for any chunk owned by your faction.

New permissions:
factions.access - Ability to grant territory access for your faction, if you have the proper "ACCESS" FPerm (defaults to leaders and officers only). Added to factions.kit.halfplayer permission kit.
factions.access.any - Ability to grant territory access for any faction on the server. Added to factions.kit.mod permission kit.
factions.access.view - Ability to view territory access info for your own faction. Added to factions.kit.halfplayer permission kit.

New command:
/f access [view|p|f|player|faction=view] [name=you] - view or change the access information for the chunk you are in. If "view" or nothing is specified, it will simply display the info. If "p" or "player" is specified, a player will be granted access, or removed from the list if they were already granted access. If "f" or "faction" is specified, the same will be done for the specified faction. The name defaults to yourself or your faction if not specified. If your own faction is specified, you will toggle restricted access for the chunk so that normal faction members can be denied access, unless they are in the access list.
Examples:
/f access - view access list, if in your own territory
/f access p SomePlayer - grant access to player "SomePlayer" for the current chunk, or remove them from the access list if already there
/f access f - toggle restricted access for the current chunk (since faction name isn't specified, uses your own faction), assuming you're in your own factions territory
Added back a FactionsBlockListener.playerCanBuildDestroyBlock() method which references Location instead of Block, mainly for backwards compatibility
Removed bit of code which was apparently intended to optimize movement event code but which was actually slowing the process down a bit overall
Brief access info is now displayed under two circumstances: if you have been granted explicit access to the territory you are in ("access granted"), or if you are a normal member of the faction which owns the territory and access is denied to you ("access restricted"). This info will be displayed through Spout under the faction tag if possible, otherwise it will be displayed through chat.

New conf.json setting:
"spoutTerritoryAccessShow": true,  - whether to show brief access info using Spout
Changed default Spout territory faction display to upper left, since Spoutcraft client now has minimap in upper right
Release 1.7.5
Release 1.7.5 alpha: one last minor fix to EssentialsChat integration needed
added PowerLoss for negative power setting
fix evil bug with getPlayer matching online players 
if the offline player had similar name with the online player
ie. online "s2", offline "s", then "s" would show as online because
getPlayer("s") will return getPlayer("s2")
this is why getPlayerExact should be used
Merge pull request #146 from basicsensei/master

fix #145 for master branch (1.7) (thanks)
Bug fix for that wilderness painting on dynmap.
Some servers might want to disable territorial warfare alltogether.