Tags
Creators
Details
All versions
1.4.0
Release
1.4.0last year 449
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
Additions:
- Magnet boots can now be toggle with a keybind (defaults to
X) - Magnet boots work in the curios's boots slot
- Added
ship_landing_modeconfig option:PLAYER_MENU: Will always use the player menu for landing location. Ships cannot land without a player nearby. (Behaviour from previous versions)HISTORY: The saved launch position (for that planet) will be used. If no launch has been saved, the origin will be used.AUTO_HISTORY: Ships will usePLAYER_MENUmode if a player is nearby, otherwise they will useHISTORYmode.
- Added
ship_landing_accuracyconfig option. When a ship is landing on a planet, the ship will be teleported randomly within the stated range in chunks. - Added
ship_first_landing_spawn_rangeconfig option. Defines how far away the ship should spawn from the origin when first landing on a planet. - Added LOD warning when the
lodDetailValkyrien Skies setting is too low. - Added
supressess_press_y_hintconfig option to suppress the "Press Y To Open GUI" Cosmic Horizons message.
Changes:
- Starlance now only supports forge 47.4.0 and above
Fixes:
- Fixed magnet boots not working at block edge
- Fixed the render optimisation mixins using the server config instead of client one.
- Fixed ships having the incorrect orientation when entering planet from the sides.
API:
- Added
PreTravelEventto adjust new position and new orientation when a ship cluster is teleporting. - Added
PreShipTravelEventto adjust ship's velocity and omega when teleporting.
Optional dependencies
Unavailable 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:dSMrdNMg:dtdCzUv3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dSMrdNMg:dtdCzUv3"
}

