Why Deterministic Finite State Machines Matter
In digital trading card games (like Cardfight!! Vanguard) and high-stakes financial order matching engines, state corruption and desync are unacceptable.
1. Strict State Isolation (FSM)
Actions are only valid within their exact phase. A client cannot send a "Drive Check" packet if the engine is not strictly in the DRIVE_CHECK state, eliminating timing and packet-injection exploits.
2. Seed-Based Deterministic RNG
Given the same initial seed and sequence of user inputs, the entire game or transaction matches identically across client and server. Replays are 100% reproducible by simply saving the input stream.
3. MoonSharp Lua Sandboxing & OTA
Game mechanics and card rules are written in sandboxed Lua scripts loaded dynamically over-the-air (OTA). The core C# engine guarantees zero memory leakage and strict execution timeouts.
4. Cryptographic State Hash (Auditability)
After each state transition, a checksum hash of the entire game tree is generated. In P2P multiplayer or financial audit trails, this allows instant desync detection without sending bulky payloads.
Erlando Aubrey
Architecting deterministic rule engines, low-latency financial systems, and full-stack software. Open to Senior/Staff Individual Contributor (IC) roles and technical consulting.