02b45cc4

Guide
- Move sets
- Pose constraints
- The variation harness
- Getting content into a running game
- Components
- Entity queries
- Booleans and handoff
- The editing pipeline
- Element selection
- Face materials
- Foliage mode
- Icons
- The editor shell
- Editable meshes in a scene
- Editor modes
- Building to a number
- Scene menus
- The shape tool
- Snapping
- Sub-object picking
- Sculpt and paint mode
- Writing an editor plugin
- Block-out shapes
- Booting an application
- Character movement
- Editable meshes
- Growing a forest
- Foliage instances
- Grass
- Mesh booleans
- Mesh operations
- Mesh surfaces
- Networked players
- Players and possession
- Splines
- Terrain brushes
- The terrain heightfield
- Painting a terrain
- Sculpting a heightfield
- Saving and restoring a world
- Admission, health and the control plane
- Durable state and the ledger
- Placing players
- Placing realms
- Shards, keys and specs
- The cluster
- The service plane
- Transfer tickets
- Transferring players
- Upgrading a fleet
- Writing a realm
- Drawing foliage
- Drawing grass
- Impostors
- Culling and streaming instances
- Turning on dynamic global illumination
- Meshes and materials, type by type
- Drawing particles
- Lighting a scene in lux and lumens
- Making a room look different
- The post-processing node kinds
- Making everything cast a shadow
- Drawing a terrain
By kind
- Components39
- Systems48
- Controls165
- Shaders48
- Graph nodes64
- Importers22
- Annotations45
- Diagnostics8
- Log events64
All namespaces275
Releases1

DirectiveSyntax

class

csharp

public abstract class DirectiveSyntax

A file-level header: @component, @namespace, @tag or @using.

No guide page documents this yet — the page shows what the code says about itself.

Remarks

⚠ They share a base so that they can share a list, and they share a list so that the tree holds them in the order the file wrote them. Held as one field each — which is what this was — a node's children come out in *field* order, so a file that put its @using above its @namespace did not reproduce itself. That is the one property everything else here rests on: an incremental reparse, a formatter and every span-to-source mapping all assume a tree can be printed back into the file it came from.

Used by (6)

ComponentDirectiveSyntaxVixen.Ui.Markup
DocumentSyntaxVixen.Ui.Markup
NamespaceDirectiveSyntaxVixen.Ui.Markup
SyntaxFactoryVixen.Ui.Markup
TagDirectiveSyntaxVixen.Ui.Markup
UsingDirectiveSyntaxVixen.Ui.Markup