SQLite3 Module

SQLite3 Module

Bioblaze Payne
–

Introducing the SQLite3 Module: native SQLite databases, resources, nodes, backups, BLOBs, and advanced query tools for Blazium Game Engine.

Introducing the SQLite3 Module

Blazium Game Engine now includes a native SQLite3 module for projects that need local databases, structured saves, embedded tools, analytics, or data-heavy gameplay systems. SQLite is one of the most widely used database engines in the world, and this module brings it directly into Blazium with a rich engine-facing API.

The module provides three layers for different workflows: SQLiteAccess for low-level control, SQLiteDatabase as a resource-backed database layer, and the SQLite node for scene-friendly integration. Together they cover simple queries, prepared statements, transactions, backups, BLOB access, custom SQL functions, JSON import/export, object serialization, diagnostics, and reactive hooks.

Key Features

Possible Uses in Games and Applications

The SQLite3 module is useful anywhere a project needs more structure than flat files but does not need a separate database server. It is small, battle-tested, and well suited to desktop tools, headless servers, editor utilities, and exported games.

For Games

For Applications & Tools

Because SQLite is embedded, the same project can run in the editor, in exported applications, or in headless automation with the same database behavior. The node and resource layers make common workflows approachable, while SQLiteAccess remains available when a project needs advanced control.

Documentation & Next Steps

The module is already available in the latest nightly of Blazium and includes a dedicated test project (see sqlite3_module_tests for examples).

Whether you are building a game with deep save data, an editor with structured project files, or a headless service with local persistence, the SQLite3 module gives Blazium a solid embedded database toolkit.


Jump into our Discord for real-time chats, dev support and feedback

Or follow us everywhere else: