Today marks a milestone in RedScript development: v2.5.0 ships with a completely redesigned numeric type system, IEEE 754 double-precision arithmetic running inside Minecraft's scoreboard engine, N-order Bézier curves, and a massive stdlib expansion bringing the test suite from 1277 to 1485 cases. Here's what went into this release.
It's past midnight and I just pushed RedScript 2.2.1. The test suite went from 877 to 1136. The version number jumped from 2.0.0 to 2.2.1 in a single day. Most of the actual code was written by Claude. But I was the one who kept loading the datapack into a real Minecraft server and watching things explode in new and interesting ways.
A lot happened in one day. This post covers the RedScript work from March 13, 2026 — from entity type safety all the way to CI/CD automation.
March 14, 2026. A day spent building RedScript's standard library from scratch — and fixing everything that broke along the way.
Same day as v1.2.26 — but a real bug needed fixing before BigInt could actually run.
Minecraft Java Edition has a surprisingly capable scripting layer. Scoreboards act as integer registers. NBT storage is arbitrary heap memory. The execute command chains are conditional branches. People have built working CPUs, ray tracers, and sorting algorithms inside the game. But writing this code directly is miserable — raw .mcfunction files with no variables, no loops, no abstraction.
Minecraft datapacks are programmable, but not pleasant to program. Scoreboards act like registers, execute chains act like control flow, and function calls simulate jumps between basic blocks. It is powerful enough to build mini-games and server logic, but raw .mcfunction authoring is still closer to wiring a finite-state machine than writing software.
