Tags
Creators
Details
Licensed MIT
Published 8 months ago
Updated 8 months ago
All versions
0.3.0
Release
Strange Matter 0.3.08 months ago 42
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1–1.20.6
Platform
Forge
Supported environments
Client and server
Changes
[0.3.0] - 12/16/2025
Added
- Chrono Blister: A gadget that shoots a bubble of time blocks that slow down mobs.
- Tinfoil Hat: A helmet that protects the player from certain anomaly effects.
- Research Tablet Debug Tools: In-game debug tools for research node layout and positioning
- Debug Mode Toggle: Press Ctrl+D in the research tablet screen to toggle debug mode
- Mouse Coordinate Display: Shows X/Y coordinates in research space and grid-aligned positions when debug mode is active
- Node Dragging: Click and drag research nodes to reposition them with 80-unit grid snapping
- Position Persistence: Node positions are saved to
config/strangematter/research_node_positions.jsonfor sharing between modpacks - Manual Save: Press Ctrl+S in debug mode to manually save node positions - Research Tablet Zoom: Added ability to zoom in the research tablet using the scroll wheel.
Changed
- Energetic Rift Zaps Lightning Rod: Placing a lightning rod near an energetic rift directs all zaps to the lightning rod, protecting mobs/players.
Fixed
- Dimension Dependent Research: Fixed issue where research was dependent on the dimension the player was in.
- Graviton Hammer Block Breaking: Fixed issue where Graviton Hammer AoE/tunnel mining could break bedrock and bypass FTB Chunks claims.
- Ores not working with modded tools: Fixed issue where tools from some other mods don't drop shards/resonite when mining ores.
- Dedicated Server Startup Crash: Fixed dedicated server crash by moving client-only packet/UI/sound hooks behind proper Dist guards.
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:4qqD58Pk:1GLg2b5Z"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4qqD58Pk:1GLg2b5Z"
}

