Guild Wars 2

Hi there, currently working on a little solo project, where the plan is to add items that I want to craft into a list that will be displayed in a overlay. This works for regular crafting recipes like the crystalline ingot. But for the mystic forge there is no way to get any recipes. Will those recipes be added sometime soon, or should I make it so those items have to be managed manually?

I don’t know how up-to-date this answer is, but there was a post here 4 months ago about a user-created json mystic forge recipe list.

As far as I know there is no access through the official API, but that user file provides a nice alternative.

edit: link to the host’s domain where it’s stored/explained: http://gw2profits.com/json

Thanks! I’ll be sure to check it out

Alright, thanks for the answer =)

Would it be possible to create an endpoint of “generic” MF recipes that are discovered, or are at least already available on the wiki? Such as the Gifts, promotions, side-conversions (stats), etc, where instead of the massive inputs, it’s more along the lines of text output itemizing the “ingredients.”

As for the timetable, I’d say that once it’s put on the wiki, release it in the API, as once it’s on the wiki, it’s likely to spread to a large number of players.

Lawton Campbell.8517:

Aidan Savage.2078:

As for the timetable, I’d say that once it’s put on the wiki, release it in the API, as once it’s on the wiki, it’s likely to spread to a large number of players.

I can do that. The API endpoint would basically proxy the wiki’s semantic search for mystic forge recipes; will need to look into it a bit to figure out how the semantic search bits work.

This would be great (and substantially address the concerns I raised in the post Lawton linked above). Looking forward to seeing it.

Though it does bring up an interesting conundrum- should it just be recipes that have defined (semi-defined for promotions n stuff) inputs and outputs (ie actual recipes that use the forge as the “workstation”), or should it be all mf recipes that are currently known on the wiki? For ones such as the random forging of equipment, I understand why those you would be reluctant to do. That’s partially why I suggested having those recipes essentially be generic in format:

//Mystic Forge recipe
{
type: "Exotic Weapon",
output_item_type: "Weapon", //this format would necessitate a couple new fields probably,
// but should be workable, being a new endpoint
output_item_count: 1,
ingredients: [
{
input_item_type: "Weapon",
input_item_quality: "Exotic",
count: 4
},
],
id: XYZ,
}

Recipes for the random forging would have two “duplicate recipes” as a result of being able to get a given quality level by using an equal quality, or the one immediately preceding it. This would mean that, instead of 9999999999999999999999999999999 recipes, you’d have…. 19×2×4plus19 for specific weapons (2 for each quality level besides basic, just 1), and then 9 “generic” ones that are basically 4 random weapons of a given quality. Armor is…. 18×2×4plus18 and the 9 generic as well I believe. Trinkets are similar as well. Still a hefty amount of work, but substantially easier than having to itemize everything.

edit: stupid shortcut formatting

Aidan Savage.2078:

Recipes for the random forging would have two “duplicate recipes” as a result of being able to get a given quality level by using an equal quality, or the one immediately preceding it.

I don’t think this is going to work like you think it will.

The wiki uses templates to convert the ingredient information into the visual format you’re familiar with. This is also how it stores that information. I figure this is what the API is going to be accessing – the data stored in the templates. If a particular combination isn’t written up in template form, but is explained verbally (like this stuff probably is), the API isn’t going to see it and won’t be able to report it.