
SimpleTMs: TMs and TRs for Cobblemon
This Minecraft mod is an expansion to the Cobblemon mod, integrating TMs (Technical Machines) and TRs (Technical Records) from the Pokémon universe. The mod allows players to teach moves to their Pokémon, with either a TM or TR.
Tags
Creators
Details
2.3.0
Compatibility
Required content
Changes
v2.3.0 Changelog
New Features
TM/TR Cases & TM Machine
New storage items for organizing your move collection.
TM Case & TR Case
- Store all your TMs (1 each) or TRs (stackable) in a single portable item
- Personal storage like an ender chest - your items persist even if the case is lost or destroyed
- Tooltip tracks your collection progress (e.g., "127/Pokemon TMs stored")
TM Machine
- Placeable block with shared storage accessible by all players
- Combines TM and TR storage in one interface
- Works like a regular chest - items belong to whoever takes them
Shared UI Features
- Ghost previews of all available moves so you can see what's missing at a glance
- Search by move name, or use tags like
#fire,#physical,#special - Filter toggle: switch between All / Stored / Missing views
- Pokémon filter: show only moves a specific Pokémon can learn
- Shift+click the filter button to select from your party
- Or use the case directly on one of your Pokémon, or shift use the TM/TR case item to select.
- Your last selected Pokémon stays available as a quick filter option
Other Changes
- Loot tables now use injection for better mod compatibility (Cobblemon, PokeLoot, Cobblemon Additions)
- Removed unavailable moves: Shed Tail, Night Daze, V-create
- Added translations: German, Spanish, French, Korean, Brazilian Portuguese, Simplified Chinese
- Recycling recipes added: Craft any 4 TMs together (2×2) to get a Blank TM. Same for TRs. Useful for clearing out duplicates or unwanted moves.
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:yFqR0DNc:29UCYRJS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yFqR0DNc:29UCYRJS"
}
