Protection Fields
DOWNLOAD LINK AT BOTTOM OF THE PAGE
How to install (Nothing special)
This plugin allows users to create fields that will protect their land provided they keep placing items in the chest. The shield will continually consume items from the chest/trapchest as power. If the shield doesn't have any power the shield will not protect your land.
Protection
Fields protect against people teleporting inside without permission.
Fields protect against outsiders being able to open chests. (People are able to bypass the Field's blocker with hacks.)
Fields can protect against liquid griefing.
Fields can protect against TNT and Creeper explosions.
Fields DOES NOT YET protect against gravel and sand greif.
The following distances are customisable in the config.yml.
- Iron gives a radius of 9 blocks with 2 extra for glass
- Gold gives a radius of 14 blocks with 2 extra for glass
- Diamond gives a radius of 26 blocks with 2 extra for glass
- Emerald gives a radius of 54 blocks with 2 extra for glass
For the creation and the usage of ProtectionFields, no permission nodes are needed.
Permissions
Permissions
- Fields.* - Fields.whitelisted - Fields.cantCreate - Fields.exemptFromMaxLimit - Fields.exemptFromHomeLimit - Fields.canTogglePassthrough - Fields.canDisplayAll
Permission Description
* //Gives all the commands. The player is treated as an admin and can destroy and build where ever they want. They can also edit other's fields. whitelisted //Puts the users invisibly on the whitelist cantCreate //Prevents a user from making a Field exemptFromMaxLimit //Allows to player to make as many Fields as they want, regardless of what the config.yml has set the max too. canTogglePassthrough //Allows a player to change if the Field should block outsiders from entering, regardless of if the config.yml is preventing players from changing the setting. canDisplayAll //Allows a player to display their whole Field in it's entirety. This is disabled by default since it can cause some lag; Players have the alternative of using /pf display instead of /pf displayAll.
Detailed Creation
ProtectionFields can be created with 5 blocks of either Iron, Gold, Emerald or Diamond.
Field.cantCreate will prevent the user from being able to create the Fields.
Below you can see the different types of Field. The glowing effect on the bottom Fields shows that they are powered.
This is how you create and fuel a Field. Different items have different burn times.
Commands
The main root for commands are
/pf, /protectionfields, /protectionfield, /fields and /field
Player Commands
There are a *lot* more commands than are shown here. Please see the bottom of the config.yml to view them all.
/pf add <playername>
Adds a player to the nearest field.
Note: Only the Owner of the field and Whitelisters can use this.
/pf remove <playername>
Removes a player from the nearest field.
Note: Only the Owner of the field and Whitelisters can use this.
/pf info
Shows the Owner, all the people who have access and the distance to the NEAREST Field.
Admin Commands
/pf whitelist
Lists all the players currently on the whitelist
Note: Whitelist resets upon reload. Note: Whitelist allows a person access to all Fields as their owner.
/pf whitelistadd <playername>
Adds a new player to the whitelist.
Note: Only OPs and people with -Fields.whitelisted can use this command
/pf whitelistremove <playername>
Removes a player from the whitelist.
Note: Only OPs and people with -Fields.whitelisted can use this command
Different Languages
More languages to come. Click the flags to download the specific language packs.
- Download the file
- Unzip the file
- Copy ProtectionFields_Language.txt
- Paste in \plugins\ProtectionFields\
In Progress
- Prepare plugin for 1.13
- Investigate and fix Languages file
- Reduce cpu usage
- Fix bug where other people can get suck inside Field upon creation
- Changable Field fuel consumption in Config file
- Add Fuel whitelist and blacklist
- Add "minimum field creation distance" config option
- Allow the creation of Cubic Fields
- Make Field blocks invisible to other players
- Make videos on how to setup Protection Fields
- Make 1.13 version backwards compatible
- Add a separate permission to use each field type as Fields.[Block] (ex. Fields.coal_block, Fields.gold_block). For use level/rank systems on the server.
- Add plugin to spigotmc.org
To Do
- Prevent sand and gravel greif
- Make water greif protection slightly less unholy
- Add config options for each world.
- Make whitelist persistent so that it stays after reloads
- Make Personal Player Whitelists
- Make possible to add a whole alliance to the shield
- Add option to teleport to other Fields like shops.
Auto-Updating version- Add integration with other protection plugins (Worldguard)
- Allow field painting
Done
- Removing a player from your field moves them outside of the field
- Anyone without permission to enter your field will be teleported back outside (Swimming under water/Hacker/Lag inside)
- New .yaml options Performance Mode replaces all the glass with an invisible block. This should be easier on people's GPU.
- Config option for allowing or disallowing Dropper and Hoppers to fill the center chest
- Field drawing bugfix, possible Worldguard compatability fix
- Added config file for changing the shield creation materials
- Removed this idea. Allow people with access to be able to cut through the glass field if it is up
- Made Field display itself to members who are close by.
- Made a French language pack.
- Fixed bug with Fields not displaying properly after a backup was created
- Add possibility to add multiple languages
- Add config file for changing the shield material distances
- Add config file for changing the power provided by consumed items
- Add command to display shield borders
- Add editable limit for max number of shields per player
- Add infinite power source item, maybe dragon egg
- Make ores/ingots last longer than normal materials along with customisable materials table
- Make glass colour customisable
- Added custom field colours
- Added animated field colours
- Allows the disabling of colour changing and the setting of default colours in config.
- Fixed bug involving multiple worlds and explosions
- Added legacy support to automatically update previous field .dat files
- Made the distance of different block types configurable
- Added automatic config.yml replacer (Custom YML stuff moved to .old file. You will need to manually transfer the config data over.)
- Added scheduled field save feature and made it's duration changeable
- Added a feature to display some of the code's runtime to the console /pf consoleStats
- Added a feature to allow the user to see how long items and stacks burn for. /pf burnTime
- Added MANY variants to the same plugin commands to make things easier for people. (e.g. /pf color and /pf colour)
- Added a configurable limit to the number of fields players can be the owner of.
- Added a way for players to view the full boundaries the shields protects. This privilege can be revoked through permissions.
- Added a way for players to view the boundaries in only a small area around the player. This is for low lag.
- Added a configurable list of blocks that the field's boundaries can replace.
- Added a list of blocks that will provide the field with unlimited power.
- Added the ability to set the default amount of time an item burns for.
- Added the ability to set the time any specific item burns for.
- Added permission nodes to config.yml for convenience.
- Added command to allow outsiders to pass through your field. /pf toggleOutsiderPassthrough
- Added yml setting to set outsider passthrough default value.
- Added permission node for toggling passthrough
- Fixed bug where players warping in would warp into the air regardless of if passthrough was set to true or not.
- Added a list of permission nodes and commands to the end of the plugin.yml
- Added permission node to allow displaying of whole field - Fields.canDisplayAll
- Added small integration with Holographic Displays
- Added config option to disable or enabled the HolographicDisplays plugin integration.
- Fixed a bug where all Field members except owners would be kicked from the Field on reload.
- Added config option to change the Check Boarder Radius that blocks players from entering the Field.
- Fixed a bug where the incorrect Field material would be shown in /pf info when using uncoloured glass.
- Fixed a bug where ender pearls could be used to teleport inside the field. (I thought this wasn't possible)
- Updated to 1.9
- Removed a few deprecated method calls
- Made all fields saved on creation. This will hopefully prevent field structures existing without their functionality due to server crashes.
- Fixed bug where when server ran too fast my code wouldn't display text to say a player had entered a field zone
- Add option to teleport to your home Field.
- Re-design logo.
- Fields now understands that glowing redstone (id 73) and redstone (id 74) are the same type of block.
Soft Requirements
None of the following plugins are required. But ProtectionFields will integrate with them if they are there.
@_Magno20_
Hello Magno,
I expected to have mainly fixed the lag issues.
Please provide all server files in a private PM so that I can examine them myself.
I get lag with this plugin in spigot on there 1.7.10 builds
I see. Yes I had lots of plugins before. I deleted server and recreated it. With some new, and some old plugins. Server is latest posible version 1.7.9 (now). I also use core protect, os maybe that is a problem? As core protect creates block log. Anyway, I have now about 15-20 plugins. I am planing to remove 1. BEFORE I had 40+ plugins. I will try to download latest version avaible. Plugin is realy awesome, great plugin to prevent survival grief, and without any moderators around. But please could you also make disabled world guard Regions or worlds? Like in my plot world, if player creates emerald Beacon, others won't be able to pass. Or in my survival City. I don't want people to be able in specific world guard Regions create beacons and claim builds they didn't build. Thanks.
Otherwise, fantastic plugin. To bad there isn't a DONATE button ;)
@WarMage100
I thought I fixed all the lag issues and only got lag with about 20 overlapping Fields.
When someone creates a Field there definitely shouldn't be a crash. Do you get any error messages from PF in console?
I went onto your server and it seems you have a lot of plugins installed, perhaps there is a conflicting plugin. What bukkit version are you using?
@MrMaggott
Thanks for the feedback,
A Field should never disappear on it's own accord, occasionally the Field may not be active due to lack of food. You can check the distance to the nearest field by using /pf info to see if it really has gone poof.
Upon shutdown/restarts all Fields are stored in ProtectionFields_Fieldlist.dat and on startup are loaded from the same file. A server crash could leave the file in it's previous state (perhaps in this case empty) and only old (none) fields would be loaded.
I have just checked and can guarantee that the latest download doesn't have that problem with Bukkit 1.4 1.7.9R0.3
ok working. I pasted it accidenly in wrong folder. Now problem is, that when someone creates a field, server crashes. And is so laggy with fields instaled. PLease fix this.
Hey can you help me! I put the plugin jar into plugins folder, but when I type /plugins it isn't on the list. Do I need other plugin to make this work? Thanks! Or I have a plugin this 1 isn't working with. Thanks.
IP: EnderGamesServer.mcph.co
This is a powerfull and great plugin, and I will definitely use it on my server. I have had players trying for hours to get through, but they can't! Great work! I only have one thing against it. When the server makes a restart, the forcefield is gone! Is it possible to make it resume somehow?