The config file for Factions can be found here:
/plugins/Factions/conf.json
A default file will be generated the first time you run the plugin.

This is a JSON-file (not to be confused with YAML). Mix tabs and spaces in any way you like, JSON won’t care
If you get startup errors, validate your config here: http://www.jsonlint.com/

If you continue to have trouble when making any change to any of the configuration files, where your changes are lost on startup (or Factions ignores them), there are two possibilities.

1. Factions saves current settings and data to all files occasionally (overwriting them), including when the server shuts down. You should only edit the files when the server is completely shut down, or use these provided admin commands: use /f save and then /f lock on (save all current data to files, then temporarily lock them from being overwritten), then edit the file(s) as needed and save them, then use /f reload (alternately /f reload conf or similar to only reload a specific file) followed by /f lock off to reload the file(s) and disable the temporary lock.
2. You (or your text editor of choice) messed the file format up somehow. If that’s the case, Factions will give an error in the server log/console when it starts up and the file will be wiped and returned to defaults. The first thing you can try is to get a decent text editor, such as Notepad++.

However, if you’re wanting to change settings in conf.json and just can’t get it to work by manually editing the file like described above, there is now an easier way. The /f config [setting] [value] command (with permission node “factions.config”, or from server console) is available and will even fix any capitalization problems with what you type in. This command works for changing every setting in conf.json. It works immediately, and will save an updated conf.json in the process. For example, if you want to set “powerPlayerMax” in conf.json to 20, you can use the command f config powerplayermax 20. Simple, right?
Further information on changing different data types using this command:

