All versions
1.3.5
Release
Pokebuilder for Cobblemon 1.3.56 months ago 27
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Unavailable version
Unavailable version
Unavailable version
Unavailable version
Unavailable version
Changes
[1.3.5] — 2026-04-16
Changed (security default)
- Bypass permissions are now ignored by default. New config flag
security.allow-bypass-permissions(default false) is the master gate for the entirepokebuilder.bypass.*family (bypass.cost,bypass.cooldown). When the gate is off,TransactionServicetreats those nodes as not-granted no matter what the permission plugin says — defeating the wildcard-grant accident (pokebuilder.*on an admin group) that was silently giving every admin free purchases on cora-on-SYLX and others. - No more "every op gets free purchases" surprise. Fresh installs,
upgrades, and existing configs that don't explicitly set the gate
all default to the safe behavior. Admins who want bypass
functionality flip
security.allow-bypass-permissions = truein config (or via the Security admin GUI panel — new toggle row).
Added
SecurityAdminGuigets the bypass-gate toggle. Click the new wool button to flipallow-bypass-permissionslive without editing config. Toggle is yellow (active = potentially unsafe) when ON, green when OFF (safe default)./pokebuilder debugshows the gate state and effective bypass. Distinguishes betweenperm=true(the permission plugin grants the node) andeffective=true(the gate ALSO allows it, so the bypass actually fires). Two separate lines so admins can see "yes the perm is granted but it's being ignored because the gate is off — which is why purchases are correctly deducting."
Migration notes
- If you were relying on bypass.cost (i.e. you intentionally gave
certain players free purchases via a permission plugin), upgrade
will silently re-enable charging for them. Either:
- Set
security.allow-bypass-permissions = truein config (or toggle in the Security admin GUI) — restores the 1.3.4 behavior for everyone holding the bypass node, OR - Use the Tiers system instead — set a tier multiplier of
0.0for the appropriatepokebuilder.tier.<id>permission. Per-player, audited via the existing tier mechanism, and it doesn't require flipping a server-wide gate.
- Set
- The bypass nodes (
pokebuilder.bypass.cost,.cooldown) themselves are unchanged — same names, same explicit-only resolution. Only the server-side default of whether the node has any effect changed.
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:hUzEOIQX:eoVMJFcs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hUzEOIQX:eoVMJFcs"
}

