Bukkit

@Luxius96

I just tested using the latest dev build of Spoutcraft (1197), the latest dev build of SpoutPlugin (988), with the latest dev build of CraftBukkit (2083) and Factions 1.6.7, and faction leader capes and colored faction tags over peoples heads worked for me.
I didn't test with CraftBukkit Beta 1.2.3-R0.2 since the latest dev build of SpoutPlugin didn't load on it, as indicated at server startup; it indicated it wasn't build for that CraftBukkit version. Maybe that's your problem? Check your server startup log.

@Toxicminers

Can you paste your server startup log with all loading information (from the very start until after Factions finishes loading)? Also, have you checked the logs for any error that might be occurring when they're having problems?

Needless to say, I'm unable to duplicate your problem on 1.6.7 and CB 1.2.3-R0.2.

Why dont work with spoutcraft for 1.2.3?(SPOUT OPTIONAL)

I dont see cape and more..

@imdynamo

No configuration should be necessary, and I've tested it in 1.6.7 on CB 1.2.3-R0.2 with damage between enemies working in the territory of either.
What message do they get hen trying to attack each other? Is there any error logged? What version of Factions and what version of CraftBukkit are you using (check the actual version numbers in your server startup log, don't just say "latest version" please)?

@Luxius96

Not yet, as I said.

You dont create the messages properties for translate? :(

@Hol7y96

Read the FAQ.

@Luxius96

The ability to translate is on my to-do list, but due to it requiring a complete overhaul of pretty much every file, it will need to wait until the 1.7 branch is ready to fully replace the 1.6 branch. There's no way I'm doing that huge overhaul on two codebases.

I want to translate this plugin for my language >-< i can help you?

@Luxius96

Huh?

Can you add the messages properties?

@A1ter

I understood, and as I said, it would add considerable overhead to explosion handling. For each explosion it would need to check a list of all online players, find any in the target faction, and then check the locations of each until it finds one which is in their own territory. In 1.7 I think it would actually need to do that for every block destroyed in the explosion, barring a complicated rewrite of how that's handled.

Released version 1.6.7:

• Fix: If plugin failed to load correctly for various reasons, it could potentially end up wiping the board or faction list. This should now be prevented. Example: if you loaded 1.6.6 (not 1.6.6b) on CB 1.1-R6 or newer, it would trigger an exception at startup and cause this problem.
• Custom events are now provided for other developers to hook into to create their own plugins based around Factions! Check the factions/event folder in our source for the currently implemented events. (by patrickfreed, bladedpenguin, and donington)
• Removed dependence on external GSON lib in lib/gson.jar. GSON 2.1 is now embedded in CraftBukkit itself.
• New setting "logPlayerCommands" (default true) which can be disabled to prevent player commands from being logged.
• New setting "playersWhoBypassAllProtection" (default empty), which is a list of player names that should always bypass normal faction protections such as block destruction and placement. This is primarily for use with other plugins/mods which use a fake player to take action, which shouldn't necessarily be subject to protections provided by Factions. Note that case is important; you must preserve the exact capitalization of the name.

• Reworked radius claim method. The old method tried to put together a list of chunks, and then tried to claim them all in one go starting from one corner of the overall area. It now starts in the current chunk and spirals outward, in a repeating task designed to keep from overloading the server. New setting "radiusClaimFailureLimit" (default 9). If claims are unsuccessful that many times in a row during a radius claim, the task will cancel out. There is no longer a limit to the specified radius since the process should no longer cause major server stress, and due to the process canceling out after several failures as just described.
• Faction homes should no longer be lost if their target world isn't already loaded when Factions loads at server startup. This is done using a new lazy-load Location container class which only initializes the Location when it's actually needed.
• Fixed slashless commands not being logged if player was in faction chat or alliance chat mode.
• Fix for "econClaimUnconnectedFee" not working correctly.
• Connected standard command handler getCommand("f"), solely for the sake of other plugins which might directly execute commands using that interface.
• Various minor optimizations and cleanup.

New conf.json settings:
"logPlayerCommands": true, can be disabled to prevent player commands from being logged.
"radiusClaimFailureLimit": 9, when someone is attempting a radius claim, it will halt if this many claim attempts in a row are unsuccessful.
"playersWhoBypassAllProtection": [], list of player names that should always bypass normal faction protections such as block destruction and placement. Primarily for use with other plugins/mods which use a fake player to take actions.

@Zwoz

I doubt HomeSpawnPlus is actually causing any problems with faction homes. Maybe those faction homes were in worlds which are not yet loaded at server startup? If so, such home locations are lost since Bukkit Locations require a loaded world reference. Our next release should take care of that annoyance, though.
As for coordinates of faction territory, you might have trouble beyond just using /f map. If you were dedicated enough you could get their faction ID (by checking in factions.json) and look for a coordinate in board.json which is set to that faction ID. If you found such a coordinate, you could then translate it to standard world coordinates by multiplying each number by 16. They're stored in board.json as "X,Z": "factionID".

@HollywoodMinersCentral

Factions only interfaces with SuperPerms, but PermissionsEx should be doing so as well. Read our FAQ above regarding removing permissions.

@ShyOblivion

You can't directly set power levels for a player, sorry, you can only provide a boost/penalty (via /f powerboost).

@juodas

The current release.

@A1ter

That would add a fair bit more overhead to explosion handling, so probably not going to happen. Sorry.