All versions
1.1.0
Release
DAOT: Mobility+ 1.1.03 months ago 3,763
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Unavailable version
Any compatible version
Any compatible version
Changes
MULTIPLAYER UPDATE!!!
Mobility+ has been rebuilt to support:
- minecraft servers with a new hybrid system
- LAN
- singleplayer
- mod menu
- boosts using DAOT's gas!
the addon now uses the same jar to work in client and server!
HYBRID system uses both client and server sides to work in multiplayer
CLIENT SIDE
- uses original physics
- camera steering
- lock-rope
- cinematic 3rd person
SERVER SIDE
- boost authority
- gas usage
- cooldown validation
- config override
server boost authority
server:
- recieves boost packets
- validates cooldowns
- checks gas usage
- applies final boost!
this prevents:
- infinite boosting
- cooldown bypassing
- gas bypass exploits
REAL DAOT gas integration!
Mobility+ now directly works with DAOT's gas system
- reads actual ODM gear gas data
- consumes gas during boosts
- blocks boosts when empty
FULL CONFIG!!
added:
- cloth config api support
- optional mod menu integration
- JSON config file support
- server-side gameplay configuration
config settings:
- boosts use gas (true/false)
- boost gas cost (number)
- boost cooldown ticks (number)
- boost strength (number)
- cinematic third person (true/false)
- vertical strength multiplier (number)
- speed cap (number)
PASSIVE MOVEMENT STYLES
BLITZ MODE:
- only works when not using any input other than hook key
- 75% increased speed cap
- increased acceleration
CONTROL MODE:
- active when using input other than hook key like w/a/s/d/sprint
- vertical and horizontal orbit
- rope lock mode

Optional dependencies
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:lh2U8Yzz:ZtceE5hK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lh2U8Yzz:ZtceE5hK"
}

