Flags - ShaneBeee/GriefPreventionFlags GitHub Wiki

If in the config "PvP Only In PvP-Flagged Claims" is set to true, PvP will be off in the world, and you can then add a flag to a claim to allow PvP in specific claims. There is also an optional message to be sent to players when they enter these claims (can be changed in the config)

--- CURRENTLY BROKEN IN 1.15+ ---
You can now change the biome in claims. You can also give players permissions to set flags, and they can change the biomes in their own claims.

When you are using the command to set a biome on 1.13+, it will give you a scrollable list of available biomes. On 1.12.2 and below, just hit tab, and it'll show you a list of all the biomes. Make sure to type them in exactly.

I added a list of blacklisted biomes to the config so you can stop players from using certain biomes. By default, I added the mushroom island biomes because, as monsters spawn on mushroom islands, which could give the player a slight advantage. You can add more biomes to this list or you can remove the biomes. If you remove all of the biomes, make sure to add at least null or it'll reset with the defaults. You need to use the BukkitAPI names for biomes, which can be found here: 1.12.2 or below and 1.13.2+
Players with the permission gpflags.bypass will be able to bypass the blacklisted biomes. Config Example (snipped out other config options just to show you how it looks)

World Flags:
  world:
    Biomes:
      Blacklist:
      - MUSHROOM_FIELDS
      - MUSHROOM_FIELD_SHORE
      - NETHER

When a claim is deleted or a ChangeBiome flag is unset, the biome will revert back to it's previous state to make sure your world stays looking clean. This will prevent players from running around the world, claiming land, changing the biome, abandoning the claim, and making your world look patchy. Just a side note, I didn't want to save a bunch of "previous" biomes in a config, so rather when the biome resets, it takes the biome from the block 2 north of the claim. So beware that this might sometimes still look a tiny bit patchy depending on the boundaries of the claim.

Blacklist commands. Prevents players from using any commands you list in the flagged area, unless they have the gpflags.bypass permission.
Example usage: /SetFlag CommandBlackList sethome;setwarp;kit

Whitelist commands. The flag prevents players from using any commands except those you list in the flagged area, unless they have the gpflags.bypass permission.
Example usage: /SetFlag CommandWhiteList tell;me;home

Prevents players levels dropping when they die in this area

Runs a console command when the player enters this area (Variables: %owner% = Owner of claim in flag, %name% = player in event, %uuid% = uuid of player in event) For multiple commands, separate with a semicolon (;) (make sure to not have spaces after the semi colon)

Runs a console command when the owner of this claim enters the claim (Variables: %name% = player in event, %uuid% = uuid of player in event) For multiple commands, separate with a semicolon (;) (make sure to not have spaces after the semi colon)

Runs a console command when a member of this claim enters the claim (Variables: %name% = player in event, %uuid% = uuid of player in event) For multiple commands, separate with a semicolon (;) (make sure to not have spaces after the semi colon)

The same as the EnterCommand flag, except this one will run commands from a player vs from console. (Variables: %owner% = Owner of claim in flag, %name% = player in event, %uuid% = uuid of player in event) For multiple commands, separate with a semicolon (;) (make sure to not have spaces after the semi colon)

Sends a message to the player when they enter this area (Variables: %owner% = Owner of claim in flag, %name% = player in event)

Runs a console command when a player exits this area (Variables: %owner% = Owner of claim in flag, %name% = player in event, %uuid% = uuid of player in event) For multiple commands, separate with a semicolon (;) (make sure to not have spaces after the semi colon)

Runs a console command when the owner of this claim exits the claim (Variables: %name% = player in event, %uuid% = uuid of player in event) For multiple commands, separate with a semicolon (;) (make sure to not have spaces after the semi colon)

Runs a console command when a member of this claim exits the claim (Variables: %name% = player in event, %uuid% = uuid of player in event) For multiple commands, separate with a semicolon (;) (make sure to not have spaces after the semi colon)

Same as ExitCommand except this will run the command from player vs from console (Variables: %owner% = Owner of claim in flag, %name% = player in event, %uuid% = uuid of player in event) For multiple commands, separate with a semicolon (;) (make sure to not have spaces after the semi colon)

Sends a message to the player when they leave this area (Variables: %owner% = Owner of claim in flag, %name% = player in event)

Health is regenerated when the player is in this area

info coming soon

A player will keep their inventory if they die in this area

Executes console command when entering a Portal. Runs one or more console commands when a player steps through a nether portal in the flagged area. Use %name% or %uuid% placeholders to target the player stepping through the portal, and separate multiple command lines with semicolons [;]. If your in-game command entry box is too short for all your commands, consider backing-up your flags.yml file and then modifying it with a text editor to get more command lines in for a single portal, then using /GPFReload to load your edited file. Example usage: /SetFlag NetherPortalConsoleCommand tp %name% 0, 65, 0;xp 10L %name%

Executes player command when entering a Portal. Causes any players who walk into a nether portal in the area where the flag is applied to automatically run a command line instead of teleporting (it runs as the player, not as a console command). Helpful to give players a /home portal or random wilderness teleport portal, for example.

Prevents players from teleporting when they eat chorus fruit in this area

Clears drops on entity death. When a mob (except for players) dies in an area with this flag active, no loot will drop. Using this, you can create combat challenges where players can keep their inventories and experience (with other flags above), but prevent players from abusing those flags to farm loot. Player death loot is controlled by the above KeepInventory flag.

Prevents players from using elytra

Prevents players from teleporting when they throw an ender pearl in this area

