The412Banner fbd068c6b8 Epic: the engine takes the chunk cache path, and assembles the files itself ...

EpicNative.run passes chunkCacheDir after installDir, as the contract now
has it: "" keeps the cache beside the game, a path is the scratch cache in
the app's own storage that an install to a card uses. EpicNative.assemble
wraps the new nativeAssemble the same blocking way: the pending files are
written from the cache and each chunk goes right after its last use, then
the folder. The manager hands both runs the same path, uses the assembler
when it starts and keeps its own write loop as the fallback; the engine's
cache no longer has to sit beside a game on a card.

2026-10-08 19:32:14 -04:00

..

development

Epic: the engine takes the chunk cache path, and assembles the files itself

2026-10-08 19:32:14 -04:00

releases

docs: point 0.3.2 full changelog at the 0.3.2 tag (#438)

2026-10-08 10:49:29 -04:00

testing

Add game file exports and sync for Android frontends (#179)

2026-10-03 21:29:01 -04:00

agent-control.md

feat: agent bridge wayland and gamescope coverage (#406)

2026-10-08 03:50:58 +00:00

progress-log.md

Epic: the engine takes the chunk cache path, and assembles the files itself

2026-10-08 19:32:14 -04:00