gum-tool-font-generation

Automating bitmap font generation for Gum projects involves collecting font properties, building a BmfcSave model, writing a .bmfc template, and running bmfont.exe to produce .fnt and .png pairs. This pipeline supports both on-demand and bulk project-wide generation.

Deterministic caching for bitmap fonts uses FontCacheFileName to deduplicate outputs, ensuring identical font settings reuse existing caches. This mechanism eliminates redundant generation passes and maintains stable, consistent font files across the pipeline.

On-demand font creation from property changes is fully supported alongside bulk generation. You can trigger individual font updates or execute project-wide generation depending on your specific workflow requirements.

Texture size optimization during .fnt and .png generation estimates necessary texture dimensions or applies a heuristic to minimize page count and memory costs, reducing overhead while maintaining font quality.

A BmfcTemplate.bmfc file serves as the configuration template for bmfont.exe, defining font properties and settings. The generation pipeline builds a BmfcSave model, writes this .bmfc file, and executes bmfont.exe to create the final bitmap font outputs.

Bmfont.exe integration is required to execute the final rendering phase of bitmap font generation. The pipeline writes the .bmfc configuration file and then invokes bmfont.exe to produce the actual .fnt and .png texture pairs.