Skip to content

nfty 0.4.1 — the packed .set stays in the folder you chose

Choose a tag to compare

@corderro-artz corderro-artz released this 06 Sep 22:36
· 655 commits to main since this release

Patch release. One fix.

The packed .set stayed out of the folder you picked

With Pack ticked, the archive was written as a sibling of the output folder — cook into
Documents/chests and the .set turned up in Documents. Everything else a cook writes goes into
the folder you chose, and the one output that left it was the one most likely to be handed to
somebody else. The Cook dialog made it worse: it reports and reveals the folder you gave it, which
was not where the archive went.

It now lands inside that folder, beside the images it packs, named after the folder:

mycollection/
  images/
  metadata/
  nfty/
  set.json
  mycollection.set     <- was ../mycollection.set

Two things had to come with it. The archive can't contain itself, so the file list is taken before
it is created. And a .set already in the folder is never packed into the new one — cooking twice
into one folder is exactly what extend does, and otherwise the first archive would nest inside
the second and double the size on every run.

Entries are also written in a fixed order now rather than whatever order the filesystem hands back,
so the same Set packs to the same archive on any machine.

If you have scripts that expect <outdir>.set, they need the path moved inside. Archives
written by 0.4.0 and earlier still read exactly as before — only where new ones are placed changed.


Nothing else moved: same demo CookBook, same engine, same output. Suite Cli 117 / Core 942 / App 639,
zero warnings.