Tags
Creators
Details
1.3.0
Compatibility
Required content
Changes
š 1.3.0 "cool update" šššš„š
Events you can actually see
Every night-sky event now draws something. Raise the viewfinder (filter + lens, at night, same as the objects) or turn on Stellar View:
- Meteor Shower ā streaks fanning out from a radiant all night, a few fireballs that flare up and leave a train. The radiant moves to a new spot every shower night.
- Aurora Storm ā three curtains over one side of the horizon, rippling, green at the foot and violet at the top.
- Deep Sky Night ā the Milky Way, from horizon to horizon, dark rift and all.
The Night Analyzer says when there's something up there. None of it changes what objects are up or what a photo matches, it's just light.
Datapacks
It's a sky block in the event json: meteors, aurora, milky_way, any mix, every field optional. Colours, rate, radiant, span, tilt ā all in the guide. "sky": { "aurora": {} } is enough. Textures are white on transparent in textures/sky/ and can be swapped by a resource pack.
Performance
- Every object in the sky used to be its own draw call with its own texture. On an event night with luck x2.5 that was a couple of hundred per frame. The icons are now stitched into one atlas when the catalog syncs and the whole sky goes out in one call.
- Objects don't pop any more. Each one fades in and out (dusk, dawn, viewfinder up or down), and with Stellar View on, raising a camera whose lens sees a different set cross-fades between the two instead of blinking. The event sky fades with the layer.
Other
- New Cosmic Album icon. The old one looked like a folder.
Nothing in your world changes, studied entries keep their progress.
Requires Exposure and Architectury. Dedicated servers fine, same jar both sides.
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:CXqSHlx2:1D6nSN9B"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CXqSHlx2:1D6nSN9B"
}





