AI and Nucleus
How much of a role did AI play in developing Nucleus?
Assisted by AI, built by humans.
What AI did
- Regression, bug and security testing. Wrote live-network tests that catch regressions, proved each bug with a failing test before proposing a fix, and hardened the engine by running security suites designed by a human.
- Code cleanup and documentation. Enforced the style rules, cleaned up naming, merged duplicated code and wrote the XML documentation.
- Demos, tutorials and first-draft docs. Built the demos and tutorials, wrote a step-by-step README for each, and drafted the first version of the documentation.
What humans did
- Architecture. Designed every core system of the engine and how they fit together.
- Performance and bandwidth. Came up with the techniques behind the engine's speed and low bandwidth, drawing on years of networking experience.
- Problem solving. Solved the hard problems, and supplied the key idea whenever a fix needed real insight.
- Quality control. Reviewed every change, and signed off on each change before it landed.
Is AI-assisted code secure? What about vibe coding?
Nucleus is not vibe-coded.
Vibe coding means shipping code nobody has really read, and that is where security holes hide. Nucleus is built the other way round. It was designed by people who each have more than seven years of experience in multiplayer game networking, and they reviewed every change. AI's part in security was running suites that a human designed, then proving each finding with a failing test before a fix was proposed.
Dozenscritical exploits our security suite has found in other modern frameworks and their services
0reported by the same suite against the Nucleus toolkit
Pricing and licensing
Support
How do I report bugs or request enhancements?
- Nucleus and the website. Open an issue on the Nucleus issue tracker.
- Documentation. Open an issue on the documentation issue tracker.