Skip to content

FolioSpace Library 1.02

Choose a tag to compare

@funland funland released this 09 Oct 13:28
· 10 commits to main since this release

FolioSpace Library 1.02

This release publishes the PC-98 font and Triforce routing fixes previously used
in production, on top of the complete 1.01 baseline.

Changes

  • Per-ROM/version PC-98 font selection through a JSON sidecar or dedicated sibling
    bitmap, with generic-font fallback. One logical FONT.bmp is served with its own
    size/checksum. Targeted scans detect font-only changes without rewriting ROMs.
  • Triforce ISO/GCM/RVZ files in an exact Triforce path segment, library name, or
    library root use platform=ngc, emulatorHint=dolphin, romSetName=Triforce.
    Unrelated disc/NGC routing stays unchanged. Client emulation support, BIOS setup,
    and actual gameplay acceptance are separate from server delivery support.
  • Preserves 1.01 MAME content-equivalence support, FBNeo build-identity compatibility,
    CIA installation, Range/resumable downloads, and bilingual beginner setup.
  • Service and MCP metadata report 1.02. Docker images support Linux AMD64/ARM64.

No ROMs, cover collections, fonts, BIOS, firmware, tokens, or private catalog data
are included. No new automatic game import or policy replacement is introduced.

Upgrade

docker pull funland/foliospace-library:1.02

Back up the existing config/database. Update the image in your existing Compose
configuration, preserving its token, ports and mounts, then run docker compose up -d.
Do not replace a customized configuration with the example file.
For font changes, use a targeted ROM scan and refresh the client manifest/package.

See PC-98 configuration
and the retained MAME upgrade notes.

简体中文

1.02 将生产中使用的 PC-98 独立字体修复与 Triforce 分类路由正式发布。
保留完整 1.01 基线,不恢复 FBNeo App 指纹/构建标识拦截,也不包含私人资料库或游戏文件。
字体修改后定向扫描对应 ROM 并刷新客户端 manifest;Triforce 游戏能否实际运行仍取决于客户端核心和配置。
升级时保留现有 token、端口、挂载与配置数据。

Validation and known build-tool notices

Before publication: all Go tests and go vet passed; 34 web tests, TypeScript/Vite
production build, Compose configuration validation, and diff checks passed.
The scanner implementation matches the production hotfix source snapshot.

The unchanged npm lockfile reports high-severity advisories in the existing
Vite/PostCSS/nanoid/source-map-js build-tool dependency chain. These require a
separate dependency update; this release does not claim they are fixed. The final
Docker stage serves compiled static assets and does not include Node, npm, or
the Vite development server. The existing bundle-size warning also remains.