• For boolean (true/false> values, you can specify true, false, on, off, yes, no, y, n. Example (set “homesEnabled” to true): /f config hOmesEnableD y
• For numeric values, some need to be whole numbers and others don’t. You’ll be notified if that’s an issue. Example (set “powerPlayerMax” to 20.5): /f config powerplayermax 20.5
• For text values, just enter the desired text. Note that if you have a space (” “) at the end, it will be trimmed off. Example (set “chatTagReplaceString” to “{FACTION TAG HERE}”): /f config chatTagReplaceString {FACTION TAG HERE}
• For lists of multiple values, the command will add the specified value if it doesn’t exist or remove it if it does. Example (add/remove “BUCKET” from “territoryDenyUseageMaterials”, depending on whether it’s already in there or not): /f config territoryDenyUseageMaterials bucket

War configuration

• “powerPlayerMax”: 10
  “powerPlayerMin”: -10
  Alter these values to change how much power a single player contributes to a faction. Per default the power of a player will be at max. On death a player will loose power, but the power can not fall below the min value.
• “powerPerDeath”: 2.0
  This decides how much power a player (and consequently it’s faction) will loose on death.
• “powerPerMinute”: 0.2
  All players regain this much power each minute. It can be seen as the “health rate”. With the default 0.2 it will take 5 min to regain one power.
• “territoryShieldFactor”: 0.5
  If a player is hurt by an enemy in it’s own territory the player will not take full damage. The damage will be reduced with this factor. Set it to 1.0 and it will be impossible to kill someone in their own territory.
• “territoryProtectedMaterials”: ["WOODEN_DOOR", "TRAP_DOOR", "DISPENSER", "CHEST", "FURNACE", "BURNING_FURNACE", "DIODE_BLOCK_OFF", "DIODE_BLOCK_ON"]
  These blocks can only be interacted with by the members of the faction that controls the territory where the block is standing, as long as any members of the faction are online. When no members are online, “territoryProtectedMaterialsWhenOffline” is used instead. Find a full list of material types here: https://github.com/Bukkit/Bukkit/blob/master/src/main/java/org/bukkit/Material.java
• “territoryDenyUseageMaterials”: ["FLINT_AND_STEEL", "BUCKET", "WATER_BUCKET", "LAVA_BUCKET"]
  These inventory items cannot be used inside faction territory by players not in that faction, as long as any members of the faction are online. When no members are online, “territoryDenyUseageMaterialsWhenOffline” is used instead. These use the same material type list linked to above.
  
• “autoLeaveAfterDaysOfInactivity”: 14.0
  This means that players that does not log in for two weeks will leave (be kicked) from their faction automatically. If the server admin may only be kicked if there are no other members and in that case the faction id deleted.
• “homesEnabled”: true
  “homesTeleportToOnDeath”: true
  Configure if faction homes can be set and used and if players will respawn there on death instead of at the global spawn point.

Note that with this default config you can fight down the power of an enemy faction to 0 if half of the faction members are online and you completely gank them all.

Multiworld support

Factions can have some features disabled in specific worlds using these conf.json settings:

• “worldsNoClaiming”: [], – prevents factions from claiming land in these worlds
• “worldsNoPowerLoss”: [], – prevents power loss on death in these worlds
• “worldsIgnorePvP”: [], – Factions will completely ignore PvP damage in these worlds
• “worldsNoWildernessProtection”: [] – any wilderness protection options you have set will be ignored in these worlds

Note that adding/removing worlds from these is best done using the /f config [setting] [value] command.
Example: /f config worldsNoClaiming your_creative_world

 

Chat configuration

Our goal is that Factions should work well together with other plugins that alter the chat format. Factions will therefore try to modify (as opposed to overwrite) the chat format after the other plugins have altered it. Per default the writing players faction tag will be injected one char from the beginning of the chat format. Per default that faction tag will be also be colored to visualize the relation to the listener.

Examples
We have two players online. One is called “Foo” and the other player is called “Bar”. Foo is an admin and her name is colored red by some other plugin. Foo is a regular player. Without factions installed a conversation could look like this:
<Foo> Nice to see you online Bar
<Bar> Thx! Hi (:

Now we install factions. Foo creates a faction for ninjas with tag NIN. After that the same conversation would look like this from Foo’s perspective:
<**NIN Foo> Nice to see you online Bar
<Bar> Thx! Hi (:
And like this from Bar’s perspective:
<**NIN Foo> Nice to see you online Bar
<Bar> Thx! Hi (:

The two stars, **, is the default prefix for a faction admin. And the tag was green for Foo as she has the relation “member” to herself. White is the default color for relation “neutral”. So the reason we injected the tag on char from the beginning is to get after the “<” char.

If you’re looking to use another chat plugin and want to be sure it has full compatibility with Factions, there are two which have additional integration work done to make sure they work perfectly together. The first is EssentialsChat, a part of the Essentials plugin, for which it’s recommended you add “[FACTION]” to the chat configuration in Essentials config.yml. The second is ChannelChat, which even has an additional “faction” channel added by the author.

Now to the config options:

• “chatTagEnabled”: true
  Should we insert faction chat tags at all? You should not decide to turn this of as it is an awesome feature If you experience conflicts with some other plugin you should test to set this next config option to false instead:
• “chatTagRelationColored”: true
  Per default we color the chat tag to visualize relation. Foo saw her faction tag in green color because this option was set to true. HOWEVER you may want to try to turn this feature of in the rare case that you experience conflicts with other plugins.
• “chatTagInsertIndex”: 1
  Fallback insertion method. How many characters in from the beginning should we inject the faction tag?
• “chatTagReplaceString”: “[FACTION]“
  Replacement style insertion method. If that string exists in the chat message, the faction tag will replace it.
• “chatTagInsertBeforeString”: “”
  If set and the specified string exists in the chat message, the faction tag will be inserted before it.
• “chatTagInsertAfterString”: “”
  If set and the specified string exists in the chat message, the faction tag will be inserted after it. As an example, “<” might be a good choice.
• “chatTagFormat”: “%s§f “
  The %s will be replaced with the tag. The §f means white and then there is a space.
• “factionChatFormat”: “§a%s§f %s”
  This is the format for the faction chat command. This will not inject into the format and stuff. It is only used for the faction chat command which sends chat messages that only your fellow faction members can see.
• “prefixAdmin”: “**”
  “prefixMod”: “*”
  The prefixes for faction admins and moderators.

The tag placement settings for chat messages in conf.json work as follows:

1. First, Factions will check for “chatTagReplaceString” (will default to “[FACTION]“). If that string exists in the chat message, it will be replaced. You could therefore stick that string in your chat plugin’s prefix or suffix or whatever. Note that if local or channel chat is enabled in another plugin, Factions might never get a chance to replace it (depending on how the other chat plugin implements it; see below). If you use EssentialsChat, this is the recommended method. Simply include “[FACTION]” in the EssentialsChat format string in Essentials’ config.yml.
2. If that string doesn’t exist in the message or the setting is empty (thus disabled), Factions will then check the “chatTagInsertBeforeString” setting (defaults to nothing “”, thus disabled). You could set that to a certain character such as “<”, “>”, “[", "]“, or whatever. The tag will then be inserted before the first instance if that string if it exists in the message.
3. If that string doesn’t exist in the message or the setting is empty (thus disabled), Factions will then check the “chatTagInsertAfterString” setting (defaults to nothing “”, thus disabled). This works much the same as the above, except it will insert after the first instance of that string.
4. Only if all of the above are disabled or don’t find matches will it finally resort to the “chatTagInsertIndex” setting, which indicates how many characters into the chat message to insert it. Note that color tags consist of 2 characters, and are considered in this placement. If you see strange characters and stray letters or numbers, you need to adjust this value or alternately use one of the above placement settings instead.
5. The settings “chatTagPadBefore” and “chatTagPadAfter” will add an extra space (“ ”) before or after the faction tag when inserting it.

A reminder, any plugins that limit the number of chat recipients (like local chat, or channel chat) will likely keep the chat message from reaching Factions at all, since those implementations usually cancel the chat event and send out individual messages which can’t be intercepted. Thus, no faction tags in those messages. Only global chat messages will get faction tags. There’s nothing I can do about that. The author of the other chat plugin can however do something about it; all it should require is to change how the messages are sent to only specific people. Instead of the current norm of cancelling the chat event and using player.sendMessage() to send out individual messages, they should instead be getting event.getRecipients() and simply removing specific players from that list as needed. If that is done, the chat messages will be available for other plugins (like Factions) to work with.

 

Economy configuration

As with all other settings, a reminder, you should probably change these using /f config rather than manually editing conf.json. For example, /f config econEnabled true or /f config econCostClaimWilderness 100.

•   “econEnabled”: false, – Whether economy integration is enabled it all.
•   “econUniverseAccount”: “”, – If you have a universe account set up which all transactions should be taken from or added to, you can set the name of it here.
•   “econCostClaimWilderness”: 30.0, – The basic cost for claiming land.
•   “econCostClaimFromFactionBonus”: 30.0, – How much the cost of claiming land is reduced if it is being taken from another faction, as an incentive. A negative number can be specified to make claiming rival faction land cost more instead, or 0 can be specified to disable this bonus.
•   “econClaimAdditionalMultiplier”: 0.5, – If set higher than 0.0, each additional land claimed by a faction will cost more than the last. Example: with base cost of 30 and miltiplier of 0.5, the 2nd claim will cost 45, the third will cost 60, and so forth.
•   “econClaimRefundMultiplier”: 0.7, – If set higher than 0.0, a refund of part of the cost of the land will be given when land is unclaimed. 1.0 would be a 100% refund, 0.7 is a 70% refund. If set to a negative number, it will actually cost that much money to unclaim land rather than refunding it.
•   “econClaimUnconnectedFee”: 0.0, – Additional cost for claiming land which is not connected to existing claims. This additional cost is only added if the faction has at least 1 existing claim somewhere in the current world, and is added to the cost after all other calculations are done. This fee is not refunded from unclaiming land or even considered in actual land values.
•   “econCostCreate”: 100.0, – The cost to use /f create.
•   “econCostOwner”: 15.0, – The cost to use /f owner.
•   “econCostSethome”: 30.0, – The cost to use /f sethome.
•   “econCostJoin”: 0.0, – …etc…
•   “econCostLeave”: 0.0, – …etc…
•   “econCostKick”: 0.0, – …etc…
•   “econCostInvite”: 0.0, – …etc…
•   “econCostHome”: 0.0, – …etc…
•   “econCostTag”: 0.0, – …etc…
•   “econCostDesc”: 0.0, – …etc…
•   “econCostTitle”: 0.0, – …etc…
•   “econCostList”: 0.0, – …etc…
•   “econCostMap”: 0.0, – …etc…
•   “econCostPower”: 0.0, – …etc…
•   “econCostShow”: 0.0, – …etc…
•   “econCostOpen”: 0.0, – …etc…
•   “econCostAlly”: 0.0, – …etc…
•   “econCostEnemy”: 0.0, – …etc…
•   “econCostNeutral”: 0.0, – …etc…
•   “econCostNoBoom”: 0.0, – …etc…
•   “bankEnabled”: true, – Whether faction banks are enabled, which will be normally used to pay for most costs. Enables the /f money commands.
•   “bankMembersCanWithdraw”: false, – Players have to be moderator or admin to withdraw or pay money to another faction, unless this is set to true.
•   “bankFactionPaysCosts”: true, – If true, payments for faction command costs are charged to faction bank.
•   “bankFactionPaysLandCosts”: true, – If true, payments for land claims are charged to faction bank.

 

Other configuration

All colors can be configured, etc. Some further info on various settings is below. These are mostly in no particular order, as they are taken directly from changelog notes; apologies in advance for the messiness.

• “newFactionsDefaultOpen”: true, – whether newly created factions default to open membership (where anyone can join without invitation)
• “showMapFactionKey”: true, – whether to show the faction key (with names) on the map
• “showNeutralFactionsOnMap”: true, – if disabled, will hide neutral factions on the faction map (unless player is standing inside the faction’s territory)
• “showEnemyFactionsOnMap”: true, – same as above, but for enemy factions
• “CanLeaveWithNegativePower”: true, – whether players can leave, join, or be kicked from a faction while they have a negative power level
• “homesTeleportAllowedEnemyDistance”: 32.0, – if enemies are within this distance and you’re not in a safezone or your own faction’s territory, /f home will not work (set to 0 to disable)

• “territoryEnemyDenyBuild”: true, – whether players are prevented from building/destroying blocks in the territory of enemy factions, while any members of that faction are online
• “territoryEnemyDenyBuildWhenOffline”: true, – whether players are prevented from building/destroying blocks in the territory of enemy factions, while all members of that faction are offline
• “territoryEnemyDenyUseage”: true, – whether players are prevented from using certain inventory items (by default buckets and flint&steel) while in the territory of enemy factions
• “territoryEnemyProtectMaterials”: true, – whether players are prevented from interacting with certain block types (by default doors and chests and such) while in the territory of enemy factions

• “warZoneBlockCreepers”: false, – block creeper explosions in warzones?
• “warZoneBlockFireballs”: false, – block ghast fireball explosions in warzones?
• “warZoneBlockTNT”: true, – block TNT explosions in warzones?
• “warZoneDenyBuild”: true, – keep regular users from building/destroying blocks in warzones?
• “warZoneDenyUseage”: true, – keep regular users from using items in the territoryDenyUseageMaterials list (normally all buckets and flint&steel) in warzones?
• “warZonePowerLoss”: true, – should players who die in a warzone lose power? note that this ALWAYS overrides worlds in “worldsNoPowerLoss”
• “warZoneFriendlyFire”: false, – whether PvP between fellow faction members and between allies is enabled in War Zones

• “disablePVPForFactionlessPlayers”: false, – whether PvP damage will be disabled to/from players who are not in a faction
• “homesMustBeInClaimedTerritory”: true, – whether to require faction homes to be set only inside the faction’s own territory
• “homesTeleportAllowedFromEnemyTerritory”: true, – whether to allow teleporting to the faction home if the player is in enemy territory
• “claimsMustBeConnected”: false, – whether to require all faction claims beyond the first to be connected to each other
• “considerFactionsReallyOfflineAfterXMinutes”: 0.0, – makes all “Offline” options still consider the faction as having members online until X minutes after the last one logs off

• “noPVPDamageToOthersForXSecondsAfterLogin”: 3, – prevents players from being able to do PvP damage for the specified number of seconds after logging in (set to 0 to disable)

• “homesRespawnFromNoPowerLossWorlds”: true, – whether or not players should respawn to faction homes when they die in “worldsNoPowerLoss” worlds
• “homesTeleportCommandEnabled”: true, – can be used to disable the /f home command, while possibly leaving faction homes enabled for the
• “homesTeleportToOnDeath” functionality
• “homesTeleportAllowedFromDifferentWorld”: true, – whether or not players are allowed to use /f home when their faction home is in a different world from them

• “pistonProtectionThroughDenyBuild”: true, – can be disabled to turn off piston protection. This option is available due to the (untested) potential that a world with many pistons constantly repeatedly firing could result in additional lag from these piston protection events.
• “claimsCanBeUnconnectedIfOwnedByOtherFaction”: true, – will allow claims to bypass the “claimsMustBeConnected” option if the attempted claim is vulnerable land controlled by another faction.
• “homesTeleportIgnoreEnemiesIfInOwnTerritory”: true, – if disabled, players will no longer be able to teleport to their faction home while close to an enemy even if they are in their own territory.

• “powerFactionMax”: 0.0, – Maximum power limit for all factions. If set to anything above 0, factions will have their power capped at this amount.
• “claimsRequireMinFactionMembers”: 1, – Can be increased to prevent small (potentially one player) factions from claiming land until they have more members

• “ownedAreasEnabled”: true, – Whether in-faction individual ownership of claimed areas is enabled.
• “ownedAreasLimitPerFaction”: 0, – If set above 0, will limit the number of owned areas a faction can have set
• “ownedAreasModeratorsCanSet”: true, – Whether faction moderators are allowed to set ownership.
• “ownedAreaModeratorsBypass”: true, – Whether faction moderators can bypass the protections provided by ownership.
• “ownedAreaDenyBuild”: true, – If enabled, owned areas cannot be built/destroyed by normal faction members.
• “ownedAreaProtectMaterials”: true, – If enabled, owned areas disallow interaction with protected materials (doors, chests, etc.) by normal faction members.
• “ownedAreaDenyUseage”: true, – If enabled, owned areas deny usage of certain inventory items (flint&steel, buckets) by normal faction members.
• “safeZonePreventAllDamageToPlayers”: false, – If enabled, will prevent all damage to players while they’re in a Safe Zone; note that attack damage from other players and monsters is still prevented regardless.
• “disablePVPBetweenNeutralFactions”: false, – If enabled, will prevent all PvP damage between neutral factions.

• “econIConomyEnabled”: false, – if enabled, Factions will try to use iConomy to charge (or give) money for certain commands as outlined in the settings below
• “econCostClaimWilderness”: 30.0, – the base amount of money which will be charged to claim territory which is wilderness (only used if iConomy is available and enabled in the option above)
• “econCostClaimFromFactionBonus”: 30.0, – how much the cost of claiming land is reduced if it is being taken from another faction; can be set to a negative number to make such claims cost more instead of less
• “econClaimAdditionalMultiplier”: 0.5, – if set higher than 0.0, each additional land claimed by a faction will cost more than the last. Example: with base cost of 30 and miltiplier of 0.5, the 2nd claim will cost 45, the third will cost 60, and so forth.
• “econClaimRefundMultiplier”: 0.7, – if set higher than 0.0, a refund of part of the cost of the land will be given when land is unclaimed. 1.0 would be a 100% refund, 0.7 is a 70% refund. If set to a negative number, it will actually cost that much money to unclaim land rather than refunding it.
• “econCostCreate”: 100.0, – the cost to use /f create
• “econCostOwner”: 15.0, – the cost to use /f owner
• “econCostSethome”: 30.0, – the cost to use /f sethome
• “econCostJoin”: 0.0, – the cost to use /f join
• “econCostLeave”: 0.0, – …
• “econCostKick”: 0.0, – …
• The other “econCost<Command>” settings work the same.

• “worldsIgnorePvP”: [], – PvP damage will not be prevented by Factions for any worlds in this list (should probably use /f config worldsIgnorePvP [world name] to add/remove worlds instead of manually editing)
• “peacefulTerritoryDisablePVP”: true, – prevents PvP damage for anyone inside a peaceful faction’s territory.
• “peacefulTerritoryDisableMonsters”: false, – provides protection against monsters spawning or attacking inside a peaceful faction’s territory.
• “peacefulMembersDisablePowerLoss”: true, – keeps members of peaceful factions from suffering power loss when they die.
• “actionDeniedPainAmount”: 1, – how much damage is done to players by the PainBuild settings below. A value of 1 is equivalent to 1/2 of a heart.
• “territoryPainBuild”: false, – will cause pain to people trying to build/destroy in a neutral/ally faction’s territory while at least one of that faction’s members is online.
• “territoryPainBuildWhenOffline”: false, – same as above, but for when all of the faction’s members are offline.
• “territoryEnemyPainBuild”: false, – as above, but in enemy territory with at least one of them online.
• “territoryEnemyPainBuildWhenOffline”: false, – in enemy territory, all members offline.
• “ownedAreaPainBuild”: false, – as above, but in your own faction’s territory in an owned chunk that you don’t have access to.
• “territoryNeutralDenyCommands”: [], – list of commands which are blocked while a player is in the territory of a neutral faction
• “territoryEnemyDenyCommands”: ["home", "sethome", "spawn"], – list of commands which are blocked while a player is in the territory of an enemy faction

• “enablePVPAgainstFactionlessInAttackersLand”: false, – if enabled, allows PVP vs. factionless in attacker’s faction territory
• “territoryAllyDenyBuild”: true, – if disabled, players will be able to build/destroy in ally faction territory while at least one member of that faction is online
• “territoryAllyDenyBuildWhenOffline”: true, – if disabled, players will be able to build/destroy in ally faction territory when no members of that faction are online
• “territoryAllyPainBuild”: false, – if enabled, players will be hurt when trying to build/destroy in ally faction territory while at least one member of that faction is online
• “territoryAllyPainBuildWhenOffline”: false, – if enabled, players will be hurt when trying to build/destroy in ally faction territory when no members of that faction are online
• “territoryAllyDenyUseage”: true, – if disabled, players will be able to use buckets, flint&steel, etc. in ally faction territory
• “territoryAllyProtectMaterials”: true, – if disabled, players will be able to interact with doors, chests, etc. in ally faction territory
• “ownedLandMessage”: “Owner(s): “, – lead-in text shown when entering one of your faction’s claimed areas which is owned
• “publicLandMessage”: “Public faction land.”, – text shown when leaving an owned area in your faction’s territory
• “ownedMessageOnBorder”: true, – whether to indicate ownership when entering your faction’s territory from outside
• “ownedMessageInsideTerritory”: true, – whether to indicate ownership when moving around inside your faction’s territory
• “ownedMessageByChunk”: false, – whether to indicate ownership while moving between claimed chunks even when the owner list is the same
• “spoutFactionTagsOverNames”: true, – whether to show relation-colored faction tags over players’ names, over their heads (Spout plugin and Spout client both required)
• “spoutFactionTitlesOverNames”: true, – whether to show players’ faction titles over their names, over their heads (Spout plugin and Spout client both required)
• “spoutFactionAdminCapes”: true, – whether to show relation-colored capes on faction admins (Spout plugin and Spout client both required)
• “spoutFactionModeratorCapes”: true, – whether to show relation-colored capes on faction moderators (Spout plugin and Spout client both required)
• “capeAlly”: “https://github.com/MassiveCraft/Factions/raw/master/capes/ally.png”, – URL for cape texture used for allied faction leaders
• “capeEnemy”: “https://github.com/MassiveCraft/Factions/raw/master/capes/enemy.png”, – ^ same, but for enemy faction leaders
• “capeMember”: “https://github.com/MassiveCraft/Factions/raw/master/capes/member.png”, – ^ guess
• “capeNeutral”: “https://github.com/MassiveCraft/Factions/raw/master/capes/neutral.png”, – ^ guess
• “capePeaceful”: “https://github.com/MassiveCraft/Factions/raw/master/capes/peaceful.png”, – ^ guess
• “worldsNoWildernessProtection”: [], – Wilderness protection options will not be applied to any worlds in this list (should probably use /f config worldsNoWildernessProtection [world name] to add/remove worlds instead of manually editing)

• “newPlayerStartingFactionID”: 0, – can be changed to have new players start out in a specific faction
• “factionOnlyChat”: true, – can be set to false to disable faction chat
• “worldGuardChecking”: false, – can be set to true to prevent factions from claiming chunks that are part of WorldGuard regions

• “powerOfflineLossPerDay”: 1.0, – players will lose this much power per day offline
• “powerOfflineLossLimit”: 0.0, – players will no longer lose power from being offline once their power drops to this amount or less
• “territoryDenyEndermanBlocks”: true, – if enabled, endermen will be unable to place/remove blocks in faction-claimed territory
• “safeZoneDenyEndermanBlocks”: true, – as above, but for Safe Zones
• “warZoneDenyEndermanBlocks”: true, – as above, but for War Zones
• “wildernessDenyEndermanBlocks”: false, – as above, but for unclaimed wilderness areas

• "baseCommandAliases": [
"f"
], – list of command aliases for Factions; normally just “f” (thus /f)
• "allianceChatFormat": "§d%s:§f %s", – format to display ally chat messages in, much like factionChatFormat
• "homesTeleportCommandSmokeEffectEnabled": true, – show smoke effect when player teleports to faction home
• "homesTeleportCommandSmokeEffectThickness": 3.0, – thickness of smoke effect
• "territoryDenyEndermanBlocksWhenOffline": true, – prevent endermen from removing or placing blocks in the territory of a faction which has no members online
• "spoutTerritoryDisplayPosition": 3, – set the screen position at which the current territory is shown. 0 = disabled, 1 = top left, 2 = top center, 3 (default) = top right
• "spoutTerritoryDisplaySize": 1.0, – font scale (size) for the territory and owner displays at the top of the screen
• "spoutTerritoryDisplayShowDescription": true, – whether to show the faction description in the territory display, instead of just the faction tag
• "spoutTerritoryOwnersShow": true, – whether to show the owner list under the territory display, instead of outputting it to chat
• "spoutTerritoryNoticeShow": true, – whether to show the territory change notice
• "spoutTerritoryNoticeTop": 40, – vertical offset for territory change notice; 0 = top of screen, 240 = below the bottom of screen
• "spoutTerritoryNoticeShowDescription": false, – whether to show the faction description in the territory change notice, instead of just the faction tag
• "spoutTerritoryNoticeSize": 1.5, – font scale (size) for the territory notice
• "spoutTerritoryNoticeLeaveAfterSeconds": 2.0, – how many seconds to show the territory change notice before it goes away
• "econEnabled": false, – if set to true and Register plugin is available, economy integration will be enabled
• "econUniverseAccount": "", – when money is paid or gained by a player, that money amount will be conversely removed from or added to this account
• "bankEnabled": true, – enable faction banks
• "bankMembersCanWithdraw": false, – have to be at least moderator to withdraw or pay money to another faction, unless this is set to true
• "bankFactionPaysCosts": true, – if true, payments for faction command costs are charged to faction bank
• "bankFactionPaysLandCosts": true, – if true, payments for land claims are charged to faction bank

• "colorPeaceful": GOLD, – the color used to denote peaceful factions and safe zones
• "colorWar": DARK_RED, – the color used to denote war zones
• "logFactionCreate": true, – log faction creation
• "logFactionDisband": true, – log factions being disbanded, by command or by circumstance (no players left in faction, etc.)
• "logFactionJoin": true, – log player joining a faction
• "logFactionKick": true, – log player being kicked from a faction
• "logFactionLeave": true, – log player leaving a faction
• "logLandClaims": true, – log land being claimed (including safe zone and war zone)
• "logLandUnclaims": true, – log land being unclaimed (including safe zone and war zone)
• "logMoneyTransactions": true, – log money being deposited, withdrawn, and otherwise transferred in relation to faction banks

• "removePlayerDataWhenBanned": true, – can be changed to false to prevent Factions from deleting player data for players when they are banned from the server
• "powerPlayerStarting": 0.0, – power level which new players will start at

• "lwcIntegration": false, set to true to enable LWC integration 
• "onUnclaimResetLwcLocks": false, determines if unclaiming land resets LWC locks 
• "onCaptureResetLwcLocks": false, determines if capturing land resets LWC locks 
• "permanentFactionsDisableLeaderPromotion": false, if enabled, promotion routine is skipped for permanent factions so that they can exist without a faction admin 
• "permanentFactionMemberDenyCommands": [], list of commands which members of permanent factions are prevented from using 
• "econClaimUnconnectedFee": 0.0, additional cost for claiming land which is not connected to existing claims