Now under a new maintainer: Tux2!

PREVENTS all forms of grief, including build/break, theft, spam, fire, spawn camping, lava, and treetops, so you don't have to rollback! No configuration or database required! Stop responding to grief and prevent it instead. Grief Prevention will solve your grief problems without requiring you to manage a large roster of trained administrators, juggle 10 different anti-grief plugins, take away cool standard game features, publish a manual, or add a pile of explanatory signs to your world. You can also choose to integrate PvP elements into build design to finally get a PvP experience befitting a sandbox game about creativity.

Grief Prevention stops grief before it starts automatically without any effort from administrators, and with very little (self service) effort from players. Solve all your grief problems with a single download, no database, and no configuration step.

Troubleshooting and Common Questions

Save yourself some time! Check this page for the answer to your question.

Feed the Beast and Tekkit Lite Compatibility

I have heard reports on this plugin working fairly reasonably on Tekkit Lite/Feed the Beast servers, however, this is entirely unsupported due to large holes in the way mods are coded and the incomplete nature of the BukkitForge mod. If you choose to use it you do it at your own risk! There are plenty of things that bypass GriefPrevention in the mods, which means you will need to disable quite a bit (mining lasers, iTNT, etc.), including MystCraft, as the way GriefPrevention is coded it makes it incompatible with MystCraft without breaking the GriefPrevention API terribly and the need to totally overhaul of the design of the plugin.

In-Depth Topics

Development Builds

Development builds of this project can be acquired at the provided continuous integration server. These builds have not been approved by the BukkitDev staff. Use them at your own risk.
Development builds can be found here

Feature List

Yes, everything is customizable. See administrative details.

No database or world backups required.

Extremely efficient CPU / RAM usage.

Land claims are easy to manage.
- New players get automatic claims around their first chests.
- Players who ask for help in chat get an instant link to a demonstration video.
- Resizing claims and creating new claims is done with ONLY the mouse, no slash commands.
- When a player appears to be building something nice outside his claim, he's warned and shown his claim boundaries.
- Claim boundaries are easy to see, and don't require any client-side mod installation.
- Extremely easy-to-remember, single-parameter slash commands for giving other players permissions.
- Claim subdivision and granular permissions are available to organize towns and cities. Watch this video.

It's IMPOSSIBLE to grief a land claim. Watch this video.
- No building or breaking.
- No stealing from ANY containers.
- No using crafting equipment.
- No sleeping in beds.
- No button/lever usage.
- No adjusting redstone repeaters.
- No pushing blocks in with pistons.
- No pulling blocks out with pistons.
- No TNT damage.
- No creeper damage.
- No damage from TNT cannons.
- No explosive damage from other plugins, like Extra Hard Mode or Magic Spells.
- No enderman block changes.
- All doors may be automatically locked (optional, see config file).
- No killing or luring animals away.
- No stealing water.
- No trampling crops, by players, animals, or monsters.
- No growing trees inside the claim by planting outside.
- No building overtop, all claims reach to the max build height.
- No placing or breaking paintings / item frames.
- Fluids will not flow into a claim from outside.

Excellent anti-spam protection
- Warns, then mutes, then may kick or bans (configurable) spammers.
- Most spammers get only one message out before they're muted.
- Almost no false positives.
- Blocks server advertising.
- Blocks repeat message spam.
- Blocks ASCII art (ex. Nyan Cats) spam.
- Blocks similar message spam.
- Blocks unreadable (gibberish) message spam.
- Blocks CAPS.
- Blocks macro spam (very different messages in quick succession).
- Blocks login/logout spam, even when the spammer has multiple accounts.
- Blocks death spam.
- Blocks slash command spam, including /tell, /emote, and any more you add.

Wilderness Protection and Rollback
- Fire doesn't spread or destroy blocks.
- Creepers and other explosions don't destroy blocks above sea level.
- TNT doesn't destroy blocks above sea level.
- Griefers can't dump water or lava above sea level, unless they claim the land first.
  - The fluid will not flow out of the claim.
  - Deleting the claim removes the fluid to prevent spillage.
