Help wanted: What would your “one-stop” Minecraft creator toolkit need to do first?

Over the past 18 months I’ve been supporting my son (8) who lives and breathes Minecraft. Along the way I kept running into the same pain point as a creator: you can do almost anything… but the workflow is fragmented. You end up bouncing between multiple tools, formats, sites, and steps just to get one thing done.

So I started building LumenForge: a web-based, no-install toolset aimed at giving creators a single, time- and cost-efficient pipeline for common Minecraft creator workflows.

Capabilities brief (best viewed on desktop/tablet): 👉 https://lumenforge-mc.co.uk/product-brief

The screenshots attached walk you through each page so you can see what’s already working today. It’s actively being developed, and if you check the Future Roadmap slide you’ll also see what’s already planned next (this is just scratching the surface).

A quick note on intent: I’m not here to “replace” the great tools and sites already out there — some have deeper or more specialised features than anything I’m building. LumenForge is about bringing those everyday creator needs into one central place, so pack creators, builders, and modders spend less time stitching workflows together and more time creating.

Current focus (high-level)

• Textures + block workflows (editing, iteration, preview, and creator utilities in one place)
• Build / schematic conversion + inspection (tested across legacy through modern versions — from 1.12.2 up to 1.21.11 — and across common formats like .schem, .litematic, .nbt, legacy .schematic, etc.)
• Pixeliser + voxeliser tooling (fast, consistent transformations for creator workflows)

What I’m looking for from the community

I’d genuinely love to hear from builders, resource pack creators, modders, map makers, server owners (essentially, everyone who plays) — anyone who’s dealt with the current ecosystem.

If you could have one central pipeline, what would you want it to do first?
A few prompts (answer any, ignore any):

• What’s the most annoying or expensive part of your current workflow?
• What do you do today that feels way harder than it should be?
• Which tools do you bounce between most often (and why)?
• If you could unify one messy process, what would it be?

PS (Beta access / shaping the roadmap): I’m aiming for a beta launch in early February to collaborate with any and all who may be interested to help push it hard (regression testing, stress testing, multi-user behaviour, edge cases) and help shape what the tool expands into next. This isn't a promotion for me, but for all of us who love the game. I am hoping to help all with the big problems.

#minecraft #resourcepacks #minecraftmods #texturepack #schematics #modding #gamedev #tooling #indiedev #creators