gum-runtime-fonts

Guide font loading and management across Gum's three runtime paths.

597|79|Updated Mar 11, 2015
One-click install
npx skills add https://github.com/vchelaru/Gum --skill gum-runtime-fonts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gum-runtime-fonts
Source: https://github.com/vchelaru/Gum/tree/main/.claude/skills/gum-runtime-fonts
Command: npx skills add https://github.com/vchelaru/Gum --skill gum-runtime-fonts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gum's runtime font loading can be complex due to multiple paths and a cascading lookup; this guide clarifies how to load and manage fonts for text rendering across MonoGame/KNI, including default embedded fonts, caching behavior, and extension points.

Core Features & Use Cases

  • Three Font Loading Paths: use a pre-built .fnt file (Path 1), auto-generated font cache files based on font properties (Path 2), or in-memory font creation at runtime via an IInMemoryFontCreator (Path 3).
  • Lookup Cascade: describe the sequence from cache to embedded resources to in-memory to disk to default font, ensuring predictable font rendering.
  • Key Files and Extensibility: overview of how TextRuntime, BitmapFont, FontCache naming, and CustomSetPropertyOnRenderable wiring interact, plus the IInMemoryFontCreator and IRuntimeFontService extension points.

Quick Start

Explain how to load fonts in Gum using the three paths and set up TextRuntime font properties.

Frequently Asked Questions about gum-runtime-fonts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does runtime font loading work in Gum for MonoGame?

Gum runtime font loading follows a cascade from FontCache files to embedded default fonts, then to in-memory creation and disk, ensuring predictable text rendering in MonoGame/KNI.

How do I load a bitmap font in Gum using a pre-built .fnt file?

Loading a pre-built .fnt file in Gum uses Path 1, directly referencing the bitmap font file for TextRuntime rendering without requiring auto-generated cache files.

What is the FontCache naming convention used for auto-generated font files in Gum?

Gum's FontCache naming convention auto-generates cache files based on TextRuntime font properties, allowing the Path 2 lookup mechanism to locate or create matching font files at runtime.

Can I create fonts in memory at runtime in MonoGame using Gum?

Yes, Gum supports in-memory font creation at runtime via the IInMemoryFontCreator extension point, bypassing disk lookups by wiring font generation through the IRuntimeFontService.

Why is my TextRuntime font not displaying correctly in Gum?

TextRuntime fonts may fail to display if the lookup cascade falls back to the default font, meaning you must verify FontCache naming, .fnt file paths, or IInMemoryFontCreator wiring.