Tags
Creators
Details
2.0.0
Compatibility
Required content
Changes
Features
Starlance no longer requires Cosmic Horizons to play. Instead, Starlance will only load its thrusters and other VS features.
However, if a compatible space mod (right now just Cosmic Horizons and Ad Astra) is installed, Starlance will automatically enable its compat for that space mod, allowing VS ships to integrate with that mod.
Changes:
- Updated to VS 2.4.11+
- Can now be loaded without Cosmic Horizons
- Now compatible with Ad Astra (and still compatible with Cosmic Horizons)
- Added new "tier" blocks for modpack makers - these blocks control what tier of Ad Astra planet a VS ship can go to. These blocks will also be integrated with other space mods in the future.
- Added config to disable space mod compat entirely (e.g. if you want Ad Astra + Starlance but don't want VS ships to go to space)
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:dSMrdNMg:mby9tpNq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dSMrdNMg:mby9tpNq"
}






