Home Features Pricing FAQ Documentation Join Report a bug or suggest an enhancement

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

Is the Single Success Payment fair?

We think it is the fairest deal an indie developer can get.

  • No risk to you. Nothing is owed unless a project earns more than US $500,000, so a game that never takes off never pays a cent, and a game that does pays once.
  • It keeps Nucleus going. Pro licences and support alone are not enough to fund years of development and pay the team. The Single Success Payment is what keeps the engine maintained for the games that depend on it.
  • It pays for itself. Nucleus uses a fraction of the bandwidth, CPU and garbage of other frameworks (see the benchmarks), so a successful game saves far more in server fees and development time than the one-time share costs.
If my game earns a lot more after I have made the Single Success Payment, do I owe more?

No. The Single Success Payment is made once per project, and then it is done.

Once your report is final and the one-time payment has been made, the Single Success Payment for that project is satisfied and no longer applies to it. You owe nothing more for that project afterwards, no matter how much it goes on to earn, whether that is another million or another hundred million.

What if my game earns slowly?

If it earns slowly, you may owe nothing.

If your game passes US $500,000 but earned US $75,000 or less over the year before its payment is assessed, you owe nothing. Just report it on time, and that game will never owe anything again, no matter how much it earns later.

Support

How do I report bugs or request enhancements?