0.1.0.0
Compatibility
Changes
https://github.com/Akiak7/RecurrentComplexVolts1.20.1
Recurrent Complex Volts is a staged Minecraft 1.20.1 Forge port of the
legacy Recurrent Complex mod. The current port focuses on preserving the old
Recurrent Complex structure ecosystem: bundled .rcst files, user structure
files, missing-mod tolerance, manual placement, worldgen compatibility, and the
first pieces of the creator workflow.
Target:
- Minecraft: 1.20.1
- Forge: 47.4.10
- Java: 17
- Mod id: reccomplex
Implemented and actively tested:
- legacy
.rcstloading from bundled resources andconfig/reccomplex; - missing block fallback to
minecraft:air; - safe skipping/degrading of missing items, entities, and unsafe NBT;
- manual commands such as
/rc list,/rc check, and/rc place; - runtime compatibility audit commands with
/rc audit; - natural Overworld and Nether worldgen through the deferred compatibility bridge;
- legacy village, decoration/tree, sapling, maze, and script-generation subsets;
- command-side authoring with
/rc select,/rc export, and selection edit commands; - schematic interchange commands for listing, previewing, converting, and exporting
Sponge
.schemplus legacy.schematicfiles; - first-pass authoring tool items: Block Selector, Floating Block Selector, and Inspector;
- client-side selection outline, floating selector preview, and operation preview/confirm/cancel for structure placement and clipboard paste;
- a first modern
/rc guibrowser for browsing structures/schematics, launching preview-first operations, making editable config copies, applying generation/expression/transformer/metadata presets, and running selection, clipboard, export, marker, and script-marker workflows from the Author tab.
Still in progress:
- the full old GUI/editor workflow beyond the current browser, preview launcher, generation panel, and Author tab;
- exact 1.12.2 transformer table, placer/dependency expression language, and variable-domain parity;
- true modern jigsaw-pool integration for village pieces;
- exact old planned/complemented chunk records for every generation type;
- old GUI-driven schematic conversion screens and rich schematic ghost previews;
- complete modded block/entity/item remapping beyond safe missing-content fallback.
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:J8SYWt2i:ryrMcxGi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:J8SYWt2i:ryrMcxGi"
}

