Suggestion: Option to Request Check/Define Result Ranges

[WManoil]

With D&D 5e (and other similar systems in mind), what do you think about adding a checkbox to request a skill or tools check (maybe offering multiple selectable options, if a tools check could alternatively be handled by a skill instead)? A stated DC for the recipe's check could be applied, and from there, you can apply not only success and failure ranges but also define if the supplied materials are destroyed on a failure or critical failure.

You could follow that up with the potential to multiply the completed recipe product at certain ranges beyond the DC or with a critical success, or offer the option to add contextual messages at certain ranges that could provide narrative flavor or player instruction.

I'm running an outdated version of Foundry at the moment (v11) and I've been interested in this module for a while, but I've hesitated to adopt it for my purposes because I'm hoping it can utilize more risk of failure or depend on the talents of specific characters.

[WManoil]

Ah! Forgot to add another suggestion in my original post:
Creating interactive NPCs (like the Loot Piles module), in which certain categories of crafting can be handled. I'm interested in creating specific stations for crafting, and having a garage workbench for mechanics-related crafting and a stovetop for cooking-related crafting would be fantastic for immersion.

[Furukia]

Hello and thank you for your suggestions! But i do have some disagreements about them. Let me break it down for you.

With D&D 5e (and other similar systems in mind), what do you think about adding a checkbox to request a skill or tools check (maybe offering multiple selectable options, if a tools check could alternatively be handled by a skill instead)?

I do not think that doing it that way is a good idea. When i created this module the first thing that was in my mind is making it system agnostic and simple to use. Some less popular system's can benefit from my module this way. Creating system specific request logic will strain my efforts. Especially because popular systems tend to update often which can easilly break things.

Instead of this i had an unimplemented idea to create a way to link macroses to recipes. That way any advanced foundry user will be able to code their own logic to do whatever, at different points of the crafting process. If i ever implement this later i may even provide some example macroses for different system's in compendiums.

I'm running an outdated version of Foundry at the moment (v11) and I've been interested in this module for a while, but I've hesitated to adopt it for my purposes because I'm hoping it can utilize more risk of failure or depend on the talents of specific characters.

Well, my efforts with this module as of right now are mainly on converting from foundry's soon to be deprecated AppV1 to AppV2 interface. Which mean's that Foundry v11 won't be supported after that. And i'll be honest, i have been neglecting this for a while... From coding perspective it's a complicated process. But it need's to be done sooner or later. And i tend to be lazy and work on this slowly...

You can still utilize the good old manual way of doing this. For check's - you can simply request your player's to make it before craft. For more cumbersome task's like crit successes you can utilize the "force craft" function. It does not consume any items, so you can ask your player's to manually adjust their item's the way you want to. I know this may not be very immersive, but it work's.

Creating interactive NPCs (like the Loot Piles module), in which certain categories of crafting can be handled. I'm interested in creating specific stations for crafting, and having a garage workbench for mechanics-related crafting and a stovetop for cooking-related crafting would be fantastic for immersion.

I may consider it for later. No promises. There are different way's to implement it and it's a cumbersome task. Selecting the best way to implement this can also be a challenge.
For example i think the best way would be to create a new actor type for a "workbench". It's rarely done by modules, but i think it's more versatile and cleaner than going the "Loot piles" way of overwriting actors UI or working with tile's like "Terminal" and "Tile triggers" modules do. Especially because there's no need to care about item's inside the workbench-actor, which is the main reason "Loot piles" overwrite UI in the first place.
Also this whole idea can easilly turn the "simple" in my module to "complicated". I am a bit hesitated to add functionality that requires a lot of setup from the user's side besides creating the recipes. Maybe i'll think about it later once i finish migrating to AppV2.

By the way. You can kinda imitate this behaviour in the current version of the module. You can create an item that serves as an "instrument kit". Then just place it as an ingredient in a recipe. It will consume it upon craft tho, and if it's not what you want you can crank it's quantity to a big number like "999" to not worry about it.

To summarise:

• I probably won't add any system specific mechanics but i do plan to add macro support
• Workbenches can be considered in the future, but i do not promise that.

That's all.