All versions
1.2.0
Release
Jump Circle 1.2.03 months ago 651
Compatibility
Minecraft: Java Edition
1.21.10–1.21.11
Platform
Fabric
Supported environments
Client-side
Changes
Jump Circle 1.2.0
Version 1.2.0 is a major visual and performance update with redesigned effects, improved settings, and broader Minecraft support. Existing settings from 1.1.0 remain compatible.
Effects
- Added six circle types: Classic Rings, Layered Rings, Shockwaves, Gradients, RGB Effects, and Energy Effects.
- Added eight independent particle styles: Ice, Fire, Nature, Soul, Enchant, Wither, Lightning, and Galaxy.
- Every style now has unique geometry, movement, and sparks instead of using the same recolored effect.
- Improved Ice with snowflakes, Fire with layered flames, Soul with ghostly wisps, Enchant with mysterious runes, Wither with skulls and dark spikes, Lightning with branching bolts, and Galaxy with spiral arms and comets.
- Energy Effects now shows only the selected style without an unwanted generic ring.
Settings
- Rebuilt the settings screen in a compact Minecraft style.
- Separated Circle Type and Particle Style into independent options.
- Added sixteen ready-to-use two-color schemes with live previews.
- Simplified color settings and removed the old variant and gradient-type controls.
- Updated all eleven included translations.
Performance and Fixes
- Optimized geometry generation, color calculations, spark movement, and render-path allocations.
- Kept object pooling, distance culling, and distance-based detail scaling.
- Reduced CPU geometry-generation time by roughly 15–23% in the included microbenchmark without lowering visual quality.
- Fixed radius scaling for Energy Effects.
- Fixed effects becoming invisible with older configurations.
- Improved cleanup when changing worlds or reconnecting.
Compatibility
- Added four Fabric compatibility JARs covering Minecraft 1.21–1.21.11 and 26.1–26.2.
- Added verified Forge builds for Minecraft 1.21, 1.21.1, 1.21.8, 1.21.9, and 1.21.10.
- Improved compatibility with Fabric API, Mod Menu, Sodium, Iris, and shaders.
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:1CGoSGxp:GBErMZYs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1CGoSGxp:GBErMZYs"
}

