Factions

Fun Login to Add Favorites
  • 1 Like
  • Minecraft
  • 21,712 Monthly Downloads
  • Supports: CB 1.2.5-R1.2
  • 230,492 Total Downloads
  • Updated 5/16/2012 11:28:45 PM
  • Created 8/25/2011 8:29:25 PM
  • 15 Favorites
  • Project Site
  • Release Type: Mature
  • License: GNU Lesser General Public License version 3 (LGPLv3)
  • Newest File: 1.6.8
or

About Factions

The Factions Logotype Read our user guide here.

To discuss this plugin, please use the thread on the main Bukkit forum for now.


F.A.Q.

Q. I don't want all players to have the permissions which are currently 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 either reset to default or it ignored and overwrote my changes. What happened?
A. This is why we recommend people not edit the file manually. You should normally be using /f config to change any configuration, as outlined in our user guide. If it simply ignored your changes, you probably edited the file while the server was running which doesn't work. If the configuration reset, 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).

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.

NOTE: For existing users, a couple things you should make sure of:
1. If you haven't done so already on your existing Factions 1.6.x setup (does not apply for 1.7.x), you should deny usage of fireballs:
/f config territoryDenyUseageMaterials fireball
/f config territoryDenyUseageMaterialsWhenOffline fireball
2. If you're using Spout, they now have a minimap where we used to default to show the territory faction display. You can switch our territory display to the upper left as a workaround:
/f config spoutTerritoryDisplayPosition 1


  • Added fireball/"fire charge" to default territoryDenyUseageMaterials list, to prevent them from being used to set things on fire like flint&steel.
  • Optional prevention of Ender pearl exploit, which could be used to clip through doors, glass, and probably a few other things if just the right spot was targeted. New setting "handleExploitEnderPearlClipping" (enabled by default) to determine whether it's prevented or not.
  • Optional prevention of obsidian generator exploit, which converts redstone wire to obsidian. New setting "handleExploitObsidianGenerators" (enabled by default) to determine whether it's prevented or not. Some servers might want to disable this prevention, to keep it as a viable obsidian creation method. Thanks to ObGenBlocker and WorldGuard plugins for the prevention method.
  • New setting "handleExploitInteractionSpam" (defaults to true). If enabled, players will begin to take injury if they rapidly try interacting with anything in another faction's territory. This is to prevent people from spam-clicking on doors and chests and such in the hopes that they'll get one through. After 10 rapid interaction attempts in a row, every click will cause them damage; the damage amount is a half heart of damage for every 10 clicks (up to 1 heart at 20 clicks, 1.5 hearts at 30, etc.). After the player has stopped trying for 2 seconds, their failed interaction counter will reset.
  • New setting "handleExploitTNTWaterlog" (default false/disabled) which, if enabled, will cause TNT which explodes in liquid to actually destroy a single adjacent block in all 6 directions. This will only apply to blocks which can be destroyed by TNT normally, specifically anything other than air, bedrock, water, lava, obsidian, and enchanting tables. The destruction of these blocks will be handled as if they had been mined, dropping the appropriate item. TNT in water/lava doesn't normally destroy any surrounding blocks, which is usually desired behavior. That's the reason this setting is disabled by default. However, it is available because it provides a method to get through waterwalls with enough persistence, and it makes cheap (non-obsidian) TNT cannons require minor maintenance between shots.
  • /f show|who command will no longer reveal players as online if they are hidden from the viewer by the Vanish API.
  • Double-space (or more) after command alias is no longer accepted, i.e. "f home". Otherwise, command prevention routines (in Factions itself and in other plugins) can be bypassed. For example, preventing the "f home" command wouldn't prevent anyone from using "f home" or "f home" instead.
  • Fix for /f power command used on self incorrectly also requiring factions.power.any permission.
  • Fix for rare case where faction home location's world being removed or renamed (world with specified name not existing) could lead to NPE.
  • Removed our TNT exploit prevention code, and removed our workaround fix code for the bug where half-step placement wasn't detected, since the Bukkit team did finally fix those issues.

New conf.json settings:
"handleExploitEnderPearlClipping": true, enables exploit prevention for ender pearls which otherwise can allow clipping through doors, glass, and other objects
"handleExploitObsidianGenerators": true, enables exploit prevention of obsidian generators which convert redstone wire to obsidian
"handleExploitInteractionSpam": true, enables exploit prevention of people trying to rapidly interact with doors to glitch through, by progressively injuring them after several attempts
"handleExploitTNTWaterlog": false, will cause TNT explosions in liquid to destroy the 6 adjacent blocks if those blocks would normally be destroyed by explosions

Learn how to disable ads
Learn how to disable ads
Login to Curse

Don't have an account? Create One.

Get an epic experience with Curse Premium
  • Faster addon downloads
  • Premium-Only Beta Giveaways
  • Ad-Free Curse experience
  • Premium Curse Client
  • and many More Features
  • Learn More »

Diablo III Giveaway

Enter Now!