Tags
Creators
Details
All versions
0.14.0-beta
Beta
Version 0.14.0-beta7 months ago 45
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Any compatible version
Changes
Changelog
As of version 0.14.0-beta, TBCS may only be redistributed under the terms of the MCOML License.
[0.14.0-beta] - 2026-04-01
Added:
- #31 Command argument
asfor thebattlecommand- This argument can follow any entity selector and allows to specify the id of a trainer that should be attached to the entity at the start of the battle
- Using this argument is equivalent to invoking
attachfor the targeted entity, and makes an explicit invocation ofattachobsolete (whileattach+battlestill works usingbattle ... <entity> as <trainerId>is generally adviced) - When used with a player selector (e.g.
@s as <trainerId>) the player will enter the battle with a temporary copy of that trainers team (enjoy setting up puzzles) - When used with another trainer id (e.g.
<trainerId_1> as <trainerId_2>) thentrainerId_2will be attached to the same entitytrainerId_1is currently attached to (if possible)
- #30 Exposed (barebones) API for other mods to register win commands (see
TBCSCommands#getContext()andCommandsContext#registerWinCommands())- All API features are server side only and can be installed with any of the
tbcs-apireleases (i.e. clients do not need to have TBCS installed) - If the regular TBCS mod is installed on a server then
tbcs-apishould not be installed alongside, since TBCS already contains the api (this will require clients to also have TBCS installed) - The API version of the mod does not provide any commands, it does nothing by itself (it only offers functionalities for other mods that may depend on TBCS)
- All API features are server side only and can be installed with any of the
- #29 New command
tbcs reload <trainerId>: Reload a single trainer that was read from a TBCS (trainers) directory only
Changed:
- #28 Update min required version of rctapi to
0.15.0-beta
Fixed:
- #27 Conflict with Cobblemon
1.7.3(ambiguous event handler)
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:NApIzVVy:4ugGuuZK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NApIzVVy:4ugGuuZK"
}

