Bukkit

*absolute and utter mindrape upon opening conf.json*

This file has grown. A lot. I haven't used factions for months and the thing is just absolutely HUGE at this point. Yay for gEdit! :D:D

(gEdit > Notepad++ x1337)

@Brettflan

Thanks for the info, will try removing all plugins if that doesn't work.

@denxerator
Have a look over here. I don't keep track of which other chat plugins are compatible or not. The only ones I know for sure are EssentialsChat and ChannelChat, both mentioned in our user guide at that link.

@angelofdev
That error is happening in CraftBukkit's code from something else accessing the same list of players in a world. It shouldn't really be happening unless a plugin (not ours) is running a separate thread which isn't being handled through CraftBukkit as they should. So... either way, nothing we can really do about it in Factions.
If it happens a lot and you (understandably) don't feel like trying to temporarily remove other plugins for an extended time to see if one of them is causing it, you could try disabling our teleport effect: /f config homesTeleportCommandSmokeEffectEnabled false

Since I updated to 1.1-R4 my server crashes with the following error in console.

2012-02-17 15:30:35 [SEVERE] Could not pass event org.bukkit.event.player.PlayerCommandPreprocessEvent to Factions
java.util.ConcurrentModificationException
at java.util.AbstractList$Itr.checkForComodification(Unknown Source)
at java.util.AbstractList$Itr.next(Unknown Source)
at org.bukkit.craftbukkit.CraftWorld.getPlayers(CraftWorld.java:562)
at org.bukkit.craftbukkit.CraftWorld.playEffect(CraftWorld.java:686)
at org.bukkit.craftbukkit.CraftWorld.playEffect(CraftWorld.java:677)
at com.massivecraft.factions.zcore.util.SmokeUtil.spawnSingle(SmokeUtil.java:37)
at com.massivecraft.factions.zcore.util.SmokeUtil.spawnSingleRandom(SmokeUtil.java:47)
at com.massivecraft.factions.zcore.util.SmokeUtil.spawnCloudRandom(SmokeUtil.java:73)
at com.massivecraft.factions.zcore.util.SmokeUtil.spawnCloudRandom(SmokeUtil.java:81)
at com.massivecraft.factions.cmd.CmdHome.perform(CmdHome.java:137)
at com.massivecraft.factions.zcore.MCommand.execute(MCommand.java:126)
at com.massivecraft.factions.cmd.FCommand.execute(FCommand.java:59)
at com.massivecraft.factions.zcore.MCommand.execute(MCommand.java:116)
at com.massivecraft.factions.cmd.FCommand.execute(FCommand.java:59)
at com.massivecraft.factions.zcore.MCommand.execute(MCommand.java:131)
at com.massivecraft.factions.zcore.MPlugin.handleCommand(MPlugin.java:206)
at com.massivecraft.factions.P.handleCommand(P.java:152)
at com.massivecraft.factions.zcore.MPlugin.handleCommand(MPlugin.java:216)
at com.massivecraft.factions.zcore.MPluginSecretPlayerListener.onPlayerCommandPreprocess(MPluginSecretPlayerListener.java:26)
at org.bukkit.plugin.java.JavaPluginLoader$5.execute(JavaPluginLoader.java:298)
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:61)
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:460)
at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.java:777)
at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:744)
at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:732)
at org.getspout.spout.SpoutNetServerHandler.a(SpoutNetServerHandler.java:178)
at net.minecraft.server.Packet3Chat.handle(Packet3Chat.java:33)
at net.minecraft.server.NetworkManager.b(NetworkManager.java:226)
at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:100)
at org.getspout.spout.SpoutNetServerHandler.a(SpoutNetServerHandler.java:587)
at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:78)
at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:537)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:435)
at net.minecraft.server.ThreadServerApplication.run(SourceFile:465)

@ursak

You've probably already figured it out by now, but simply running /f autoclaim again should turn it off. If not, running /f autoclaim once more should definitely do it.

@Brettflan

srs. I even thought of that, but when I went to check the branch, I swear it said I was in 1.6... I've never really used Github before, so that could be the issue. Thanks!

@Brettflan

Glad to hear, yea I just realized it the other day :P

@detox78

Are you sure your change took? You might check the second FAQ entry above to be sure. Those prefixes for faction admins and moderators are not hardcoded in any way, so your problem indicates those values are still set at the default.

@RaesWolf
You can add a world to worldsIgnorePvP to have Factions ignore PvP damage (other than in safe zones). /f config worldsIgnorePvP YourWorldNameHere, then the same command again later to remove it. You could also enable friendly fire for war zones only, though it will affect all war zones: /f config warZoneFriendlyFire true

@HighlifeTTU
There isn't sorry. It would have high potential for spamming messages to members of the target faction.

@DrAgonmoray
I'm guessing you're looking at the main branch of the source, which is our 1.7 dev branch. Ownership is removed from it for the time being until it can be reworked and improved. What you probably want is the 1.6 branch. Though, of course, since an improved ownership system is planned in 1.7.......

@Vitaminous
It will probably work fine when the time comes, I expect; it depends on whether Bukkit has any breaking changes or not. My WorldBorder plugin, on the other hand, will definitely need some changes to the fill and trim commands since they do some direct work with the current region file format.

@Crayder
1. Ah, I think I see now; you're talking about individual war zone claims having friendly fire enabled, rather than all of them. Yeah, sorry, that indeed is not possible in 1.6.x. However, it should be possible for you in 1.7 by letting you create an extra permanent custom warzone faction.
2. Maybe another plugin is interfering? Otherwise, my only guess is as before related to the player world location possibly not always reporting correctly.

@unv_annihilator
Ah, wow, right you are. I could have sworn I had covered that, but I just checked and can confirm it's only running a lowercase conversion on the commands in the list, not the one run by the player. Ack. Thanks for the report, it will be fixed in the next release.

@DrAgonmoray

Noob lol

@Brettflan @Cayorion - For the blacklisted commands in enemy faction territory it doesn't send their command to lowercase which means they can use a command in full caps and if the command in full caps isn't blocked then they can use it. You should probably toss their command to lowercase as well can check commands all in lowercase to avoid this issue.

-Thanks

Any idea how Factions will work with .mra (cuboid chunks)? Would the plugin in its current iteration work at all?

Hi- Trying to make Factions better by adding features via Github. I'm going to hopefully add things relating to land ownership. I've searched every file in the Github source, and I've yet to find the place where the owner of a plot of land is defined. Could you perhaps point me in the right direction?

Thanks!

is there a way to set some form of friendly fire on? So during say free for all pvp events people can kill each other even if they are in the same faction?

@Crayder
What? I just gave you the command to enable friendly fire in WarZones only. The name of the setting should make it quite clear regardless.
As for that issue you're having with people transitioning between worlds, it would almost have to be a CraftBukkit problem. Mostly likely caused by a lagging server. Factions checks the location of the person being attacked. If CraftBukkit is not reporting an up-to-date world for them, there's nothing we can really do about that.

@NoelleMinuet
Other than recommending you make absolutely 100% completely certain that you are running the latest version of Factions and CraftBukkit and all of your other plugins, I don't know of any recent issues that might cause that other than it maybe being related to that incorrect location issue Crayder seems to be having.