Bukkit

@ThaSourceGaming

What type of error is shown right above the part you have in the screenshot? The line number shown there is very helpful, but we are currently set up on that line to catch a specific formatting error. The one you're receiving is apparently a different formatting error, though.

You might try this as a quick fix, it works to handle the other error that we catch on that line:
/f config chatTagInsertIndex 0
The better fix would probably be to check through the different chat integration methods we have covered in the user guide.

Either way, I'd still be rather interested to know what exception type is reported in your error message. The one we currently catch is "UnknownFormatConversionException". For that matter, I'd be interested to see the chat configuration settings you have set in conf.json. If I can add in a way for Factions to catch the type of error you're getting now as well, that would be nice.

@Skadar

Yeah, that's a pretty typical setup.

Factions and WorldGuard work fine together, though as a word of warning, our specific WorldGuard integration feature ("worldGuardChecking") is broken, so you shouldn't try to use it.
As for whether WorldGuard is necessary, that's up to you to decide. It does provide quite a lot of good features; it just depends on whether you need or want them. I personally don't run WorldGuard on my server as I don't need it, but that's just my situation.

@twisted420mc
No idea then, same as to begin with. Unless you changed this setting in conf.json, but you seem to have indicated otherwise:

"chatTagReplaceString": "{FACTION}",

Hmm. Not that it should be relevant, but what version of Essentials are you using?

EDIT: OK, it is actually relevant. It looks like they've changed something in Essentials 2.8 that broke the chat integration. I'll see about getting that fixed soonish if possible.

@Conderan
I notice an error regarding LWC integration and that you're using 1.6.3; take a glance at the changelog for 1.6.4 and then go update to it.

@michalkomar
Nothing should have changed in 1.6.3 or 1.6.4 which should be able to cause something like that.
... And I just tested it in 1.6.4 trying to use /f home near an enemy, and it prevented me as expected.

What version are you running?

I've added a FAQ above which should hopefully reduce the number of commonly repeated questions at least a little bit.

@Conderan

I need the rest of the stack trace from that error info for it to be useful.

@domingo15
Our permissions are listed in the user manual.

@twisted420mc
I have no problems with Essentials and local chat. I use it on my own server. Essentials chat config:

chat:
  radius: 50
  format: '<{FACTION} {DISPLAYNAME}> {MESSAGE}'

@Hummer2008
Tested using that exact faction name and command in 1.6.3 and couldn't duplicate your problem. It shouldn't be able to crash your server without even outputting any error to your server log, and without that... I don't know what else to tell you.

@HelloWorldCool
Commands never work in the console with a slash, FYI. You'll find that's the case with other plugin commands as well. That's just how CraftBukkit works. Remove the slash.

@nitr0burn
The kit is granted by default, but some permission plugins remove all such default permissions. They're probably doing that, which is fine; since you're using such a plugin, you would likely want finer control of permissions anyway. The reason we grant that permission kit by default is so people can use Factions without necessarily needing a permission plugin or to configure permissions.yml at all.