Tags
Creators
Details
1.2.8
Compatibility
Required content
Changes
🔭 1.2.8
⚠️
/cosmiceventremoved. It's/exposurespace event ...now. Fix your command blocks.
Performance
- Sky renderer and viewfinder cached the wrong things (i.e. nothing). Both now share one cache instead of rebuilding per frame.
- Analyzer no longer re-checks a photo that already failed to match. Same fix in the Lightroom.
- Rendering wrapped in a catch. If a mod conflict breaks it, the cosmic layer turns off and logs instead of crashing you. Send me the log if you hit this.
Rewards
Diamonds were dropping from about a third of the catalog, some of it normal tier. A six-minute Sculk scan paid roughly what a common object did. Redone across all 256.
- Payout follows lens tier + object type. Pulsars → redstone, comets → ice, probes → redstone and copper, black holes → obsidian and netherite.
- Diamonds are excellent/sculk only now.
- Slow or rare objects pay extra.
- Film drops from 81 objects, was 6. Black-and-white up to high-sensitivity colour at Sculk.
Datapacks
New folder data/<namespace>/cosmic_removals/*.json. Lets you delete objects and events, which datapacks couldn't do before.
{ "objects": ["exposure_space:voyager_1"], "types": ["probe"], "tiers": ["sculk"] }
Also "all_objects": true if you want to wipe the catalog and ship your own. Rule files from every pack get merged.
Commands
/exposurespace analyzer <x> <y> <z> speed 10
/exposurespace analyzer <x> <y> <z> reset
/exposurespace status
Per-block speed, 0.05 to 100, saves with the block. Mostly for map makers, and for not sitting through a Sculk scan while testing.
Nothing in your world changes, objects are in the same places, studied entries keep their progress.
Requires Exposure and Architectury. Dedicated servers fine, same jar both sides.
Chinese translation by Flowersauce — thank you!
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:Tloc97gi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CXqSHlx2:Tloc97gi"
}