- No planting trees on platforms in the sky ("tree grief").
- Instant, point and click nature restoration for not-claimed areas. Watch this video.
  - Insanely easy and fast fixes for penises, swastikas, and anything else unsightly.
  - Point at what you don't like and click, and it's fixed. Even from far away.
  - Never accidentally changes blocks inside land claims.
  - No need to investigate who built it, who broke it, or when they did it.
  - Doesn't matter if the griefer built with "natural" blocks, it will still be fixed.
  - No database.
  - No backups.
  - No chunk regeneration (it's dangerous for technical reasons).
  - Fixes bad chunk generations, like floating islands. It will be better than new.
  - Fills holes, even next to water to correct big spills.
  - Smooths noisy terrain.
  - No griefer construction is safe. If it's unnatural enough to be noticeable by players, it will be removed or filled-in.

Land claims can't be used as a griefing tool.
- Land claims beyond the first require a golden shovel.
- Minimum claim size prevents sprinkling small claims to annoy other players.
- Max claim allowance grows with time played on the server, and can't be cheated by idling.
- It's impossible to get a player "stuck" inside a land claim.
- A simple administrative slash command will instantly remove all of a griefer's claims, no matter where they are.

Catches clever griefers.
- Enhances the /ban command to ban ALL a griefer's accounts (not just his IP address).
- Logs sign placements.
- Optionally, logs whispers and opens them to administrative eavesdropping.

PvP Protections.
- When PvP is off, no setting fire or dumping lava near other players.
- Absolutely bullet-proof anti-spawn-camping protection, which requires no configuration.
- No logging out, stashing items, or using plugin teleportation to escape combat.
- Optional siege mode, to answer players who hide in their claimed houses to avoid combat.

Supports your server growth.
- Permit players to exchange server currency for claim blocks (requires configuration and other plugins).
- Grant claim blocks automatically for votes, donations, etc (console command provided, other plugins required).

Even works with Tekkit (requires configuration).

Extensions

There is a DynMap plugin for GriefPrevention, which adds markers for player claims to your DynMap.

If you want to your players to buy/sell/lease claims, then you can install the Real Estate plugin for GriefPrevention.

GriefPrevention Flags adds flags to your grief prevention claims for PvP (admin claims only), and Mob spawning at the moment. (More features in the works!)

More Great Plugins!

Anti-XRay
- Limits how quickly players can mine valuables, based on their play time / values mined ratio.
- Keeps your valuables in the ground, so non-cheating players can find them (unlike ore loggers).
- Practically free to run, unlike the tremendously expensive Orebfuscator.
- Most legit players won't notice, but xrayers will ragequit and move on.

Population Density
- Automatically assigns new players to wilderness where they'll find other new players and plenty of space, wood, and ore.
- Optional teleportation system which can't be abused by players to escape combat or save them from being lost.
- Login queue to guarantee fairness when the server is full.
- Optional reserved spots for administrators.
- Automatically removes idle players when the server is nearly full.

EnderHoppers
- Allows the use of Hoppers with EnderChests inside a Claim
- Items are taken from and added to the EnderChest inventory of the Claim owner

Command Reference

Player Commands

Command	Description	Aliases
/AbandonClaim	Deletes the claim you're standing in.
/ClaimExplosions	Toggles if explosions are allowed in the claim.
/Trust	Gives another player permission to edit in your claim.	/t
/UnTrust	Revokes any permissions granted to a player in your claim.	/ut
/AccessTrust	Gives a player permission to use your buttons, levers, and beds.	/at
/ContainerTrust	Gives a player permission to use your buttons, levers, beds, crafting gear, containers, and animals.	/ct
/TrustList	Lists the permissions for the claim you're standing in.
/SubdivideClaims	Switches your shovel to subdivision mode, so you can subdivide your claims.	/sc
/BasicClaims	Puts your shovel back in basic claims mode.	/bc
/PermissionTrust	Grants a player permission to share his permission level with others.	/pt
/Untrust All	Removes all permissions for all players in your claim.
/AbandonAllClaims	Deletes all of your claims.
/BuyClaimBlocks	Converts server money to claim blocks.	/BuyClaim
/SellClaimBlocks	Converts claim blocks to server money.	/SellClaim

Admin Commands

All of the permissions below start with "griefprevention.". For example, "restorenature" is "griefprevention.restorenature".

Command	Description	Permission	Aliases
/AdjustBonusClaimBlocks	Adjusts the number of claim blocks available to a player.	adjustclaimblocks	/acb
/RestoreNature	Switches the shovel to restore nature mode.	restorenature	/rn
/RestoreNatureAggressive	Switches the shovel to aggressive restore mode.	restorenatureaggressive	/rna
/RestoreNatureFill	Switches the shovel to fill mode.	restorenatureaggressive	/rnf
/IgnoreClaims	Toggles claims override.	ignoreclaims	/ic
/AdminClaims	Switches the shovel to administrative claims mode.	adminclaims	/ac
/BasicClaims	Switches the shovel back to basic claims mode.		/bc
/DeleteClaim	Deletes the claim you're standing in.	deleteclaims	/dc
/DeleteAllClaims	Deletes all claims belonging to a specific player.	deleteclaims
/DeathBlow	Kills a player, optionally giving his items to another.	deathblow
/ClaimsList	Lists a player's claims and claim block details.	adjustclaimblocks

Permissions

Permission	Description
griefprevention.deathblow	Allows the use of the /deathblow command
griefprevention.restorenature	Allows the use of the /restorenature command
griefprevention.restorenatureaggressive	Allows the use of the /restorenatureaggressive command
griefprevention.lava	Players with the permission may place lava anywhere they have build permission, but still not near other players.
griefprevention.adminclaims	Allows creating, deleting and building for an admin claim
griefprevention.ignoreclaims	Allows the player to ignore claims using the /ignoreclaims command
griefprevention.deleteclaims	Allows the player to delete and resize other player's claims
griefprevention.createclaims	Allows players to create additional claims when Claims.CreationRequiresPermission is set to true
griefprevention.claims	This permission is granted to everyone by default, and is necessary for the claims-related slash commands.
griefprevention.buysellclaimblocks	This permission is granted to everyone by default and allows the player the ability to buy/sell claim blocks
griefprevention.adjustclaimblocks	Allows the player to adjust player's bonus claim blocks amount
griefprevention.eavesdrop	Allows the player to see PMs
griefprevention.admineavesdrop	Only in versions for MC 1.5 and up Allows a player to see PMs from players with the griefprevention.eavesdrop permission as well.
griefprevention.spam	Allows the player to bypass the spam protection
griefprevention.loginspam	MC 1.5 and up Allows the player to bypass the login spam protection

Official Servers

You can experience this plugin for yourself (as a player) by joining any of these public servers. :) I maintain these servers personally, which helps me catch bugs and spot opportunities for new features and improvements. Have fun!

