Put this module in the mods folder. If the Core is installed, it will be loaded.
B:enable=true
If this configuration is set to false, None of the permissions created by this module will be checked.
B:enableMobCheck=false
If this configuration is set to true, the permissions controlling mobspawning will take effect. Sometimes the mob-spawn permissions cause extensive ammounts of lag. You have been warned.
The protection module is similar to the ModifyWorld plugin for PEx. it simply adds permissions relating to protection of the world.
| Node | Description |
|---|---|
| ForgeEssentials.Protection.overrideProtection | If allowed, overrides every other Protection permission |
| ForgeEssentials.Protection.allowEdits | Allows the breaking and placing of blocks. |
| ForgeEssentials.Protection.allowBlockInteractions | Allows the usage of blocks such as levers, buttons, and doors |
| ForgeEssentials.Protection.allowEntityInteractions | Allows interacting with mobs in any way. hitting mobs, getting hit by mobs, milking cows, and shearing sheap are all controlled by this permission |
| ForgeEssentials.Protection.pvp | Allows Player vs Player damage |
| ForgeEssentials.Protection.itemUse | Allows using specific items in the world. See below |
| ForgeEssentials.Protection.mobSpawn.natural | Allows the natural spawning of mobs in the world. See below |
| ForgeEssentials.Protection.mobSpawn.forced | Allows the forced spawning of mobs in the world. See below |
ForgeEssentials uses an sophisticated algorithm to search for all existing items in Minecraft as of the start of the server. It compiles a list of all of these items, and converts them into permissions. To make the list of generated permissions more manageable, ForgeEssentials.Protection.itemUse._ALL_ has been registerred than all the variations that have you will learn about below. The names are created in the following format: [source].[block|item].[name|id]
example for vanilla dirt: vanilla.block.dirt
example for BuildCraft DiamondGears : BuildCraft|Core.item.diamondGearItem
Sometimes, the algorithm somehow finds multiple items of the same name, thus numbers are appended to the names in order to keep them unique.
vanilla.item.record
vanilla.item.record1
vanilla.item.record2
vanilla.item.record3
Sometimes, multiples items are scrunched into a single ItemID like in the case of IronChests.
IronChest.block.IronChest Only one name is generated for all the possible types of IronChests there are.
In order to get arround this, the permissions checked for items when they are used is the following.
if the item is registerred: ForgeEssentials.protection.itemUse.[source].[block|item].[name].[#damage|#meta]
if the item somehow evaded registration: ForgeEssentials.protection.itemUse.unknownSource.unknownType.[#id].[#damage|#meta]
if you wish to Allow/Deny all an entire ID. Use the name format. if you wish to deny an ID with a specific damage value, simple add the damage value to the end of the permission as the above format.
IronChest.block.IronChest.0 affects the Iron chest
IronChest.block.IronChest.1 affects the Gold chest
IronChest.block.IronChest.6 affects the Obsidian chest
For your convenience, a list of all the generated names and their equivalent itemIDs can be found in ./ForgeEssentials/UnfreindlyItemList.txt. This file will help you regarding what IDs are mapped to which names and vice versa. It does not however, help you at all when it comes to damage values and meta. For this, it is better to use something like NEI to ascertain the damage values of items. Like all the rest of the permissions, these can be found in ./ForgeEssentials/Permissions/PermissionsList.txt minus the IDs.
NOTE THAT THIS PERMISSION HAS TO BE APPLIED TO PLACE BLOCKS!
Similar to the ItemUse permission, the MobSpawn permission also relies on a list of all the types of mobs. However, unlike the ItemUse list, the MobSpawn list is nearly infallible. Because of this infallibility, a file similar to UnfreindlyItemList.txt is NOT created for mobs, They are only outputted as part of the PermissionsList.txt
format example: [forced|natural].[mobName]
Note that the source of the mob is not included in the permission.
ForgeEssentials.Protection.mobSpawn.natural.Ghast
ForgeEssentials.Protection.mobSpawn.natural.Giant
ForgeEssentials.Protection.mobSpawn.natural.LavaSlime
actual permission examples
Natural spawns are spawns that Minecraft usually does on its own in the world.
Forced spawns are rarely done, but in case they are, a permission exists for them.
As new hooks are added to forge, such as endermen griefing events and creeper explosions, new permissions will be added to stop them.