Hi DilanRona, thanks for the interest. Quick clarification: Manifold is a library for mod authors, and ManifoldSample is just a small showcase of what the API can do, not a content mod we keep adding features to. So I won't be adding a mining dimension to the sample itself, but what you're describing is exactly the kind of thing the library is built for, and it's fully doable today.

A custom dimension is completely isolated from the overworld: it gets its own dimension id, so generating it, filling it, or wiping it never touches overworld terrain or chunks. "Resetting" a mining dimension just means destroying it and recreating it. When a dimension is destroyed, Manifold drops its generated-column records, so the recreated dimension runs its worldgen again from scratch (fresh layout and ores) instead of reloading the old chunks.

The sample already demonstrates the two building blocks you'd combine:

• a persistent, generated dimension (see /flatdim, registered with .Persistent().WithWorldgen(...)), and
• a destroy-then-recreate teardown (see /destroytempdim, which calls ForceRemoveDimension to evacuate any players first, then removes the dimension).

So a resettable mining world is essentially a persistent dimension whose worldgen strategy places stone and ores, plus a command that calls ForceRemoveDimension and re-registers it. The overworld is never affected. If you (or a modder) want to build that as its own mod on top of Manifold, that's the intended path, and I'm happy to help point you to the right API bits.

Played some more with it today, and noticed a problem with the void dim. i filled it with a cube with dirt. and when i went back to the overworld, it placed me back where I was. Going back to the void dim placed me at y axis 1, and i started to fall into the void. Another problem I encountered is that if I use for example the portal mod, or something similar, it doesnt work between overworld and void dimensions. The void dimensions would be perfect for one particular megabuild project with a lot of space ships and a space station.

Hi! Yes to both.

Block-triggered transit (no commands) is the main path I designed Manifold around: it ships a `PortalBlockBase` helper class. A mod just registers a block that extends it; when a player touches or interacts with the block, Manifold runs the transit for you. ManifoldSample does this with a single demo portal block. The same hook works for a runic gate, a teleporter pad, a devastation-style proximity zone, anything visual the mod wants. No chat commands needed.

Vanilla translocators specifically are a bit more involved. Their teleport logic lives in the survival mod and isn't dimension-aware, so wiring them into Manifold means either a small Harmony patch on the translocator block-entity (totally fine for a companion mod, just not for Manifold core which is zero-Harmony) or a parallel translocator-style block that uses Manifold under the hood. I'd lean toward the second option so vanilla translocators keep working inside the overworld and your cross-dim hops live in a clearly-marked block.

If you want to take a swing at either, the API surface is small: `manifold.Transitions.TeleportPlayer(player, dimensionCode, options)` from any block-entity is enough. Happy to help via GitHub issues if you have a specific design in mind.

Thanks for the quick response! This is great to know as I would love to try and mess around with the manifold system for something i have in mind in the future, as for a specific design being set in mind i dont have on quite yet 😅. This is mainly me planning for the far future. im curios to see how your current mod and future mods develop!