Options are available which check the territory you're in and prevent specified commands in neutral or enemy territory, but not ones which look for enemies nearby, sorry. Something along those lines should be in 1.7. The source includes a lib folder. There they are. There is a permission for creating factions (factions.create), among our myriad permissions for basically every command. Sounds like what Olof was encountering on his server running 1.7. He thinks he might have fixed it. I'll upload an updated 1.7 build in just a bit when I post 1.6.4. EDIT: as a reminder, though, the 1.7 branch is still in alpha state and thus not recommended for live servers unless you really know what you're doing. 1.6.4 should be ready in the next few hours. 1.6.4 is now released. Changelog copied from our main changelog so hopefully a few more users might actually read it: New command /f powerboost <p|f|player|faction> <name> <#>, which will apply a permanent power bonus/penalty to a specified player or faction. When applied to a player, it will affect their max power and min power. When applied to a faction, it will be applied to current and max power levels. Whether it is a bonus or a penalty depends on whether the number you specify is positive or negative. Any power bonus/penalty is displayed in /f power and /f who output. New permission factions.powerboost which is required to use the command. This permission is added to the factions.kit.mod permission kit. (added thanks to a donation from Kain888) example usage of new command:/f powerboost p Player1 1.5 (give player "Player1" a bonus of 1.5 power)/f powerboost f SomeFaction -6 (give faction "SomeFaction" a penalty of -6 power)/f powerboost player Joe 0 (set player "Joe" back to no power bonus) Players no longer regain power while dead; you can no longer simply stay dead and delay your respawn in order to regain power. Added CaptureThePoints, CombatTag, and AuthDB to our softdepend list so they can potentially catch and cancel Factions commands. Updated our event handlers to use the newer Bukkit event system. Fix for error when deleting a faction if Vault wasn't present. Fix for slashless Factions commands not working for player in faction chat or alliance chat modes. Fixed NPE in LWC features (by patrickfreed, thanks) Fix for a potential NPE in FPlayer autoLeaveOnInactivityRoutine. Fix for users who have Vault but don't use economy getting an NPE. Workaround fix for half-step placement on existing half-steps not being prevented; it's caused by a CraftBukkit bug: https://bukkit.atlassian.net/browse/BUKKIT-646 Removed our TNT exploit handling code, since they did finally fix the bug in the CraftBukkit 1.1-RC1 release. New command: /f powerboost <p|f|player|faction> <name> <#> - apply permanent power bonus/penalty to specified player or faction. Requires factions.powerboost permission. New permission: factions.powerboost - allows use of the /f powerboost command; granted by default to factions.kit.mod permission kit and above I've added a FAQ to the first post here and the plugin description on BukkitDev which should hopefully reduce the number of commonly repeated questions at least a little bit. F.A.Q. Q. I don't want all players to have all permissions which are granted by default. How can I change that? A. See our permissions here, in our user guide. Factions grants the factions.kit.fullplayer permission kit by default. You will likely need to deny the individual permissions already granted which you don't want those players to have. Your permission plugin of choice should provide a method to deny permissions, such as adding a "-" to the start of the permission (like "-factions.create"). Most permission plugins at this time don't seem to allow denying parent->child / kit permissions (some don't even allow granting them), so you may need to handle them individually. Q. I modified the configuration file conf.json manually and the configuration reset to default? What happened? A. This is why we recommend people not edit the file manually. Something you changed corrupted the file, which caused Factions to revert back to default values since it could not read it. If you look at your server log from when your server started up after you edited the file, you'll see an error logged from when Factions tried to load the file. You should also see a backup copy of your invalid file made as "conf.json_bad" alongside the newly defaulted conf.json (if you don't you're using an old release of Factions and need to update). You should normally be using /f config to change any configuration, as outlined in our user guide. Q. Chat looks messed up, with odd letters and numbers added to it, and the chat isn't colored properly. Why is this happening? A. At the least, you'll need to modify the chatTagInsertIndex setting to fix that (i.e. /f config chatTagInsertIndex <value>, where <value> is 0/1/2/3/etc.), but better methods are outlined in our user guide's chat configuration coverage. Q. Does Factions have multiworld support? A. Various features of Factions can be disabled in specified worlds. See our user guide. That is currently the extent of our multiworld support. Q. How can I get my economy plugin of choice (iConomy, BOSEconomy, EssentialsEco, whatever) working with Factions? A. First, you will need to install the Vault plugin on your server to interface between Factions and your economy plugin of choice. Next, you'll need to make sure economy is enabled in Factions by running the command /f config econEnabled true. You can see more information about economy integration in our user guide. Q. As a server owner, administrator, and/or moderator, I want to be able to bypass all faction claim protections. Is this possible? A. Assuming you have the factions.bypass permission, you can enable and disable admin bypass mode using the command /f bypass. EDIT by Moderator: merged posts, please use the edit button instead of double posting.