Tags
Creators
Details
Licensed ARR
Published 10 months ago
Updated 2 months ago
All versions
1.0.1
Release
Cobblemon Fence 1.0.19 months ago 7,607
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
- Flipped the texture from upside down to the intended way.
- Code restructure.
- Now has correct break texture particles.
- Better placement in flowing water (still not perfect).
- Stopped the fences from showing up on the minimap.
- Nothing should spawn inside the fence blocks anymore.
- Added Player and Pokémon only pressure plates.
- The Player plates are exactly the same as normal plates except only players can trigger them. All vanilla wooden, stone, and weighted pressure plates are included. There are also the Cobblemon, Cobblemon Distortion World, and Pale Oak pressure plates as well.
- The Pokémon version only has one pressure plate to choose from.
- All but one of the player pressure plates are made by combining a Pokémon Fence and the pressure plate of your choosing. The Pale Oak pressure plate is made by using white carpet and a Pokémon Fence.
- The Pokémon Pressure Plate is made by putting a Pokémon Fence in the crafting grid.
- If you do not have the Cobblemon Distortion World mod installed the pressure plate will be craftable with blue carpet.
- The Pokémon Fence Detector allows you to hover over the pressure plates to see what type they are. If they are normal it displays nothing.
- Added a warning message if you try to place something where a Pokémon Fence is.
- The Pokémon Fence now will phase in and out when coming closer or going farther from it.
- The Pokémon Fence can now be seen in water.
- Mobs should have better path finding with the Pokémon Fence
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:aCQFwusS:ztAK8jdM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aCQFwusS:ztAK8jdM"
}

