github XiONDiGiTaL/EmblemWeave v0.1.21
EmblemWeave 0.1.21

latest releases: v0.1.41, v0.1.40, v0.1.39...
6 days ago

EmblemWeave 0.1.21

Game Setup has a one-click check that prepares a packed package in a minute, without compiling anything

Install

  1. Download EmblemWeave-v0.1.21-windows-x64.zip below and unzip it into a folder of its own.
  2. Run EmblemWeave.exe.
  3. On Game Setup, choose your dump. On Overview, press Build the game (once), then Play.

sha256 of the zip: 458e40e76a36587eb3afbafb560e61a673119e0706d03d87d4ef00fab3869ab7

Game folder check

0.1.20 made the engine read a .nup that packs some of its files with zstd, by writing those files into work/romfs-overlay and
laying that folder over the package. The writing happened inside Build the game, which meant a player whose game was already built had
to sit through a full rebuild to pick it up.

Game Setup now has Check my game folder, above the validation list:

  • It reads the package and reports how many files are packed and how large they are, or says the package is read where it lies when
    there is nothing to write.
  • It writes those files into engine\fefw-recomp\work\romfs-overlay, resuming where an interrupted run stopped, and does nothing if
    they are already there.
  • It records the folder in fefw.ini under [fs] romfs_overlay, so the game that is already built starts using it: no compile, no
    rebuild, and nothing about the package is modified.
  • If the game has not been built yet it says so and leaves the folder ready for the next build.

Verified

  • cargo build --release and cargo test -p emblemweave: 119 passed, 0 failed, including a test that the repair writes its key into
    [fs] once and replaces it on a second run rather than adding another.
  • The Game Setup page shows the new section with its button, checked on a screenshot of the running launcher.
  • The writing itself was measured on a real 28.9 GB .nup in 0.1.20: 65,074 packed files, 2.1 GB, and the engine booted from that
    package with the overlay.
  • Not checked: the button pressed with the mouse on a packed package end to end. The job it starts is the same writing path the build
    uses, and the key it writes is the one the engine logs as read.

Still open

A package that packs its RomFS with a codec other than zstd still has to be repacked by hand; the launcher cannot read those.

Don't miss a new EmblemWeave release

NewReleases is sending notifications on new releases.