Tags
Creators
Details
mc26.2-1.1.0+neoforge
Compatibility
Changes
New
- Added NeoForge support alongside Fabric, with separate downloads for each loader and Minecraft version.
NeoForge does not support Placeholder API. The existing server-side Placeholder API integration remains available on Fabric.
Fixes and improvements
- Fixed server-side execution of custom commands and redirects. (#38)
- Fixed aliases failing to find commands that include arguments, such as
gamemode survival,trigger bid set, or a specificfunctioncommand. (#59, #67, #80) - Fixed errors when enabling MySQL storage, including failures when creating the database tables. (#50)
- Improved database connection handling, reconnection, and cleanup when leaving a game or stopping a server.
- Fixed conflicting bundled libraries that could prevent Minecraft from starting.
- Improved error messages and loading logs to make problems with alias files easier to identify.
Fixes brought to older Minecraft versions
- 1.21.1: Included the client custom-command fix previously released for newer Minecraft versions. Server actions are sent to the server without the reported client crash, and client actions execute instead of being printed in chat. (#65)
- 1.21.1: Included earlier improvements to redirects for modded commands, such as WorldEdit, and corrected player-world lookup with
$get_world(). (#73, #77) - 1.21.1, 1.21.11, and 26.1.2: Included improved execution ordering for custom commands with multiple actions and conditional follow-up actions. This improvement was already available on 26.2 and 26.3. (#51)
Documentation
- Updated project and in-game help links to the new Command Aliases wiki. (#78)
- Added a clearer COMMAND_LIST_LOOKUP guide explaining how to reuse another command's tab-completion suggestions. (#61)
Notes for database users
- If the configured database cannot be opened, Command Aliases now logs a warning and uses temporary in-memory storage. Values stored in this fallback are not saved between sessions.
- MySQL tables are updated automatically when needed. The configured database account must have permission to update the table structure.
Full Changelog: https://github.com/FlashyReese/CommandAliases/compare/mc26.2-1.0.4...mc26.2-1.1.0
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:dHTBnV1v:sVLETbYo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dHTBnV1v:sVLETbYo"
}

