BrickSuite v0.3.0

BrickSuite v0.3.0

BrickSuite v0.3.0 is a major usability and workflow release focused on faster loose-part management, improved Build workflows, Minifig support, Collection management, and stronger database protection.

Highlights

• My Collection — Track individual Sets, Minifigs, and MOCs with state, condition, completeness, location, nickname, notes, and source Build information. Collection items can be added directly from catalogs or completed Builds.
• Minifigs Catalog & Builds — Browse and filter Minifigs, retrieve or import their parts, create Builds From Stock, allocate and pull inventory, complete Builds, and disassemble them back into inventory.
• Part Reference — A persistent visual reference window with 2,955 parts across 37 catalogs, Gallery and Dimension Grid views, searching, and direct integration with Add Part.
• Improved Build From Stock — Requirement-aware allocation, substitutions, Missing Parts integration, interactive pulling, pull-list reconciliation, and improved Set/Minifig/MOC workflows.
• Set Composition Workflows — Retrieve Set parts from Rebrickable or import CSV/ZIP parts lists, then create frozen Build requirement snapshots from the catalog.
• Faster Inventory Entry — Improved Add Part workflow, Remember Part, BrickLink ID cross-reference support, Correct/Remove Entry, and session-based Storage destination memory.
• Inventory & Collection Locations — Storage locations can now be designated for Inventory, Collection, or both while sharing the same hierarchical location model.
• Manufacturer Management — Add and maintain user-defined Manufacturers through Lists & Reference Data while preserving historical references.
• Database Status & Integrity — Run database integrity and foreign-key checks with recovery guidance and diagnostic information.
• Automatic Verified Backups — Scheduled backups with configurable frequency and retention. BrickSuite checks database health before creating an automatic backup and verifies each new backup before retention removes older ones.
• Improved Import Support — Expanded CSV/ZIP support across BrickSuite, including nested ZIP handling for supported Rebrickable imports.

Collection Modeling

v0.3.0 introduces a new physical Collection model separate from Builds and loose inventory.

Collection items can represent multiple physical copies of the same Set or Minifig and independently track:

• State — Assembled, Unassembled, Partially Assembled, or Sealed
• Condition — New or Used
• Completeness — Unknown, Complete, or Incomplete
• Collection location
• Nickname and notes

For Collection purposes, Complete means the required model pieces are believed to be present; optional catalog spare pieces are not included in that assessment.

Completed Set, Minifig, and MOC Builds can be added to My Collection. When a linked Build is later disassembled, BrickSuite synchronizes the Collection item's assembly state with the disassembly transaction.

Reliability & Database Safety

BrickSuite v0.3.0 includes substantial database-safety improvements:

• Database integrity and foreign-key diagnostics
• Recovery guidance
• Verified manual and automatic backups
• Pre-backup database health checks
• Schema-version-specific automatic backup folders
• Configurable automatic-backup retention
• Verified pre-restore safety backups
• Full migration support from the v0.2.0 database schema to v0.3.0

Platform Support

BrickSuite v0.3.0 has been built and smoke-tested on:

• Windows 11
• macOS
• Ubuntu Linux

The downloadable installer is currently provided for Windows. macOS and Linux packaged distributions remain planned for future releases.

Upgrading from v0.2.0

The v0.3.0 database migration preserves existing BrickSuite data while upgrading the database to the current schema.

As with any application upgrade, make a backup of your BrickSuite database before installing the new version.

BrickSuite's automatic backup system will begin using a new schema-version backup directory after the upgrade; backups from earlier schema versions are retained.

Notes

• BrickSuite remains a local desktop application using SQLite.
• API credentials remain optional and are configured through Settings.
• Some provider features require a Rebrickable or Brickset API key.
• Collection items are not yet used automatically as sources for missing Build parts; that capability is planned for a future release.