Epic Minecrafter play.epicminecrafter.com

Performance

According to the Bukkit wiki, a CraftBukkit server should have 1GB of RAM per 20 player slots. If you follow that guidance and run a reasonable number of plugins, I guarantee that you will not have a problem with lag or memory usage. I can say this with certainty because I'm running a middle-tier (as in, average pricing) hosted servers with the recommended RAM/players ratio, and I run several additional plugins with no issues. This has been my experience over several months running anywhere from 1 to 4 servers with an active player population.

It is normal for your server to spend more time running Grief Prevention code versus other plugins. After all, GP is watching all your players all the time, and is keeping them all happy while not bothering you. Grief Prevention is extremely efficient at doing its job - performance has been and always will be the most important factor in design and implementation decisions, because the only thing worse than a griefy server is a laggy server.

Of course any server owner will eventually have a problem if he pushes his hardware too much, for example by running lots of heavyweight plugins. If you do have a problem, the solutions are to either add more RAM/cpu power, re-prioritize your plugins to drop a few you don't desperately need or reduce your max players.

Notes for Tekkit Servers

"Classic" Tekkit servers are currently running Minecraft 1.2.5. That means you must download an earlier version of GriefPrevention which is compatible with 1.2.5. Currently, the best version compatible with Tekkit is GriefPrevention 5.5.1, which you can get by clicking the blue "files" link at the top of the page.

To protect the NEW container blocks added by Tekkit, you must add their block IDs to your Grief Prevention config file. Also, you'll want to add blocks which blow themselves up (steam engines, nuclear reactors) to that same config file.

Tekkit is NOT 100% compatible with Bukkit, AND it is not designed for Multiplayer (it was designed for single player). Some Tekkit items and blocks completely bypass all Bukkit plugins, which means they bypass any anti-grief code, are not logged by block loggers, and can't be rolled-back by block loggers. Therefore, a few Tekkit items MUST BE BANNED if you run a public or semi-public server. I highly recommend that you install TekkitCustomizer, because it has a very good default ban list, and it's extremely easy for you to customize.

