Anti-Griefing Update! 8/15/16

It's here! The anti-griefing update is LIVE!

Please note that this system isn't perfect, but is as close as we could get with the logistics involved. This update is simply meant to protect players against major destruction and is not a full blown protection system. Outposts (Residence in the Frontier) will be the full protection system in the future.


EMC's anti-griefing system is designed to prevent griefers from breaking blocks without the owner's permission. If someone does try to break a player's block without permission, the block will be protected, and they will receive an error. The anti-griefing system is available in the Frontier and Wastelands (with limits) worlds. To learn about Town's separate protection system, see the Residences page.

How do I protect my blocks?

Most decorative blocks and tile entity blocks (e.g. paintings) are always protected. However, common blocks like Dirt, Cobblestone and sand are not protected by default when placed by a player.

If you are building and you want to ensure that your common blocks are protected if they are part of your build, then please enable Build Mode. To toggle Build Mode on and off, use the command/buildmode. It is default off every time you log in.

Any blocks which you place while you have Build Mode enabled are automatically protected. Note: liquids (lava and water) as well as crops are not protected. You should only enable Build Mode when you are building outposts or other structures - if you're mining or traveling between areas, please do not enable it (disable it if you enabled it) - otherwise you'll be unintentionally making it harder for other players to mine and travel in those areas.

NOTICE: Build mode is not usable in the Wastelands, as you should not be creating permanent structures there. However, the uncommon blocks, including the decorative and high-value items, will inherit the default protection status to protect them from being griefed. If you must build a temporary structure in the Wastelands, use uncommon blocks.

What are my blocks protected from?

Blocks which you place while in build mode cannot be broken by players who do not have your permission, TNT, nor creeper explosions. However, if you want to prevent players taking items out of containers such as chests, you still need to lock them with a lock sign (learn more about these on the Feature Signs page). Other players aren't able to use lock signs on containers which you place while in Build Mode. Players are still able to use items placed in build mode - for example, they're able to open and close doors. Animals you spawn using spawn eggs aren't protected.

Are there exceptions to the protection?

Liquids, crops, and physics affected entities are not protected, even if placed while in Build Mode. This includes sugar cane, lilypads, water, lava, potatoes, etc.

Containers are NOT protected from being opened under the Anti-Griefing update. In order to adequately protect the contents of a container, you MUST use lock signs.

Who can break my protected blocks?

By default, your protected blocks can be broken by your friends (learn about this on the Friends System wiki page), people currently in a group with you and people you or your friends have vouched for. If you would like to restrict who is able to break your blocks further, you can do so in the anti-grief section of /settings. If you would like to completely disable group members from breaking each others blocks as a result of being in the same group of each other and you are the leader of the group, use /gr blockbreak.

How do vouches work?

A vouch is a way of giving someone temporary permission to break your or one of your friends' protected blocks. Each vouch lasts 30 minutes, but will expire early if you vouch on behalf of a friend who is offline and that friend connects to the SMP or the person who you are vouching for disconnects from the SMP. You cannot vouch on behalf of friends who are currently online (They can control their own vouches).

• To vouch for someone to break your blocks, use /vouch [player name]
• To vouch for someone to break one of your friend's blocks, use /vouch [player name] [friend's name]. You can only do this if they haven't disabled friend vouches in their player settings.

It is against EMC rules to vouch for someone on behalf of a friend with the knowledge that they intend to grief that friend's builds, and will be dealt with as such. Vouches are logged for Staff reference.

Am I allowed to break unprotected blocks that were placed by another player?

No. Griefing is still against EMC's rules. If it was obviously player built, leave it alone! The system is here to prevent you from doing something you're not supposed to and covers 95% of the issues. If you find a corner case that goes around the system, that does not mean it is ok and you will be punished.

Policies in effect as of this update:

New SS service.
Frontier Block Protections
10,ooo rupees per protection selection. Cap of 50,000 per player per area. No discounts.

Have a base in the Frontier that you built out of common blocks and is not protected by the Antigrief system currently? Don't want to dig it all up and replace it with Build Mode active in order to protect it? Senior Staff will set protections for your build without the hard labor on your part.
To request: FILL OUT THIS FORM
SS will be handling Established outpost protections FIRST, then will handle the non-established. Requests will be in first-come-first-serve manner with exception of the previous comment.

Requirements:

• Established outpost protection MUST be requested by the owner of the outpost. They may request that we protect on behalf of someone else though. This is to be used in the case of each player having a 'plot' to build on, etc in the outpost.
• Selections will be limited by the view-able structures in the area. We are not going to protect all 50,000 blocks surrounding and below your outpost.

Griefing by Build Mode Block Placement
This is not new, but needs to be clarified with the release of this update. Griefing is the act of irritating and angering people in video games through the use of destruction, construction, or social engineering. Griefing a player's build by placing blocks with build mode on maliciously will be dealt with as such. If you shouldn't be building there, then don't.

Please Do NOT Report Attempted Griefings
If someone is trying to break your blocks, but they are protected, then there is no cause for concern. The system will do its job and protect your blocks, as it should. Please do not spam our report logs because someone is trying to break your blocks, but the system is stopping them. The logs won't show it and we will not be able to take action.
If they find a way around the protection and actually break/steal something, then please report that.

Block Protection List: Non-Build Mode
For a long time, we kept what was and wasn't logged in our Potential Grief system private in order to protect the players from having griefers find a way around the system and break blocks that we were not tracking. However, with the release of this new build mode, a player could easily put this list together by just testing each block individually and seeing what the system stopped them from breaking. Therefore, due to that and the need for players to see what is default protected when building, we are releasing our list of uncommon blocks which are protected (if placed by a player). This list is subject to change, if deemed appropriate by the Staff.

