nfty 1.3.1 — what the app says when you have not started, and how rare this one is

Two fixes to what the app says, following 1.3.0. 2,167 tests, 0 failures.

A brand-new CookBook no longer greets you with an error

Make a CookBook and the status bar says 1 problem before you have made a single
decision. The problem is real — CookBook has zero total recipe weight — and it is exactly
what the CLI prints, but to a first-time author it reads as something they broke.

The report leads with the explanation now:

1 problem — Fresh Book
This CookBook has no Recipes yet. Add one, then add Ingredients to it — until there is
something to stack, there is nothing to cook. Nothing below is a mistake you made.
1 · CookBook has zero total recipe weight.

It is derived from the graph, not from matching Validator's wording — a reworded message
must not silently stop being recognised — and it names the empty Recipes, because "add an
Ingredient" without saying where is barely better than the raw problem.

The kicker gets a third state: a half-built book is not a broken one, so it takes a plain
dot rather than the warning ink. And the footer stops saying "cooking is refused until these
are fixed" on a book nobody has started — true, but the reader was just told what to do one
line above, so a refusal underneath is a telling-off carrying no information. On a genuinely
broken book it still says exactly that.

An asset's rarity, as a percentage or as odds

Three answers the Set browser's rail could not give, all from the numbers it was already
showing.

The unit toggles. A percentage compares traits to each other; odds are what "how rare is
this one" actually asks — 4.17% against 2.08% reads as a near-miss where 1 in 24 against
1 in 48 does not. The whole column switches, header included.

The whole asset's odds. "The lock is 1 in 4 and the bands are 1 in 3" is not an answer to
how rare the asset is. The rail now prints this combo 1 in 43,200 beside the id — the
product of exactly the rows underneath it, recipe share included, so you can check it by
hand. It assumes the layers roll independently, which incompatibility rules and optional
layers both break, and the tooltip says so.

The rarest trait stays beside the RARITY heading. Deliberately not a rarity score: the
sum of the reciprocals is a convention this project has never adopted and would have to
invent, where the rarest trait is a fact already in the table.

Downloads

	Size	.NET 10 needed
Portable	84 MB	no — unzip anywhere and run. Start here if you are unsure.
Single file	76 MB	no — one .exe. Unpacks itself on first run, so that launch is slower.
Single file, .NET	14 MB	yes — one .exe, runtime left out.
Framework-dependent	14 MB	yes — the same, as a folder.

The two .NET builds need the .NET 10 desktop
runtime; the other two carry everything.