Open AllYourBlocks opened 1 year ago
Well this is really tough to answer, because, the question is, how far do you want to go documenting this?
Example:
This is a function that resets the currently active arena, depending on arena settings, it calls the following, among many others:
These commands are technically also accessible and can be issued at any point in time, should we list them? because when I am physically in the 2 team modern condensed arena, I could just as well run the command arena:reset/2teams/modern/standard
There are commands like
They are safe to issue when you are in the arena, but they do not have a arena:paint/driver
- should we add this for consistency?
There are commands like:
It checks which arena is running and teleports you to the center of it - oh no, american spelling xD
Some colors have vintage/modern separation, some have 2teams/4teams separation, the complete list would be a mess...
So we will have to talk about what you want to give people, or maybe if we come to a list of commands, possibly all functions that end in "driver" where the data pack will apply some logic as to where it makes sense to go, without going into too much detail, and not give all the detailed specific functions?
I can tell you based on the fact that every single file in the datapack is a function that is callable at any point in time, technically, that we do have 2150 functions if we want to do a full inventory, that would include clearing of all chunks of all arenas, individually, that's why we have such a high number.
We should maybe take a day to sit down and talk this through ^^
How best to do this? Is there something we can use on GitHub to start writing this?