Links
Tags
Creators
Details
All versions
26.1.X-v1.2.0
Release
tupenter-fabric-26.1.X-v1.2.0last month 8
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client-side
Changes
Scripting:
- list(...) with commas now takes bare words as text - list(short, tall, dry) just works. Variables still win, and in chat text items show gray while computed ones stay aqua
- New name:list parameter type for custom commands - /mycmd list(a | b) or range(1, 5) arrives as a real list for #foreach
- New split(text[, separator]) function - turns text into a list, on spaces or on whatever you pass: split(pairs, "|")
- Script errors now have clickable [edit script] / [edit command] links that open the editor right on that row
Scripts tab:
- Global and world scripts are now one list - each script has a Global/World button to switch where it belongs
- Scripts that won't run (switched off, or the master switch is off) are dimmed
- Editors autocomplete variables, functions and directives like the chat bar does (Tab to accept, Up/Down to pick)
- Expanded editors have a resize handle in the corner
- Scripts that send commands to the server show a small gold ! instead of an extra button
- The tick scripts explanation is now a collapsible section that remembers if you closed it
- /tupenter scripts opens the Scripts tab (the old text status is now /tupenter scripts list)
Chat:
- Lines starting with # (like #stage) are remembered in your up-arrow history after a restart. New setting, on by default
Fixes:
- Tick scripts starting with #silent no longer fail on their first tick
- Typing ( { " $ or redoing in an editor no longer highlights the rest of the text
- The character counter under editors is no longer cut off
Optional dependencies
Any compatible version
Any compatible version
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:4icHwdbL:FjTx2kVF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4icHwdbL:FjTx2kVF"
}

