Overview
Adds the ability to retain and create grass paths under fence gates, whether the gate was placed before or after the path.
Shiny and new for version 1.16.3/1.16.4/1.16.5.
You can create a whitelist to add blocks that allow paths under them for custom gates from other mods. You can also add blocks to a blacklist to remove this ability. The blacklist is intended for vanilla gates if desired and mods that extend the fence gate block but shouldn't be able to have a path under them.
White/Blacklist formatting
Format is of the form
modid:name:properties
Name may be the wildcard operator *. If no name is specified, it is the same as having name being a wildcard.
Not all properties of a block must be defined, the white/blacklists will match against any properties defined but will ignore those that aren't. Properties are separated , with each property being a key-value pair of the format key=value. The properties may also be the wildcard operator *. If no properties are defined it is the same as them being a wildcard.
If modid is defined as ore, vanilla and Forge tags will be matched against, where name will be a tag path. If a mod uses it's own tag namespace, that must be specified as the modid to match properly. The path portion of the tag is specified as the name. Properties do not apply in this case, and using them will cause a failure to match a tag.
When only modid and name are defined, tags will attempt to be matched against first. Failing that, the entry will try to be matched to a block instead.
Example entries include:
"minecraft:*"— all blocks in theminecraftdomain"minecraft"— all blocks in theminecraftdomain"minecraft:stone"— matchesminecraft:stone"minecraft:jungle_log"— allminecraft:jungle_logvarieties"minecraft:jungle_log:*"— allminecraft:jungle_logvarieties"minecraft:jungle_log:axis=x"— allminecraft:jungle_logvarieties with the propertyaxis=xother properties ignored"minecraft:oak_stairs:facing=east"— allminecraft:oak_stairsvarieties with the propertyfacing=eastother properties ignored"minecraft:oak_stairs:half=top"— allminecraft:oak_stairsvarieties with the propertyhalf=topother properties ignored"minecraft:oak_stairs:facing=east,half=top"— allminecraft:oak_stairsvarieties with the propertiesfacing=eastandhalf=topother properties ignored"ore:spruce_logs"— all blocks under thespruce_logsvanilla tag"ore:fences/wooden"— all blocks under thefences/woodenForge tag"minecraft:logs"— all blocks under thelogsvanilla tag (this is a tag, though it looks like a block)
Note: Entries require double quotes surrounding them. Failing to do so will cause a crash.
Final Note: If you still need more help with blocks, see the CraftTweaker wiki for version 1.12. The formatting is almost a one-to-one mapping of Bracket Handlers from that mod.
1.12.2 version
Overview
Adds the ability to retain and create grass paths under fence gates, whether the gate was placed before or after the path.
Version 3.0.0 overhauls underlying systems to be more like 1.6.4/1.6.5 so that the mod can now be used server-side only if desired.
You can create a whitelist to add blocks that allow paths under them for custom gates from other mods. You can also add blocks to a blacklist to remove this ability. The blacklist is intended for vanilla gates if desired and mods that extend the fence gate block but shouldn't be able to have a path under them.
White/Blacklist formatting
Format is of the form
modid:name:properties
Name may be the wildcard operator *. If no name is specified, it is the same as having name being a wildcard.
Not all properties of a block must be defined, the white/blacklists will match against any properties defined but will ignore those that aren't. Properties are separated , with each property being a key-value pair of the format key=value. The properties may also be the wildcard operator *. If no properties are defined it is the same as them being a wildcard. Properties may also be a meta value, as an integer, that defines a blockstate.
If modid is defined as ore, the ore dictionary matched against, where name will be a label in the ore dictionary. Properties do not apply in this case.
Note: Entries in the ore dictionary are parsed differently than those used by this mod. This is due to how ore dictionary entries are accessed in Forge. There is no way to differentiate between, for example, <minecraft:log>, <minecraft:log:0>, or <minecraft:log:variant=oak,axis=y>. This means they often have overly specific meta values that map to a single blockstate (unless they've got a wildcard for a meta value).
Example entries include:
minecraft:*— all blocks in theminecraftdomainminecraft— all blocks in theminecraftdomainminecraft:glass— allminecraft:glassvarietiesminecraft:stone— allminecraft:stonevarietiesminecraft:stone:*— allminecraft:stonevarietiesminecraft:stone:variant=granite— allminecraft:stonevarieties with the propertyvariant=graniteother properties ignoredminecraft:oak_stairs:facing=east— allminecraft:oak_stairsvarieties with the propertyfacing=eastother properties ignoredminecraft:oak_stairs:half=top— allminecraft:oak_stairsvarieties with the propertyhalf=topother properties ignoredminecraft:oak_stairs:facing=east,half=top— allminecraft:oak_stairsvarieties with the propertiesfacing=eastandhalf=topother properties ignoredminecraft:log:0—minecraft:logwith meta value0resolves tominecraft:log:variant=oak,axis=yore:woodLog— all blocks under thewoodLogore dictionary entry
Final Note: If you still need more help, see the CraftTweaker wiki for version 1.12. The formatting is almost a one-to-one mapping of Bracket Handlers from that mod.