API wrong for thick elonian cord
The Wiki, which uses the API, lists 200 Thick Leather Sections, with a total cost of a bit under 5 Gold each (to craft).
What do the other sites claim as cost?
That’s because Spidy doesn’t consistently use the API. It’s one of the oldest GW2 financial sites and the developer lost interest in the game before the current API launched. It looks as if the last “major” update to the site was over 2 years ago.
Other sites, such as the wiki and GW2 BLTC, do use the recipe API, which is why they have the correct amount.
The Wiki, which uses the API, lists 200 Thick Leather Sections, with a total cost of a bit under 5 Gold each (to craft).
Technically, the wiki doesn’t use the API for that particular type of information. It still relies on keen-eyed people to manually update the recipes.
It’s also why we appreciate the contributors who are continually fixing details from two, three, or even more major updates ago. A reminder that the other supported language wikis also need help updating the same information. The French wiki is still using an old name for Elonian cords, for instance..
The Wiki, which uses the API, lists 200 Thick Leather Sections, with a total cost of a bit under 5 Gold each (to craft).
Technically, the wiki doesn’t use the API for that particular type of information. It still relies on keen-eyed people to manually update the recipes.
It’s also why we appreciate the contributors who are continually fixing details from two, three, or even more major updates ago. A reminder that the other supported language wikis also need help updating the same information. The French wiki is still using an old name for Elonian cords, for instance..
I thought that the wiki used an API ‘scraper’ to periodically update items stats, canonical names, mystic forge recipes, discovery recipes, and learned recipes. Either that or that someone was manually spitting out the various JSON lists from the API into a form that the wiki could absorb. Not necessarily as to-the-minute accurate as some websites, but still pretty darn quick.
Regardless, the wiki has a big advantage over GW2 Spidy (which used to be my favorite site) and Dulfy: the wiki is crowd-sourced, which means there are always someone like Greener updating a correction (sometimes based on what was learned on the forums), whereas Spidy and Dulfy sites both depend on a single individual to update, which means lots of changes get missed. (Dulfy is, of course, a lot faster to post — she’s super methodical and gets help from her fans, including myself, which makes her site among the top resources.)
Oh, I thought the Wiki got the prices for items from the API.
I have/had no idea that recipes, other than the item ID or something, would be in the API.
My bad.
The Wiki, which uses the API, lists 200 Thick Leather Sections, with a total cost of a bit under 5 Gold each (to craft).
Technically, the wiki doesn’t use the API for that particular type of information. It still relies on keen-eyed people to manually update the recipes.
It’s also why we appreciate the contributors who are continually fixing details from two, three, or even more major updates ago. A reminder that the other supported language wikis also need help updating the same information. The French wiki is still using an old name for Elonian cords, for instance..
I thought that the wiki used an API ‘scraper’ to periodically update items stats, canonical names, mystic forge recipes, discovery recipes, and learned recipes. Either that or that someone was manually spitting out the various JSON lists from the API into a form that the wiki could absorb. Not necessarily as to-the-minute accurate as some websites, but still pretty darn quick.
Oh, we do have amazing people who are able to gather data from the API to look for changes, and people who can run bots on the wiki to update said changes. Thanks to them, more and more things are becoming less and less manual (and therefor outdated). There are also other pieces of information, like Trading Post prices, which are gathered on demand from the API. I don’t want to take away from the processes that they are building even as I type. If people do see something that looks out of date (like the OP), do let us know. Not everything is on the wiki is 100% accurate .
Such systems are not necessarily built into the other official wikis, though. Nudge, nudge. There’s gotta be some bilingual geeks that read through this section of the forums.
Dulfy is, of course, a lot faster to post — she’s super methodical and gets help from her fans, including myself, which makes her site among the top resources.
Dulfy’s dedication and quality of work is unmatched, and she raises the bar for everyone.
Anyways, I fear I may continue to talk off-topic.
Why does spidy say they use the api in big green letters if they don’t i don’t understand it.
Why does spidy say they use the api in big green letters if they don’t i don’t understand it.
You’d probably have to ask the creator/person who maintains that site. ArenaNet can only offer the resources; they can’t make people who create apps take advantage of them or keep their apps up-to-date.
Good luck.
Why does spidy say they use the api in big green letters if they don’t i don’t understand it.
They use the old API, which didn’t include all the recipes.
Prior to that, Spidy ran a manual process to scrape prices (there was a URL you could type to get prices from the TP). (The process ‘crawls’ the web looking for data, so it’s called a Spider, which is the source of the website’s name.) The ‘Spider’ depended on having a reliable list of items to check for and on the website’s server being able to maintain it — both those things tended to fail occasionally, leading to gaps in coverage (usually lasting only a few hours, but sometimes, lasting weeks or longer).
Some time after the original API was launched, GW2Spidy finally made use of it, which was a huge improvement for the website. It became 100% reliable rather than 90% (or less), or at least, as reliable as the API.
Accordingly, it deserved a huge announcement on the front page of the site, because it was such a major improvement in coverage.
Unfortunately, the developer wasn’t able to keep making improvements and so Spidy doesn’t make use of the current API.
tl;dr announcement of use of the API was accurate at the time it was made; things have changed since and Spidy can’t keep up.
@Greener: perhaps it’s time for the wiki community to consider dropping Spidy from the list of auto-links on every article for item’s with a TP price.