Which recipes are in this book?

[dwarfkoala]

So, now that we have so many more recipes put into books, I think that a revamp of the recipes in books system is in order. You look at a book and it says "You can learn X recipes from this book", but which recipes? Have you already learned some of these recipes? What skill do you need to learn these recipes?

What if when you look at a book, it says something like this:

"This book contains 4 recipes for you to learn:
Reflex Recurve Bow (5 Fabrication)
Longbow (3 Fabrication)
Short Bow (1 Fabrication)
Metal Arrows (2 Fabrication)

You already know how to craft 1 recipe from this book:
Heavy Wood Arrow Shaft (2 Fabrication)"

That's one way to do it, or you could do:

"This book contains 5:
Reflex Recurve Bow (5 Fabrication)
Longbow (3 Fabrication)
Short Bow (1 Fabrication)
Metal Arrows (2 Fabrication)
Heavy Wood Arrow Shaft (2 Fabrication) [Learned]"

I think that would improve book recipes greatly.

[Headjack]

Yeah, I often get confused on this, and thing a three-color system for still-educational, recipes-only, and education+recipes would be ideal. Though in some cases it's less mysterious to already know what you can learn, like the lab journals

[dwarfkoala]

A three color system is effective, but I don't think that it can replace
knowing exactly what recipes you can learn from a book and what skills you
actually need to learn them. What do you think about what I have suggested
up here?

On Mon, Dec 30, 2013 at 5:25 PM, Headjack notifications@github.com wrote:

Yeah, I often get confused on this, and thing a three-color system for
still-educational, recipes-only, and education+recipes would be ideal.
Though in some cases it's less mysterious to already know what you can
learn, like the lab journals

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5302#issuecomment-31379538
.

[Headjack]

It would definitely be effective, but it could also glut the size of the descriptions and spoil interesting things like Journal-Herrera.

[dwarfkoala]

Journal-Herrera?

On Mon, Dec 30, 2013 at 5:59 PM, Headjack notifications@github.com wrote:

It would definitely be effective, but it could also glut the size of the
descriptions and spoil interesting things like Journal-Herrera.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5302#issuecomment-31380369
.

[KA101]

Dwarfkoala's issue is well taken, especially as I've made a point to have recipes in at least two books wherever at all possible. Duplication is a pisser. But I think I'm with Headjack on this one, chiefly because some of the dedicated recipe books such as the Handloader's Helper would have piles and piles of recipes, and listing them could cause screen-capacity issues.

As for the spoiler thing: Cuciana Italiana might have listings for Pasta Primavera, Spaghetti Bolognese, and Pizza, but Survival Under Atomic Attack's supposed to be tough to understand. (It's one of my favorite places to stash recipes, though. Grab a copy!)

Stuff like Lab Journal-Herrera is tricky. It's an actual lab journal, so it ought to be organized, but not necessarily labeled clearly. Rather than "CBM: XYZ", more like "Mechanical Augmentation Project Foo"?

Stuff like the mutagen proposals could probably do with the "Nicknames" removed, but then that just encourages metagame knowledge. :-/

[BevapDin]

What about a new property of recipes: name_in_book.
Defaults to the name of the result item, but can be specified in the json files.
Can also be empty to not name the recipe.
"This book contains recipes for Mechanical Augmentation Project Foo, some kind of mutagen and 3 unlabeled recipes."

[D0minae]

So many random options -

What about a flag for how much of it you've read. (New To You) - (Reading It) - (Finished It) so you can just glance at books in a pile to know if you're all done with them - skilling as well as recipes.

Or you could just put check boxes in the description, it would keep it easy to see if you're done with the book but wouldn't spoiler the recipes: Recipes In Book [x=known]: [x] [x] [ ]

[i2amroy]

I do agree that we need some sort of system to designate how many recipes you can learn from a book, but I do agree that it shouldn't list the exact recipes.

[kevingranade]

I like BevapDin's idea of labelling it on the recipes, if it's obvious that
you'll learn a recipe from it (cookbook) we could display something, if not
(process for making meth buried in the text) we don't. Cake + eat cake =
cake
Ideally this would go on the book instead of on the recipe.
On Dec 31, 2013 3:03 PM, "Christian Buskirk" notifications@github.com
wrote:

I do agree that we need some sort of system to designate how many recipes
you can learn from a book, but I do agree that it shouldn't list the exact
recipes.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5302#issuecomment-31411243
.

[KA101]

Yeah, recipe-ID is something that needs attached to the book, and ideally would show up in the item-examine screen where there's some real estate for the list. (Anything with id "recipe_FOO" is probably gonna be kinda extensive.)

[dwarfkoala]

#5321
I think this is fixed! Thanks everybody.