Links
Tags
Creators
Details
Licensed CC-BY-NC-ND-4.0
Published 10 months ago
Updated 6 days ago
All versions
2.0.8
Release
Neptunian Moons (2.0.8)last week 6
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
Galacticube 2.0.8 — Neptunian Moons
Triton and Nereid become full Neptunian destinations: ice plains & geysers, a darker cratered Nereid, research structures, and living advancements. Built for client and dedicated server.
Triton
- Nitrogen ice / frost surface over
triton_stone, dark crack deposits, cantaloupe terrain patches - Extreme cold (cryo suit) + vacuum; low gravity
- Rare nitrogen geysers with particle plumes and
triton_frost_sample - Structures: Research Station, Cryovolcanic Site, Abandoned Probe, Geological Archive
- Resources: frost sample, ice shard, probe log
Nereid
- Dark gray-brown rocky surface (
nereid_stone/nereid_dust) — not another white ice plain - Large ancient craters, rims, highlands, debris piles
- Vacuum + cold (lighter than Triton); low gravity
- Rarer structures: Survey Station, Impact Site, Research Probe, Geological Archive
- Resources: rock sample, ancient fragment, research log
Advancements & map
- Living titles: Ice of Another World / At the Edge of Orbit / Cold Eruption / Witness of Glaciers / Last Signal / Neptune’s Domain
- Both moons on the Neptune branch of the galaxy map (rocket level 3+)
- Opaque 16×16 cube GUI icons (Mars-recolor style)
Also in 2.0.8
- Planet-variant ores place correctly (no generic uranium on Pluto stone); nickel/uranium need diamond pickaxe
- Ship Constructor visual overhaul (NASA-workbench-class model, Galacticube textures)
- Nereid/Triton surface fixes (no floating blocks / vanilla grass leftovers)
Notes
- Block dust/stone/ice follow Mars-recolor blotch patterns with Neptunian palettes
- Requires Fabric 1.20.1; install on both client and dedicated server
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:uMlTdqmk:1PHyd9CS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:uMlTdqmk:1PHyd9CS"
}

