Team Colour Toolkit
Create, colour and lock teams so players cannot damage each other during events.
- Compatibility
- Tested on Java 1.21.4
- Updated
- 19 hours ago
Community archive for technical Minecraft
Discover, build and share the commands that transform Minecraft.
Find extraordinary creations, publish your own work and explore what the community can build.
Every entry is a real creation from a real creator, with its edition, tested version and install method declared up front.
Ranked by real activity
The work the community is saving and downloading most, weighted toward recent releases.
Create, colour and lock teams so players cannot damage each other during events.
Turn any gold block into a teleport pad using one repeating command block.
One command that clears every dropped rotten flesh item to cut down entity lag.
Skip to night and hold it there for cinematic builds or horror maps.
A visible countdown timer on the sidebar for events, minigames and build battles.
Gives u a god shulker from custom clownpierce
Fresh from creators
Newly published work, newest first.
Gives u a god shulker from custom clownpierce
A visible countdown timer on the sidebar for events, minigames and build battles.
Skip to night and hold it there for cinematic builds or horror maps.
One command that clears every dropped rotten flesh item to cut down entity lag.
Turn any gold block into a teleport pad using one repeating command block.
Create, colour and lock teams so players cannot damage each other during events.
Browse by discipline
Every category is a working toolset: commands, systems, packs, worlds and the logic that holds them together.
The studio is a workshop, not a text box. Every creation carries its edition, its version claim and its install method from the first keystroke.
Name it, pick the edition, describe what it does. The studio keeps a structured brief so players know exactly what they are installing.
Write commands or drop in a whole project tree. Lines are checked as you type — syntax, selectors, block types and execution order.
Declare the version you actually tested. Compatibility is a claim you make and stand behind, not a guess AXION invents for you.
scoreboard objectives add axn_charge dummyexecute as @e[type=zombie,tag=axn] at @s run particle minecraft:end_rod ~ ~1 ~ 0 0 0 0 1execute as @a[scores={axn_charge=20..}] run summon minecraft:lightning_boltIllustration of studio syntax · not a published creation
Publishing runs every command through the verification engine. The report is stored against the release, so a reader can see what was checked and what was flagged.
The command is split into coordinates, selectors, arguments and literals.
Every argument is matched against the Java or Bedrock command grammar.
Blocks, items and entities are checked against the edition's own registry.
Syntax is held against the declared target version and pack format.
Destructive, self-targeting or unbounded selectors are flagged.
Errors, warnings and safety flags resolve into one report.
Publishing is a deliberate act with a visible trail: content, metadata, verification, then the release itself.
Your files stay editable. Autosave keeps the working copy current without freezing anything.
The engine reads every command. A failing report stops the release; warnings are acknowledged.
The files freeze into a version with its changelog, edition and tested range. Downloads point at it forever.
ImmutableCreators with published work, and the collections the community uses to group it into something usable.
Creators
Profiles with published work, with live counts from the archive.
Curated sets
Public collections group related creations into something usable.
Community activity
6 published creations from 1 creator · latest 18 hours ago
Declare the edition, the version you tested and how it installs. AXION verifies the commands, freezes the release and gives it a permanent home.
Orientation
Three short reads that prevent the most common mistakes.