Links
Tags
Creators
Details
All versions
1.21.6-1.21.8-v1.1.0
Release
tupenter-fabric-1.21.6-1.21.8-v1.1.03 weeks ago 2
Compatibility
Minecraft: Java Edition
1.21.6–1.21.8
Platform
Fabric
Supported environments
Client-side
Changes
New feature: custom lists
- use list() to create a list
- comma separators compute and are for values. Ex: #local my_list = list(1*2, client.pos.y, 8)
- use quotes for strings: list("short_grass", "tall_grass", "dry_grass")
- or use pipes for trimmed strings: list(short_grass | tall_grass | dry_grass)
- list index access works through the existing 0-indexed nth() function
- useful example: /customcommand add cut <r:int=15> = #foreach type in list(short_grass | tall_grass | dry_grass | leaf_litter | bush) (/fill ~$r$ ~$r$ ~$r$ ~-$r$ ~-$r$ ~-$r$ air replace $type$)
- foreach i in (a | b | c) syntax no longer works. Must now use list syntax: foreach i in list(a | b | c)
New feature: comments
- ## <message> creates a comment that isn't sent or processed. The ## must be followed by a spacebar.
New feature: Typed variables:
- #local c:blockpos = blockpos(-10, 20, 85) - very useful for autocomplete (for blockpos, will offer the block you are looking at)
- uses the same keywords a custom command's <name:type> parameters take
Other changes:
- added blockpos(). Snaps a computed position to whole block coordinates. Ex: /setblock $blockpos(raycast(50))$ torch
- pick(a | b) → pick(a, b). Pick now takes commas like every other function, and its options are full expressions that compute
- /tupenter menu, /tupenter menu customcommands, and /tupenter menu scripts add ways to easily access the mod's GUIs
- /tupenter abort now only stops chat run commands, and leaves scripts. Use /tupenter abort all to stop everything
- #pid has existed but did not autocomplete until now - use it to give your command an easily abortable id
- Tupenter plays better with worldedit now - fixed some issues with chaining worledit commands
- fixed screen jumping issue on creating customcommands or removing
- customcommand collapsed/expand status is preserved
- fixed highlighting issues in customcommand multiline textboxes
Optional dependencies
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:o9VA9UZ5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4icHwdbL:o9VA9UZ5"
}



