Factions

The Factions Logotype ~ Read our user guide here ~
~ Source available on GitHub ~ (open source, pull requests accepted)
~ View the Changelog ~

Further discussion is also available on the main Bukkit forum.

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.

You must login to post a comment. Don't have an account? Register to get one!

4388 comments
1
2
3
100
200
300
400
437
438
439
Next →

- Reply
- #4509
MarkehMe May 19, 2013 at 07:42 UTC - 0 likes
@Noble_Two: Go

That was a pretty mean thing to say to the developers.

Install a permissions plugin, and setup permissions.

@latoiner: Go

Faction chat was removed. Install HeroChat or FactionChat to use it.

@xavierhorovitz: Go

This depends on your version and such, but it hasn't been updated in a while (It's mostly 1.6.x). Feel free to contribute!

@FateMC: Go

You should not modify the config file directly. Use /f config

@frownnnnn: Go

Be in the same Faction.

@megasnipez_: Go

WorldGuard can do this I'm pretty sure.

Want a faster response from me? Follow me and tweet me on twitter! @markehme
- Reply
- #4508
megasnipez_ May 19, 2013 at 07:22 UTC - 0 likes
how do disable creepers in warzone?
- Reply
- #4507
megasnipez_ May 19, 2013 at 07:15 UTC - 0 likes
@latoiner: Go

/f c was removed find the plugin called factionchat.
- Reply
- #4506
latoiner May 19, 2013 at 05:08 UTC - 0 likes
Why the command /f c doesn't work even OP?
- Reply
- #4505
SparkezzHD May 19, 2013 at 04:08 UTC - 0 likes
I don't see anywhere to change this but people are getting this error. Everytime their own faction member opens a chest in there claimed land they get this message: Your faction does not allow you to open containers! Help?
- Reply
- #4504
monstercat101 May 19, 2013 at 02:52 UTC - 0 likes
When is the spam on other faction entry going to be fixed?
- Reply
- #4503
xavierhorovitz May 19, 2013 at 01:34 UTC - 0 likes
Can someone frickin explain why half the options in the userguide config are not in the real config? This shit is broken.
- Reply
- #4502
faxionsurvival May 19, 2013 at 00:51 UTC - 0 likes
R: 1.8.2 for CB 1.5.2-R0.1 Apr 23, 2013 R: 1.6.9.5 for CB 1.5.2-R0.1 Apr 23, 2013

Both versions are released at the same time and the 1.8.* version is a beta version with many different changes than the stable build of 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.

Last edited May 19, 2013 by faxionsurvival
- Reply
- #4501
FateMC May 18, 2013 at 23:10 UTC - 0 likes
Are you serious.

I updated to 1.8, and it reverted my whole config file and removed

"Role:"

Now, no one owns their factions. Please someone help! I only have a backup from 10 days ago, and we average 50-60 players. Everyone is devestated, and no one owns their own factions anymore. I reverted back to 1.6 but Role: is still removed :(
- Reply
- #4500
Alexlem96 May 18, 2013 at 21:46 UTC - 0 likes
@bloodbath529: Go

Having the Same Problem!