If you're running Tekkit Lite or some other flavor of Tekkit, you may need a DIFFERENT version of Grief Prevention which matches your CraftBukkit version. Further, you should read this.

Developer's Notes

The To-Don't List

The following features have been requested a few times, but I don't plan to add them because they're not anti-grief features (and this is an anti-grief plugin). I hope you understand that thinking - one sure way to ruin a plugin is to stuff in a bunch of unnecessary features that hurt performance, increase memory consumption, and don't help solve the core problem the plugin was designed for. I don't want anyone to have to give up all the great anti-grief features of GP just because they would also be forced to accept features they don't need.

Having said all that, I do understand that some non-anti-grief features may be desirable for many. So I have created a public API, which means that other developers could create plugins which extend grief prevention to add these features as a separate download for server owners who want them. That way, server owners who want them can get them, and those who don't aren't forced to accept them. The source code is also available On GitHub, so if you have a "rare" ask, you can add custom features yourself, or have someone else add them for you.

Of the features listed below, those in bold could be implemented as extension plugins by using the public API I've provided. Those in italics can be accomplished by running another protection plugin like WorldGuard or Residence in addition to GriefPrevention, by restricting the other plugin to be used only by administrators. You can read more on the Frequently Asked Questions page.

Enter/Exit messages for claims.

Adding flags to claims to pause hunger, prevent monster spawns, etc.

Putting claims inside of claims inside of claims inside of claims inside of claims inside of claims inside of claims...

Extending GriefPrevention

Hey developers, have something to add? :) Public API Documentation

Contacting the Devs

Both BC_Programming and Tux2 check comments and Tickets here, so if you leave a comment or Ticket we will see it within a few days. We are also available on IRC, at irc.mibbit.com in the #pinoygamers channel.

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

4609 comments
1
2
3
100
200
300
400
459
460
461
Next →

- Reply
- #4885
BC_Programming May 25, 2013 at 21:52 UTC - 0 likes
@cheracc: Go

