Yeah what Rsed said, if it would be the literal string hidden, it'd be written as "hidden" with the quotes around it. If it's without those, it refers to the name of another member, and its value. I'll consider this solved.

Thanks for the report. A few dozen methods got dropped in fact, unfortunately. Sorry about that. Fixed for the next release.

Worked it all out for 2.1, thanks again.

Ah now I get what you mean, thanks. That is indeed quite underdocumented. I'll make sure to note the default for truly optional properties, and note on the others that they are required at least in the root style. I'll also write down the root style name while I'm at it. It'll be for 2.1 though.

Thanks for bringing this up, I will document the whole process for 2.1.

As for your specific concern about item signals, it goes through all recipes that produce that item (excludes catalyst-only products), that the machine can produce and that are researched, and picks the first one that works ...

I mean, isn't it implicit that any table can be empty? If it required a certain number of values, that'd be the detail to document imo.

Thanks for the report, this is noted in the docs for the next release.

Thanks, fixed for the next release.

Thanks for the report, fixed for the next release. The extra ones are indeed 32 bit though, so prototype docs are all correct.

One thing I don't quite get though is your remark about draw_grayscale_picture. I can't see any special handling of that in the code, can you explain what you mean again?

Thanks for the report, I went over everything that mentioned ticks, and changed it to MapTick where appropriate. There are still quite a few places where it'll be documented as uint32, as that's what the engine clamps it to in those cases. Fixed for the next release.

Thanks for spotting that, fixed for the next release.

I added these details to the docs for the next release, thanks.

I clarified the effect on dependent crafts for the next release.

Thanks, fixed for the next release.

Appreciate the report, and the sleuthing boskid. Fixed for the next release.

Thanks, fixed for the next release.

Thanks, fixed for the next release.

Well sort of, it's hard to do that on a static website. We'll see.

They'll show up starting with the next release, thanks for the suggestion.

Okay so for the next release, search will look for more properties. Mainly runtime concept unions, tables and LuaStructs; prototype Type unions; and define 'leaf nodes'. This doesn't satisfy the title of the thread, but I don't think making the lib page show up in search will really do anything. It ...