Referencia de API

Starting an instance, the handle a running game exposes, its events, and what the renderer resolved to.

Declaring scenes, switching between them, pausing one without stopping the loop, the transitions, and the scene document.

What runs every frame, and what runs when a scene is taken down.

What a scene is filled with: sprites, texts, models, emitters, lines, materials, and destroying them.

Attaching authored behaviour to an object, its declared settings, and what one script can expose to another.

Keyboard, pointer and gamepad, plus named actions and the remapping layer a player owns.

State that outlives a scene, with optional persistence.

The state an object keeps while it lives, and code that runs when it changes.

Named event channels, Godot-style, and the events an object sends up to whoever holds it.

The 2D drawable and its atlas.

Tile layers, their source atlas, and reading a tile back.

Emitters, their curves over a particle lifetime, and the document they serialize to.

The 3D camera and the 2D one, picking through them, and aiming one.

Directional, point, spot and ambient lights, and the two kinds of shadow the era affords.

The shapes models are made of.

What moves over time: sprite frames, skeletons and their clips, and tweens.

Surfaces, custom shaders, and the file format shaders are written in.

Writing a shader as typed values, and the node graph a .shader file holds.

The chain that runs over the finished frame: dither, posterize, palette match and LUT grading.

Colour values, indexed palettes and grading tables: the indexed-colour half of the retro look.

Sound, music in layers, zones and the listener.

Every asset hook and the loader they report through, for progress bars and preloaders.

The body format the engine defines and the seam an adapter registers through. The simulation lives in the adapter.

The project file: the game window, the main scene and the input map.

What the renderer is told and what it answers: backends, capabilities and draw items.

Angles, interpolation, quaternions and seeded randomness.

The easing curves, kept apart from Math so they do not swamp it.

Id generation and asset path resolution.

Lines, grids and axes drawn over the scene, to see what the game is doing.