F.A.Q. (Frequently Asked Questions)
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 denying factions.kit.fullplayer permission probably won't work and you'll need to handle the individual permissions instead.
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 for versions lower than 1.7.5, 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. If you're using 1.7.5 or higher, you should instead read this regarding chat configuration.
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.
Q. I'm upgrading from a 1.6.x version to 1.8.x. Is there anything I should know?
A. Yes, many things have changed. The most important things to note of are as follows:
- Permissions are no longer automatically granted, so regular players might no longer be able to use any commands. For the same standard user privileges, you can grant the factions.kit.fullplayer permission kit to your regular users.
- Chat integration has changed completely. See here for some notes on how it now works.
- The SafeZone, WarZone, and other territory options which are no longer present in conf.json are largely now available to all factions using flags (/f flag) and perms (/f perm). Get familiar with those two commands, they are powerful.
- Allies now have the ability to do various things in allied territory, which they didn't used to be able to. The new Truce relation is more in line with how Allies used to work. If you want Allies to not have this new access, you might want to change individual faction perms using /f perm (ex. /f perm SomeFaction build ally false) or change the defaults for all factions in the config (ex. /f config factionPermDefaults build ally to toggle). Besides "build" perm, allies also now default to having "door", "lever", and "button" perms as well.
- New faction members now start out at the Recruit level, which gives very limited access to prevent griefing. They will need to be promoted to full Member status (/f promote, also note there is /f demote) in order to have full access within the faction.
- The owner system (/f owner) which worked only on people in the faction was replaced by the more powerful access system (/f access) which can apply to people from other factions, and even apply to entire other factions.
NOTE: keep in mind there is still almost no documentation yet for the many changes included beyond the 1.6.x branch, beyond those in the change logs for this and previous 1.7.x+ alpha and beta releases in our file list. A few features from the 1.6 branch have been removed and may not be returning. You additionally will not be able to safely downgrade from a 1.7/1.8 release back to a 1.6 release as the data structure has changed. Based on these reasons, updating from an existing 1.6.x release should probably be tested out before updating a public server.
IMPORTANT NOTE: Existing plugin users who are updating to this version from an older 1.8.x or 1.7.x release will likely need to grant default permissions for recruits, like so:
/f config factionPermDefaults door recruit
/f config factionPermDefaults button recruit
/f config factionPermDefaults lever recruit
/f config factionPermDefaults build recruit
Updates made to both branches:
- Money transfers and deposits which failed (possible with some economy plugins) would simply lose the money; now the initiator is refunded and notified of the failure. (by jastice)
- Update to our obsidian generator exploit prevention code (via config option "handleExploitObsidianGenerators") to address newer method involving tripwire strings instead of redstone.
- New permission factions.claim.radius (granted to all players by default), which is now required in order to specify a radius with the claim command.
- Additional Exception catching for some further errors which can occur when loading JSON files.
- New setting "saveToFileEveryXMinutes" (default 30.0) to configure how often (in minutes) all data is automatically saved to disk. Setting it to 0 or lower will disable automatic data saving so that it only saves when shutting down (not recommended).
- Additional safety check to make sure data saving can't run multiple iterations simultaneously; this might have been the cause of some reports of corrupted data.
- AutoLeaveTask is now throttled to only spend a certain amount of time per server tick on removing inactive players, to prevent it from potentially choking very large servers. This amount of time can be specified by the new setting "autoLeaveRoutineMaxMillisecondsPerTick" (default 5ms, 10% of a server tick).
Updates specific to the 1.8 branch:
- We now use the standard Bukkit command handling system. Doing so removes the possiblility for dynamic command alias assignment and the ability to use slashless commands, but makes factions compatible with all other plugins doing stuff like blocking commands from being used (AntiGuest, NoCheatPlus, War etc) and plugins that log command useage (Hawkeye etc). (Olof)
- Added recruit role for factions. The recruit role's goal is to enable factions to invite new members without being afraid of getting griefed instantly. Added configuration option "factionRankDefault" for default rank of newly joined faction members (default RECRUIT, but it can be set to any supported rank). Added /f promote and /f demote commands (require factions.promote and factions.demote permissions respectively, granted by default), which leaders and officers can use to increase or decrease the rank of a faction member by one level, up to officer, or down to recruit. (by jastice)
- Faction members can now be rewarded with money (through economy) every day for every territory plot they control divided among all the players in the faction. New config options "econLandRewardTaskRunsEveryXMinutes" (default 20.0) to determine how often rewards are given, and "econLandReward" (default 0.0, disabled) to determine how much money per territory plot is rewarded each time. (by AEtherSurfer)
- Explosion protection can now be granted to factions which have all members offline. New config options "protectOfflineFactionsFromExplosions" (default false) which can be enabled to provide this protection, and "offlineExplosionProtectionDelay" (default 2.0) which determines how many minutes need to pass after the last member goes offline before the explosion protection kicks in. (mostly by squidicuzz)
- Added trapped chest, hopper, and dropper to recognized container list.
New conf.json settings:
"saveToFileEveryXMinutes": 30.0, how often all data is automatically saved to disk; setting to 0 disables
"autoLeaveRoutineMaxMillisecondsPerTick": 5, the number of milliseconds per server tick to throttle the task which removes inactive players
"factionRankDefault": "RECRUIT", the initial rank of newly joined faction members
"econLandRewardTaskRunsEveryXMinutes": 20.0, how often money (through economy) is rewarded to players for the amount of territory controlled by their faction
"econLandReward": 0.0, how much money per territory plot is rewarded each time; setting to 0 disables
"protectOfflineFactionsFromExplosions": false, can be enabled to provide explosion protection to the territory of factions which have all members offline
"offlineExplosionProtectionDelay": 2.0, how many minutes need to pass after the last member goes offline before offline explosion protection kicks in
|File Name||Release Type||Game Version||Downloads||Date|
|1.7.9 beta||Beta||CB 1.4.5-R0.2||1,220||11/30/2012|
|1.7.8 beta||Beta||CB 1.4.2-R0.2||904||11/08/2012|
|1.7.7 beta||Beta||CB 1.3.2-R1.0||3,038||09/05/2012|
|1.7.6 beta||Beta||CB 1.3.1-R2.0||2,108||08/09/2012|
|1.7.5 beta||Beta||CB 1.2.5-R4.0||10,705||05/16/2012|
|1.6.7 release||Release||CB 1.2.5-R1.0||114,242||03/14/2012|
|1.6.6b release||Release||CB 1.1-R7||22,463||03/01/2012|
|1.6.5c (ZIP)||Release||CB 1.1-R3||32,033||02/04/2012|
|1.6.5c (JAR only)||Release||CB 1.1-R3||1,207||02/04/2012|
|1.6.5b (ZIP)||Release||CB 1.1-R3||7,390||02/03/2012|
|1.6.5b (JAR only)||Release||CB 1.1-R3||279||02/03/2012|
|1.6.5 (ZIP)||Release||CB 1.1-R3||1,305||02/02/2012|
|1.6.5 (JAR only)||Release||CB 1.1-R3||217||02/02/2012|
|1.6.4 (ZIP)||Release||CB 1.1-R3||8,629||01/29/2012|
|1.6.4 (JAR only)||Release||CB 1.1-R3||425||01/29/2012|
|1.6.3 (ZIP)||Release||CB 1.1-R1||17,713||01/19/2012|
|1.6.3 (JAR only)||Release||CB 1.1-R1||684||01/19/2012|
|1.6.2 (ZIP)||Release||CB 1.0.1-R1||29,673||12/18/2011|
|1.6.2 (JAR only)||Release||CB 1.0.1-R1||625||12/18/2011|
|1.6.1 (ZIP)||Release||CB 1337||16,685||10/27/2011|
|1.6.1 (JAR only)||Release||CB 1337||637||10/27/2011|
|1.6.0 (ZIP)||Release||CB 1337||700||10/25/2011|
|1.6.0 (JAR only)||Release||CB 1337||308||10/25/2011|
|1.5.9 BETA (ZIP)||Beta||CB 1317||1,517||10/16/2011|
|1.5.1 (ZIP)||Release||CB 1185||3,290||09/22/2011|
|1.5.1 (JAR only)||Release||CB 1185||1,274||09/22/2011|
|1.5.0 (ZIP)||Release||CB 1185||233||09/22/2011|
|1.4.9 (ZIP)||Release||CB 1060||893||09/15/2011|
|1.4.8 (ZIP)||Release||CB 1060||85||09/15/2011|
|1.4.7 (ZIP)||Release||CB 1060||1,205||08/25/2011|
- Admin Tools, Anti-Griefing Tools, Informational, Teleportation, and World Editing and Management
- 193,002 Monthly Downloads
- Admin Tools, Chat Related, Teleportation, Economy, and General
- 153,994 Monthly Downloads
- Admin Tools, World Editing and Management, Fixes, General, and Anti-Griefing Tools
- 85,315 Monthly Downloads
- World Editing and Management and Admin Tools
- 75,172 Monthly Downloads
- Admin Tools, Developer Tools, Mechanics, and Economy
- 62,844 Monthly Downloads