Tags
Creators
Details
1.5.0-forge-26.3
Compatibility
Changes
Quest-book content and the small progression signals behind it. Requires Neroland Core 1.15.0. Nothing here depends on NeroQuests: the quest pack is plain data inside the jar and simply stays dormant when NeroQuests is not installed.
Added
- Quest pack. Ships a NeroQuests quest pack โ chapter
nerospace:starfarers_log"Starfarer's Log", 19 quests โ that appears in the quest book when NeroQuests is installed; inert otherwise, no dependency. The chapter walks the whole arc from the first Nerosium ingot through orbit, the planets, colonies, freight and terraforming, including one shared "world log" quest for a hundred deliveries. - Record gates. Three player-scope Neroland Core gates โ
nerospace:first_freight,nerospace:terraformed_groundandnerospace:living_worldโ are opened beside the matching Star Guide advancements.first_freightuses Core's offline-capable overload, so an owner who logged off while their flight was in the air still gets the milestone. They have norequiresand gate nothing. - World freight log. The cargo-route store keeps one world-wide count of delivered flights (a plain
number, tied to no pad or player) and publishes a
nerospace:cargo_deliveredthreshold crossing on Core's bus at 1, 10, 100 and 1000 deliveries. Its scope is the destination dimension id only. - Hook gates. Two player-scope record gates other mods may open to hand a player an effect:
nerospace:hook/reveal_star_guide_pagesends the player a hint naming their next Star Guide step (nothing is awarded), andnerospace:hook/oxygen_top_uprefills the personal / suit tank to its normal maximum once. Each is applied on the server thread, or on the player's next login if they were offline, and the gate is closed again so it can be re-armed.
Changed
- Neroland Core floor raised to 1.15.0 (the gate and threshold APIs above).
Fixed
- The rocket screen's pad-destination button had two conflicting
gui.nerospace.rocket.padlang entries; it now readsLand: <pad name>as the screen intends.
Privacy: no new per-player data is stored by Nerospace โ player-scope gates live in Neroland Core's gate store, which Core's privacy notice covers โ and no UUID is logged; see PRIVACY.md.
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:MZjgyY44:XdnkScPF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MZjgyY44:XdnkScPF"
}

