ποΈ Defining Schema in Excel
Maintain structure definitions in tables with tables.xlsx / beans.xlsx / enums.xlsx (exact file names depend on the project). Good when business tables add fields often and you want designers to see the structure tables too.
ποΈ XML Schema
XML suits stable types maintained by engineers (base libraries, complex inheritance trees) and can coexist with Excel schema. One XML file can hold enum / bean / table together; you need not split into three files as with Excel.
ποΈ Type System Cheat Sheet
Types appear in bean field type, Excel ##type rows, or validator tags. This page gives copy-ready forms; for how to fill cells see Excel basics.
ποΈ External type mapping (TypeMapper)
Sometimes you want generated code to use existing project types instead of Luban-generated ones. For example, after defining vector3 in config, you may want C# to use UnityEngine.Vector3 rather than a generated vector3 class.
ποΈ Polymorphism and Abstract Beans
Make the base class an abstract type (with subclasses); data distinguishes implementations by type name (or alias); generated code uses inheritance, and loading yields concrete subclass instances.
ποΈ Importing Tables and Organizing Modules
This page covers: how to split namespaces, multiple files for one logical table, reusing shared types, and (optionally) auto-importing tables by file name.