1.3.6
Compatibility
Required content
Changes
[1.3.6] — 2026-04-18
Fixed
-
Hidden ability payment broken for some species. The ability selector used position-based detection (
index >= 2) to decide whether an ability was hidden. This failed for any Pokemon with fewer than two normal abilities — the hidden ability landed at index 1, was treated as normal, charged the wrong price, and bypassed theABILITY_HIDDENfeature gate and permission check. Now uses Cobblemon'sHiddenAbilityclass to detect hidden abilities regardless of list position. Normal abilities are always listed first in the GUI, hidden abilities last. -
Tera type changes consumed currency but did not save. The
setTeraTypemodifier passed the tera type's display name toTeraTypes.get(), which performs an ID-based lookup — the name/ID mismatch caused a silent no-op after money was already withdrawn (no refund, no error message). Now passes the resolvedTeraTypeobject directly topokemon.setTeraType(), bypassing the string lookup entirely. Affects all tera types, not just Ice.
Added
-
EV display on Pokemon hover tooltips. The Party selector now shows
EVs: H/A/D/SpA/SpD/Spealongside the existing IV line. The PC selector also gains bothIVsandEVslines (previously showed neither). -
+10 EV per vitamin click. Clicking the vitamin icon in the EV editor header row now adds 10 EVs to that stat. Respects both the per-stat cap (252) and the total EV cap (510). New config price
prices.ev.add-10(default 50). Exposed in the admin Prices panel.
Internal
- New
AbilityEntryrecord incom.antigravity.pokebuilder.servicepairs anAbilityTemplatewith its hidden status. PokemonModifier.flattenAbilitiesTagged()replaces the old position-basedflattenAbilities()(kept as deprecated shim).PokemonModifier.addEv()andtotalEvs()added for +10 logic with dual-cap enforcement.PokemonModifier.setTeraType(Pokemon, TeraType)overload added; string-based overload deprecated.
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:wxBGMuza"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hUzEOIQX:wxBGMuza"
}

