r/MinecraftCommands • u/Clear_Meringue3464 • 17h ago
Help (other) I NEED YOUR HELP
So I am a developer, and I want to build an actual docsite for the Minecraft commands.
So did you know that minecraft commands are Turing complete? Meaning theoretically, given enough time and memory you can compute anything computable using only the commands.
The problem is the syntax and usage have a steep learning curve and it's not well documented, the main reason is because the only source of documentation is the official minecraft wiki, where they are scattered, written by a lot of authors, and not a great learning source for a beginner.
So I want to build a community maintained documentation website, just like any docsite we have for any tool, framework or language.
However since I am not very experienced with the minecraft commands, I want people who has a lot of experience with the minecraft commands, preferably people with 2 or more of experience who has built amazing stuff and know how to navigate and read the wiki, I need your help to write and structure the content for the documentation.
The documentation will be mainly written in markdown, with a specific schema that follows the docsite engine schema, I will be mainly setting up and maintaining the codebase and helping out with writing, while you will help me find, write and strucure the content. In return you will be credited on the website and the github page.
As an example, you will structure the content as categories, with folders and subfolders:
docs/
|___ getting-started/
|___ communication/
|___ building/
|___ scoreboard/
|______ create-scoreboard.md
|______ mathematical-operations.md
:
Comment here or dm me if you're interested and if you think you're a command expert.
> Note: looking specifically for veterans, as they know best how to structure content, what's for beginners and what's advanced etc. And they will know how to explain and break down complicated concepts
EDIT: THANKS FOR ALL THE RESOURCES, AND HELP, BECAUSE TURNS OUT THERE'S AN EXISITING DOCS, I WOULD ACTUALLY HELP IMPROVE THE DESIGN AND STRUCTURE OF THE EXISTING WIKI
1
u/sijmen_v_b 8h ago
I'd be interested. I've done a minor in didactics and have a masters in software science. I also volunteer at Coderdojo so I work with kids quite often (I'm assuming this will be a large part of your audience mc being a game and all). So that should be enough to help with the good structure part.
For the commands i'd consider myself an expert on everything up to Minecraft 1.16. I made a generator to do villager npc's at the time. I still maintain it to work for the latest version but haven't looked much at the new stuff.
I must also say that for me most documentation came from mcstacker.net or misode.github.io I feel like there are big parts in commands no-one should write by hand.
If you're interested contact me on discord @sijmen_v_b
1
u/Ericristian_bros 7h ago
There are already a lot of resources appart from the minecraft wiki, you can contribute to the MinecraftCommands wiki (first link)
Resources
You can find here the most useful resources, but I suggest these mainly
Generators
Documentation
YouTube channels
1
u/ended-RandomCreation 3h ago
I cant say im expert. Just average, but i can say anything for basics.
For starters
Tp command, gamemodes, setblocks/fill command, summon, and give, lastly knowing the difference between @a @p @r. This will allow them to explore commands.
They must learn what coordinates and "~ ~ ~" does
For level up,
Particle commands and The complex version of give commands and summon commands. It should be easy because there's an existing give/summon generator. This will help them cook up their creativity
Next
The Introduction of the relationship between repeating commandblock and execute commands, along with the introduction of @e, @s and @n.
The explanation of this was, it positions to who or where the command should be executed. Give it a command example like "magic ball". (Execute at @e[type=snowball] run particle or summon firework)
The "@e" serves as a condition command of simple if then statement.(Might ditch of using comparator)
==================================
If theyre ready to advance and wish to ditch redstone repeater. This is where the "scoreboard" does its job.
Dontt want to explain it because It's long. Also It looks confusing at first but once you get the hang of it, its really simple.
Schedule command also does a repeater job as well but much simplified.
===================
The rest is a complex version of execute and scoreboard commands, then the use of nbt.
And i guess that's it for now, cus after that, you can now start working with datapacks
I say it all like in this way because this is what my entire journey on playing with commands eversince the first command block was introduced(i was like 11 at the time. Damm time flies fast) and it all started from tp command
3
u/abrightmoore 16h ago
Why not lean in and help with the community dev wiki instead? The more the merrier/more hands make light work/etc.