just popped that off into the next dev build just now. I replied to the ticket with a bit more info and, in particular, some of the new configuration settings applicable for the setting. (short story /plugins/GriefPreventionData/WorldConfig/<worldname>.cfg is now where you will find most settings.
- Reply
- #4884
cheracc May 25, 2013 at 20:30 UTC - 0 likes
Thank you so much for all the recent updates. I'm glad to see new life breathed into the best anti grief plugin available!

I posted a reply to a fairly old ticket and I'm not sure that it got noticed. In short, I'd love to have the "force claims in survival" mode allow blocks on the "trash blocks" list to be broken in addition to being able to be placed. The ticket is here: http://dev.bukkit.org/server-mods/grief-prevention/tickets/14-request-forced-claim-survival-mode/

Thank you again for all you do!
- Reply
- #4883
BC_Programming May 25, 2013 at 10:44 UTC - 0 likes
@marubal21: Go

"but does it mean that a player can still use enderpearls within a claim"

Yes. If the destination location is inside a claim that the player doesn't have access trust in, the teleport is cancelled.
- Reply
- #4882
marubal21 May 25, 2013 at 09:10 UTC - 0 likes
@BC_Programming: Go

but does it mean that a player can still use enderpearls within a claim, and it just prevents them from warping from outside the claim into the claim. Reason i ask is i'll trying to prevent enderpearls glitching through walls. Such as in these vedios : http:www.youtube.com/watch?v=1E0u5Hq5-qc, http:www.youtube.com/watch?v=XHsT9L1Iodg, http:www.youtube.com/watch?v=chFzWz_-kt4. Could an option to prevent enderpearls working in a claim be added?
- Reply
- #4881
BC_Programming May 25, 2013 at 07:40 UTC - 0 likes
@marubal21: Go

When you have it set you have to have access trust on a claim to teleport into it with an enderpearl.
- Reply
- #4880
marubal21 May 25, 2013 at 06:48 UTC - 0 likes
Can someone explain the EnderPearlsRequireAccessTrust flag to me? I'm not sure what it controls, i currently have it set to true and players and still use Ender Pearls in my claims. i have my claim set to allow the public to use my container, when i use the /trustlist command it shows c: public.
- Reply
- #4879
BC_Programming May 25, 2013 at 04:45 UTC - 0 likes
@CayleRose: Go 1. It's a dev build. 2. It's a dev build from May 11th.

I'll have to repro the AbandonClaim issue, that might still exist.

@Senophoe: Go

For some reason they are using a dev build from before build #29, which is around when I removed the "checking player matches" debug output.

Also, Thanks for your testing, I'll look into those discrepancies.

WitherEating is supposed to configure which blocks the withers can eat. Withers 'eat' blocks to get at their targets.

Wither explosions should include both the large explosion Withers make when they fully charge as well as explosions from their Wither skull projectiles.

"Other" explosions is used for any explosion that GP cannot identify. Presumably this would occur most frequently for modded servers.

I'm also going to add similar 'option sets' for where withers and the golems can be spawned (ideally dropping the used blocks when they are cancelled). Many other options are ripe for being expanded to this once I resolve current issues. Options I plan to expand to this new setup would be many of the current true/false settings:

EnvironmentalVehicleDamage,PreventTheft,PreventTrades,ProtectCreatures,PreventButtonsSwitches,LockWoodenDoors,LockTrapDoors,LockFenceGates,EnderPearlsRequireAccessTrust, etc.

Last edited May 25, 2013 by BC_Programming
- Reply
- #4878
Senophoe May 24, 2013 at 23:44 UTC - 0 likes
@CayleRose: Go

You are using the dev build #44 BC_Programming just posted, right? /abandonallclaims and /abandonclaim (the second time you have to write it) are causing that error.

@BC_Programming: Go

The new "framework" is way better than I thought it would be! As flexible as hell. I spent some time testing it and here are the 2 issues I found so far:

a - /abandonclaim & /abandonallclaims as stated by @CayleRose: Go

b - TNT and Creeper explosions affecting regions outside claims.
1. TNTExplosions: BelowSeaLevelWilderness: false BelowSeaLevelClaims: false AboveSeaLevelWilderness: false AboveSeaLevelClaims: false
2. Create a claim.
3. Use /claimexplosions so blocks can be destroyed by TNT.
4. Place a TNT near the border, inside your claim, and explode it.
Notice that blocks outside the claim are going to be destroyed too. Creepers also have the same effect.

Also, what does the WitherEating thing do?
- Reply
- #4877
CayleRose May 24, 2013 at 20:26 UTC - 0 likes
Nonstop SPAM from this plugin... Making even my $2100 computer lag.

Why is it even telling me "sending claim" or "block belongs to player"? Its horrible

3:13:02 PM [INFO] Checking player nnsd2 matches ksungj 3:13:06 PM [INFO] sending BlockClaimed to player:nnsd2 3:13:06 PM [INFO] sending BlockClaimed to player:nnsd2 3:13:07 PM [INFO] Checking player Reselectionz matches whatwordsmiss 3:13:07 PM [INFO] Checking player Reselectionz matches jesuschrist_ 3:13:13 PM [INFO] Connection reset 3:13:18 PM [INFO] Reselectionz issued server command: /warp j 3:13:20 PM [INFO] Reselectionz issued server command: /warp j 3:13:23 PM [INFO] Reselectionz issued server command: /tpa nn 3:13:27 PM [INFO] nnsd2 issued server command: /tpaccept 3:13:32 PM [INFO] [ClearLag] Warning Ground items will be removed in one minute! 3:13:35 PM [INFO] [world]<[Guest]watermage1010> how do you get to survial 3:13:37 PM [INFO] [world_original]<[Guest]Reselectionz> ooh hier 3:13:39 PM [INFO] nnsd2 issued server command: /warp Isle 3:13:41 PM [INFO] sending BlockClaimed to player:nnsd2 3:13:41 PM [INFO] sending BlockClaimed to player:nnsd2 3:13:44 PM [INFO] sending BlockClaimed to player:nnsd2 3:13:48 PM [INFO] CNP628 issued server command: /abandonclaim 3:13:48 PM [INFO] sending AbandonClaimMissing to player:CNP628 3:13:48 PM [SEVERE] null org.bukkit.command.CommandException: Unhandled exception executing command 'abandonclaim' in plugin GriefPrevention v7.7 at org.bukkit.command.PluginCommand.execute(PluginCommand.java:46) at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:189) at org.bukkit.craftbukkit.v1_5_R3.CraftServer.dispatchCommand(CraftServer.java:523) at net.minecraft.server.v1_5_R3.PlayerConnection.handleCommand(PlayerConnection.java:965) at net.minecraft.server.v1_5_R3.PlayerConnection.chat(PlayerConnection.java:883) at net.minecraft.server.v1_5_R3.PlayerConnection.a(PlayerConnection.java:840) at net.minecraft.server.v1_5_R3.Packet3Chat.handle(Packet3Chat.java:44) at net.minecraft.server.v1_5_R3.NetworkManager.b(NetworkManager.java:292) at net.minecraft.server.v1_5_R3.PlayerConnection.d(PlayerConnection.java:109) at net.minecraft.server.v1_5_R3.ServerConnection.b(SourceFile:35) at net.minecraft.server.v1_5_R3.DedicatedServerConnection.b(SourceFile:30) at net.minecraft.server.v1_5_R3.MinecraftServer.r(MinecraftServer.java:581) at net.minecraft.server.v1_5_R3.DedicatedServer.r(DedicatedServer.java:226) at net.minecraft.server.v1_5_R3.MinecraftServer.q(MinecraftServer.java:477) at net.minecraft.server.v1_5_R3.MinecraftServer.run(MinecraftServer.java:410) at net.minecraft.server.v1_5_R3.ThreadServerApplication.run(SourceFile:573) Caused by: java.lang.NullPointerException at me.ryanhamshire.GriefPrevention.GriefPrevention.abandonClaimHandler(GriefPrevention.java:2085) at me.ryanhamshire.GriefPrevention.GriefPrevention.onCommand(GriefPrevention.java:882) at org.bukkit.command.PluginCommand.execute(PluginCommand.java:44) ... 15 more
- Reply
- #4876
BC_Programming May 24, 2013 at 18:56 UTC - 0 likes
<<reply 1512390>>

