Tags
Creators
Details
All versions
0.4.11
Release
v0.4.112 years ago 138
Uploaded by
Compatibility
Minecraft: Java Edition
1.8.9
Platform
Forge
Supported environments
Client-side
Changes
New Features:
All secrets display (Finally)
- Render a box (WITHOUT ROUTES) on all secrets/levers in the room
- Includes secrets that aren't in the main route
- Removes the secret upon interact (TODO: Make toggleable)
Locked chest detection
- Detects when a chest is locked after interact
- Displays waypoint to the lever of the chest
- Disapears once you interact with the lever
- Displays a message on your screen
Dungeon Boss Message Hider
- Hides Dungeon boss messages
- Toggle each boss individually
- Does not interfere with any other mods that use boss messages
Blood filled notification
- Display a custom text when all blood mobs have spawned
- Custom position, color, and duration
Tab autocomplete
- Added tab autocomplete to most of the commands
WIP features (under Dev in the config)
- Player to next waypoint -> Renders a straight line from the player to the next secret waypoint in the room
- Uses normal line settings
- Doesn't include etherwarps, mines, lever interacts, or superbooms
Dev features
Debug commands
- Added some lever debug commands (will probably throw errors if used incorrectly)
- Returns relative and absolute pos, chest name, lever name, and number
- Added a pos option to print current position, and relative pos inside dungeons
- Added bloodtime option to temporarily display the blood filled text
Bugfixes
No bugs reported
Github download link: Secret routes v0.4.11
Join the discord
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| SecretRoutes-0.4.11.zip | Unknown | 8.74 MiB |
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:l1qibtk8:8wtcMkCf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:l1qibtk8:8wtcMkCf"
}