Prevents all players from entering this area

Blocks specific players from entering this area

Disables claim expiration.

Disables damage caused by explosions (ie: creepers & tnt)

Prevents players from taking fall damage in this area

Prevent fire from damaging blocks in this area
Requires FireDamage in the GP config to be enabled!

Prevent fire from spreading in this area
Requires FireSpread in the GP config to be enabled!

Prevents players from flying in this area

Prevents fluid from flowing in this area

Stop plants from growing (crops) and blocks from spreading (podzol, grass, seagrass, kelp) in this area

Prevents players from starving in this area

Stops ice from forming in this area

Prevents player's items from taking durability hits

Prevents players from dropping items in this area

Prevents players from picking up items in this area

Prevents leaves from decaying in this area

Disables loot protection on player death. Disables GriefPrevention's player death loot "anti-theft" feature in the flagged area, allowing any player to pick up the items a player drops when he or she dies in that area. Useful for competitive areas where loot can be a reward, like PvP arenas.

Disables McMMO death penalty - cancels McMMODeathPenalties when a player dies in a flagged area.

Prevents mcMMO skill usage (activated skills, secondary skills, disarms, etc) in the flagged area. You might use this to create PvE challenge areas or specialized PvP arenas where mcMMO won't give some players an advantage over others.

Disables McMMO experience gaining in the claim.

Prevents mob damage in this area. This does not affect players, this will only prevent entities damaging passive mobs. (ex: wolves cant hurt sheep)

Prevents ALL mobs from spawning in this area, good or bad!

Prevents specific types of mobs from spawning in this area. Can support multiple types.
Must use Spigot EntityType enums.
To add multiple types, separate with a semi-colon ;
Example usage:
/setclaimflag NoMobSpawnsType creeper;cow;zombie;wandering_trader;phantom
Permissions for this flag are per mob type, examples:

- gpflags.nomobspawnstype.cow
- gpflags.nomobspawnstype.sheep
- gpflags.nomobspawnstype.* <-- wild card for all mob types

Prevents all bad mobs from spawning in this area, and will also prevent them from entering the area. If they do, they will be removed.

Prevents all bad mobs from spawning in this area. If they spawn outside of the area, they will be able to walk in.

Prevents players from opening doors/gates/trapdoors in a claim. This flag will follow GP's permissions, meaning an owner and a member with access trust or higher will be able to open doors.
Supports parameters (doors, trapdoors, gates), to use multiple parameters, separate with a comma.

Prevents players damaging pets in this area

Prevents players taking any damage in this area

Prevents players taking damage by monsters in this area

Prevents snow from forming in this area

Stops players from placing vehicles (boats/minecarts) in claims

Stops vines from growing in this area

Disables weather change - prevents weather from changing in a world, even by operators using commands. If you change your mind about the weather in a world, you have to first disable the flag, then change the weather, then re-enable the flag. You should use this only with /setserverflag or /setworldflag, because it has no effect on individual land claims or subdivisions. Note: If you lock the weather during a thunderstorm, it will never end. If you lock the weather when there is no thunder, a storm will never come.

Allows an owner of a claim to fly within their own claim

Allows owners of the claim and members with access trust or higher to fly within the claim

You can set the time in a claim for a player. When the player enters, their time will be set to one of the 4 options. When they leave the claim, it will reset to match world time. [/setclaimflag playertime <day/noon/night/midnight>]

You can set the weather a player will see when they enter a claim. This is client side and will not affect the rest of the world [/setclaimflag playerweather <sun/rain> (thunderstorms are not supported)

This will protect mobs which have a name (ie: using a name tag or via commands). Player's with container trust will still be able to harm/kill said mob, but visitors to your claim will not be able to harm them.

Prevent non-members of claims from triggering raids. (This may be a temporary flag if GP decides to put something directly in GP)

Sets spawn location for the claim (Useful for PvP arenas). Overrides the usual respawn rules to respawn the player in a specific location who dies in the flagged area. For example, consider respawning a player at the beginning of a parkour challenge or just outside a pvp arena. You may optionally specify pitch and yaw (facing direction) as well. Example usages: /SetFlag RespawnLocation world 112.5 68 265.5 or /SetFlag RespawnLocation world 112.5 68 265.5 90 45

Complex flag to create spleef arenas. SpleefArena - Completely automates a Spleef minigame (players compete to remove blocks out from under each other until someone falls) in the flagged area. Example usage: /SetFlag SpleefArena minecraft:snow_block minecraft:bricks 20 The above example will generate a snow block (minecraft:snow_block) 20 blocks above every bricks block (minecraft:bricks) in the flagged area every time a player dies in the flagged area. It will also allow ONLY snow blocks to be broken by any player even without build permission, and won't drop those blocks as items when they're broken. To set up a spleef arena, first flag the claim or subdivision as shown above. Then dig down underneath where the breakable arena surface (snow block in the above example) will be and use your marker blocks (bricks in the above example) to indicate the shape of your arena, which does NOT have to be flat, rectangular, or single-block thick. The y offset (the last flag parameter) dictates how far down you have to place the marker blocks from where you want the arena surface to generate. To test your settings, use the Vanilla /kill command while standing in the flagged area. Your death will trigger the arena surface to be built per your specifications.

Sets trapped destination for the claim (Useful for admin claims). Allows players to use GriefPrevention's /trapped command in administrative land claims by specifying where the player will go when he gets "unstuck". Ordinarily, administrative land claims don't allow players to use the command at all.