Bukkit

@fifawinner

Your version of CraftBukkit is outdated. Update to 1.1-R4.

@harleyhash

Out of curiosity, what were you talking about? What was saying something needed updating?

Version 1.6.6

• Damage protection is now extended to being set on fire (by flaming arrows, for instance) and receiving harmful splash potion effects. Beneficial splash potions are unaffected, and prevention of harmful splash potion effects is handled on a player-by-player basis, so you can still harm yourself if you're not careful where you throw them.
• New setting "homesTeleportCommandEssentialsIntegration" (default true) which, if enabled, will integrate /f home teleports with the Essentials plugin's teleport handler if Essentials is on the server. This provides teleport cooldown and/or delay to /f home based on your Essentials configuration. (Olof)
• Added possibility to specify a player in the /f join command (/f join <faction> [player=you]), to make a player other than yourself join the specified faction. The new permission factions.join.others (added to factions.kit.mod and above) is required to be able to specify a different player. Note that the player cannot currently already be in another faction; if they are, you'll need to /f kick them first. Also note that if the faction isn't open (with no invitation required), the player isn't invited, and you don't have the factions.join.any permission or have admin bypass mode on, the attempt will also fail.
• New setting "factionMemberLimit" (default 0, no limit), which will prevent players from joining any faction that has reached this membership limit.
• Added command logging for commands used by players. (Olof)
• "autoLeaveAfterDaysOfInactivity" routine now runs only once every few minutes instead of running every time a player logs in. New setting "autoLeaveRoutineRunsEveryXMinutes" (default 5 minutes) to determine just how often the routine is run. The routine is also slightly more careful now about how it calculates how long a player has been offline.
• Updated various things for compatibility with upcoming CB 1.1-R5 and above while still being compatible with 1.1-R4. Also updated Spout integration to handle deprecated stuff.
• Updated default GSON jar version to 2.1. For existing users, you can either delete the lib/gson.jar file on your server so Factions can download the newer version, or just download and replace it yourself: https://github.com/downloads/MassiveCraft/Factions/gson.jar (note: old version still works fine, new version just works slightly better)
• Other plugins which prevent commands should be more likely to work: our PlayerCommandPreprocessEvent handler is now at Low priority instead of Lowest priority. (Olof)
• "worldsIgnorePvP" setting no longer ignores PvP damage in SafeZones and PvP damage done by players who just logged in, no matter the world it happens in.
• Fix for command prevention routine (used by territoryEnemyDenyCommands and such) not properly covering commands with uppercase letters in them.
• Fix for potential rare NPE triggered in LWC integration where the location world returns null for whatever reason.
• Fix for error when disbanding faction from server console with economy enabled.
• Hopeful fix for rare errors where location world changes partway through trying to show a smoke effect for /f home.
• Updated CAPI integration. (Olof)
• Hopeful fix for chatspy not working with CAPI chat integration.

New conf.json settings:
"homesTeleportCommandEssentialsIntegration": true, whether to hook /f home into the Essentials plugin's teleport handling (for delay and cooldown) if it's available
"factionMemberLimit": 0, if set to anything higher than 0, players will be prevented from joining any faction which reaches this limit
"autoLeaveRoutineRunsEveryXMinutes": 5.0, "autoLeaveAfterDaysOfInactivity" routine runs this often; for example, the default value makes it run once every 5 minutes

New permission:
factions.join.others - allows you to specify another player in the /f join command. Included in factions.kit.mod permission kit and above.

Updated command:
/f join <faction> [player=you] - join a faction. To specify a player other than yourself, you must have the factions.join.others permission.

Ok, thanks for the info, looking forward to it.

@kotpx3

/f home warmup: see change log for upcoming release. As for allowing certain actions, yes, there are plenty of settings for that. Read the user guide, specifically the Configuration page.

@fghjconner

A couple of other devs have decided to contribute by adding in some events for other plugins to be able to listen for, including that one. From the sound of things, they'll probably have them ready for the release after this one which I'll be posting shortly (1.6.6).

I was looking into coding a plugin that hooked into Factions, but I couldn't find any way to be informed when a player claims land for a faction. If I've somehow missed something could you let me know, and if not, would you consider adding a method for plugins to get this information? Thanks

@rebel24

Yes.

Hey, can you please update for R5?

@Konzil

I don't use it, so you'd probably know better than me. A lot of permission plugins support granting the permission kits but don't support denying permission kits, like I covered in the first FAQ entry above.

@Lildirt

In that case, it should be handled in our 1.7 branch which has an attribute flag system for factions that allows for such things.
EDIT: to clarify, you should probably wait for at least a beta release in the 1.7 branch; our 1.7 branch currently has several major features removed and doesn't completely handle upgrades from 1.6.x data files as well as it should, among other issues, which is why it's still marked as a non-production alpha.

@Brettflan

    I think I know what he means; he wants to be able to define custom area's that people can build, and attack anyone they want. Perhaps creating a new system faction for it?
    Who knows.

    I've thought about it, and maybe you can add the ability to make our own system factions, where we could set custom attributes in the factions.json or whatever file you want to, and poof! We has perfection.

    This would also solve a lot of issues with people having his issue, not just me and him. Although, I've fixed my issue; I have a world designated for the "War" plugin, which I can ignore PvP.

@Luxius96

Use WorldGuard or another plugin to block the command usage in that area. If you use WorldGuard regions, I believe it's something like blocked-commands/blocked-cmds for the flag. I'm unsure of how to use it really, but it's definitely possible.

I have another problem... /f home work in mob arena >.< can you add support

@AlexSmith49

I'm not sure I understand what problem you're running into. Perhaps "warZoneFriendlyFire" isn't what you need due to wanting only some war zone areas to have friendly fire on instead of all of them? Even considering that, I don't see how unclaiming a war zone would somehow allow another plugin to get around Factions' PvP handling in that area. So... I admit, you've left me slightly confused.

@UnitedFactions
That error isn't related to Factions, no. It's occurring independently in the core Minecraft server code, possibly not even the fault of CraftBukkit. The CraftBukkit bug tracker would be the place to report it either way, though.

@Luxius96
An option like your first one to limit the number of members any faction can have might be a decent option. It would simply prevent /f join from working if the faction is at or above that cap. Yeah, I'll probably do that.

The other three... I'd rather not add anything else to complicate and therefore slow down the autoLeaveAfterDaysOfInactivity routine. However, as I'm planning to revamp that routine to make it less likely to be stressful on large servers, I might be willing after that if I have time for it (which honestly isn't too likely, barring a donation).