Tutorials

Learn to connect game objects through links instead of names, so a rename never breaks your game design. We'll also see how multilevel inheritance lets you build specialized templates

Enemies, characters and game cards all redeclare the same fields by hand. A base object defines that structure once - and each instance only fills in the values that make it different

Give each field a real type so its value behaves predictably and is validated - string, text, number, integer, and checkbox (boolean). A typed value carries its behavior from the editor, through the balance table, to the engine

Are you always at war with the fact that some data is written in the doc, and the engine sees completely different ones? We tell you how a single file can permanently save you from desynchronization

Where are your characters' enemies located? One folder holds every enemy as a structured game object you can duplicate and reuse