Latest dev build implements a new "framework" of options. I got to thinking about the problem, and what we have are several "actions"  that we want to define as being possible inside and outside claims and above or below sea level. My solution involves creating sections for each of these settings. For example, I've moved several options into their own sections (and added some new ideas that I haven't yet implemented, too):

GriefPrevention:
  CreeperExplosions:
   BelowSeaLevelWilderness: true
   BelowSeaLevelClaims: false
   AboveSeaLevelWilderness: true
   AboveSeaLevelClaims: false
  WitherExplosions:
   BelowSeaLevelWilderness: true
   BelowSeaLevelClaims: false
   AboveSeaLevelWilderness: true
   AboveSeaLevelClaims: false
  WitherEating:
   BelowSeaLevelWilderness: true
   BelowSeaLevelClaims: false
   AboveSeaLevelWilderness: true
   AboveSeaLevelClaims: false
  TNTExplosions:
   BelowSeaLevelWilderness: true
   BelowSeaLevelClaims: false
   AboveSeaLevelWilderness: true
   AboveSeaLevelClaims: false
  WaterBuckets:
   BelowSeaLevelWilderness: true
   BelowSeaLevelClaims: false
   AboveSeaLevelWilderness: true
   AboveSeaLevelClaims: false

Each of these options now has FAR more granular control. eg; you can now configure it, if you want, to only allow TNT explosions within claims below sea level, or only allow it outside claims above sea level, or allow it outside claims above sea level and inside claims below sea level, or only allow creepers to do damage in claims below sea level, etcetera. Many options will be moved to this form (water and lava placement, primarily). Allowing for, hopefully, very fine-level control over numerous configuration options.

These are also world-specific. Onto that particular implementation. World configurations will be saved/read from Plugins\GriefPreventionData\WorldConfigs\<worldname>.cfg. Some notes:

-It doesn't currently read existing options from config.yml This is because I'm  basically reworking a lot of the options to be more coherent (IMO). As a result I recommend, if there is an existing config.yml file, backing that file up before you run the later dev builds.

World configurations are only read in and created on an as-needed basis. If the configuration file for a world is not found, GP will either create a "new" configuration file using the default settings, or it will create a new set of settings based on the contents of _template.cfg in the same folder. This allows players to create default configurations for worlds that do not yet exist, which can be useful both for standard management tasks as well as dealing with plugins that create worlds.

As with any dev build- and in many ways, more so with this one due to the extent of the changes, there are numerous issues; some chat messages are doubled up (due to the changes I made to logic) as well as some messages no longer being applicable. I will make changes and add messages where they seem to fit, and the configuration options will be changing dramatically over the next while as we work things out.

Last edited May 24, 2013 by BC_Programming