Resources & Assets¶

Doriax projects combine editor-managed resources with runtime pools and file helpers. Assets are authored or imported in the editor, copied and transformed during export, then loaded on demand by the runtime as needed.

Asset types¶

Loading assets at runtime¶

Most high-level objects accept a file path and load the resource automatically:

-- Texture loaded by a Sprite
sprite = Sprite(scene)
sprite:setTexture("sprites/hero.png")

-- Model loaded from GLTF
model = Model(scene)
model:loadGLTF("models/hero.gltf")

-- Sound loaded by Sound object
sfx = Sound(scene)
sfx:load("audio/jump.ogg")

Sprite sprite(&scene);
sprite.setTexture("sprites/hero.png");

Model model(&scene);
model.loadGLTF("models/hero.gltf");

Sound sfx(&scene);
sfx.load("audio/jump.ogg");

Runtime pools¶

Pools avoid loading the same resource data twice and centralize ownership. Objects that use the same file path share the underlying data.

Pools are managed internally. You normally interact with them through high-level objects (Sprite, Model, Sound), but you can query pool state or pre-warm a pool for level loading.

File I/O¶

The File, FileData, and Data classes provide platform-portable file access and in-memory buffers.

-- Read a file into memory
local f = FileData("saves/player.dat")
local contents = f:readString()
f:close()

// Read binary data
Data buffer;
FileData file("saves/player.dat");
file.read(buffer);
file.close();

File paths support both project-relative and absolute paths. On mobile and web, write-accessible directories are separate from read-only resource paths — use System::getPersistentStoragePath() for player save data.

User settings¶

UserSettings persists key/value pairs to a YAML configuration file. It is suited for player preferences, audio/video settings, and small game state. Changes are saved immediately on write.

UserSettings.set("volume", 0.8)
UserSettings.set("fullscreen", true)

local vol = UserSettings.getFloat("volume", 1.0)  -- second arg is default

UserSettings::set("volume", 0.8f);
UserSettings::set("fullscreen", true);

float vol = UserSettings::getFloat("volume", 1.0f);

Keep heavy save data (inventory, world state) in custom binary or JSON files. Reserve UserSettings for small configuration.

Asset path best practices¶

Export and asset packaging¶

At export time, the editor copies and processes assets into the output directory. File formats may be converted, textures compressed, and shaders compiled for the target platform. The source project folder is not modified.

See Export Window for details on the export pipeline.

See also¶

• Texture
• Model
• Sound
• Data
• UserSettings
• BundleManager
• Resources Browser