Today connected several kinds of access to the engine. The harvesting work exposed more of a classic gameplay route as small, explainable contracts. In parallel, the project changed how creators, AI agents, and readers each reach those contracts without weakening the faithful core.
July 14 produced three connected foundations: a verified factory heartbeat, an executable rules-loading cascade, and a clearer boundary between faithful engine work and everything that can be built above it.
“Can this house build this unit?” looks like a yes-or-no question. In Yuri's Revenge, the answer is a three-state decision produced by an order-sensitive control-flow graph.
Reconstructing that graph took a sequence of small, testable pieces. The final composition is one of the clearest examples yet of why faithful behavior lives in the route to an answer, not only in the answer itself.
An RTS simulation cannot be reproduced exactly if “random” means whatever the host platform happens to provide, or if timers depend on wall-clock time. The second foundation milestone gave reTS its own faithful answers to both problems.
The first end-to-end piece of reTS was not a menu or a moving unit. It was a number: the exact amount of health removed when one object hits another.
That sounds modest. It turned out to be the right foundation for the whole project, because the original engine does not calculate damage in one neat formula. It passes the value through a sequence of rules, and the integer result can change if even two apparently equivalent stages are swapped.
Welcome to the reTS devblog.
Last verified against the project charter: 2026-07-15.
reTS is an early project to build a faithful, standalone, moddable reimplementation of the classic Westwood isometric RTS engine—the one behind the Command & Conquer titles Tiberian Sun, Red Alert 2, and Yuri's Revenge. Accuracy is the non-negotiable goal; modern, opt-in layers are planned only on top of verified behavior.