Blocks placed after May 1st, 2014 will have protection built in if the block is on the following list.

- ACACIA_STAIRS

- ANVIL

- BEACON

- BED

- BED_BLOCK

- BIRCH_WOOD_STAIRS

- BOOKSHELF

- BREWING_STAND

- CARPET

- CAULDRON

- CHEST

- COBBLE_WALL

- DAYLIGHT_DETECTOR

- DETECTOR_RAIL

- GOLD_BLOCK

- DIAMOND_BLOCK

- DIAMOND_ORE

- DIODE (repeater)

- DISPENSER

- DOUBLE_STEP

- DROPPER

- EMERALD_BLOCK

- EMERALD_ORE

- ENCHANTMENT_TABLE

- ENDER_CHEST

- FENCE_GATE

- FENCE

- FLOWER_POT

- FURNACE

- GLASS

- HOPPER

- ICE

- IRON_FENCE

- IRON_BLOCK

- IRON_DOOR

- IRON_DOOR_BLOCK

- IRON_PLATE

- ITEM_FRAME

- JUKEBOX

- LADDER

- LAPIS_BLOCK

- MOSSY_COBBLESTONE

- NETHER_FENCE

- NOTE_BLOCK

- OBSIDIAN

- PAINTING

- PACKED_ICE

- PISTON_BASE

- PISTON_STICKY_BASE

- POWERED_RAIL

- QUARTZ

- QUARTZ_BLOCK

- QUARTZ_STAIRS

- RAILS

- REDSTONE_BLOCK

- REDSTONE_COMPARATOR

- REDSTONE_COMPARATOR_OFF

- REDSTONE_LAMP_OFF

- REDSTONE_LAMP_ON

- REDSTONE_TORCH_ON

- REDSTONE_TORCH_OFF

- SANDSTONE_STAIRS

- SEA_LANTERN

- SIGN

- SIGN_POST

- SKULL

- SMOOTH_BRICK

- SMOOTH_STAIRS

- SPRUCE_WOOD_STAIRS

- STEP

- STAINED_GLASS

- STAINED_GLASS_PANE

- STONE_BUTTON

- STONE_PLATE

- THIN_GLASS

- TRAP_DOOR

- TRAPPED_CHEST

- TNT

- TRIPWIRE

- TRIPWIRE_HOOK

- WALL_SIGN

- WOOD_BUTTON

- WOOD_DOOR

- WOOD_DOUBLE_STEP

- WOOD_PLATE

- WOOD_STAIRS

- WOODEN_DOOR

- WOOL

- HAY_BLOCK

- WORKBENCH

- COBBLESTONE_STAIRS

- JACK_O_LANTERN

- IRON_TRAPDOOR

- ACACIA_DOOR

- SPRUCE_DOOR

- BIRCH_DOOR

- JUNGLE_DOOR

- DARK_OAK_DOOR

- SPRUCE_FENCE_GATE

- SPRUCE_FENCE

- BIRCH_FENCE_GATE

- BIRCH_FENCE

- JUNGLE_FENCE_GATE

- JUNGLE_FENCE

- DARK_OAK_FENCE_GATE

- DARK_OAK_FENCE

- ACACIA_FENCE_GATE

- ACACIA_FENCE

- SLIME_BLOCK

- ARMOR_STAND

- BANNER

- POLISHED_DIORITE

- POLISHED_GRANITE

- POLISHED_ANDESITE

Commands Summary for this update:
Parameters in [ ] are optional
Parameters in < > are required

• /buildmode [on|off|true|false]
  • Enables or disables build mode
  • If a value is not provided, it toggles the current state
  • Any blocks you place in the Frontier (Wild/Nether/End) (NOT wastelands/town) are protected when in build mode
• /noprotectmode [on|off|true|false]
  • Will ensure no placed blocks are protected
• /vouch <for> [on behalf of]

• • Gives the for(C) player permission to break the on behalf of player's(A) blocks for 30 minutes
  • If an on behalf of player(A) is not provided, the person who used the command is used (B - self)
  • Mods can vouch on behalf of anyone if there is valid reason
  • Players can only vouch on behalf of their friends
  • Players cannot vouch on behalf of a friend if that friend is currently online
  • Vouches expire after 30 minutes
  • Vouches expire instantly if the on behalf of player comes online

• /unvouch <for> [on behalf of]
  • Removes your vouch on the for player mentioned to break the on behalf of player's blocks

• /gr blockbreak
  • Only usable when you're in a group
  • Toggles whether or not members of a group are able to bypass the protection for eachother's blocks

• /ps -> Anti Grief section
  • Allow Group Members - controls whether or not the group blockbreak setting works on you. If false, group members can't break your blocks even if group blockbreak is set to true
  • Allow Friends - controls whether or not your friends can break your protected blocks
  • Allow Friends To Vouch - controls whether or not your friends can vouch for people to be able to break your blocks when you're offline

• /f blockbreak <name> [on|off]
  • Toggles whether or not that specific friend is able to break your blocks
  • Overrides the player setting "Allow Friends"

• /clearblockprotection [filterWhoToRemove] [MOD+ ONLY]
  • After confirmation, removes the protection of the blocks which are currently in your WorldEdit selection
    Pass in an optional player name to only clear a certain players protected blocks

• /listprotection [filterListToOnlyPlayer] [MOD+ ONLY]
  • Lists the protected blocks in your WorldEdit selection. The number in ( ) after each block name is the amount of that block.
  • Pass in an optional player name to only show a certain players protected blocks

• /addprotection <owner> [overwrite] [SS+ ONLY]
  • Set owner of blocks. Unless overwrite is passed in as true, will not change owner of existing blocks

Oh yeah!

Awesome update ^_^ Will make my job easier