Guild Wars 2

Hello everyone,

I was wondering if someone could tell me what the current gold amount is needed to acquire 1800 gems (the cost for a server transfer)

https://www.gw2spidy.com/gem

Currently, as I write, 100 gems costs 19.99 gold to buy.

1800 gems =X gold
100 gems =19.99 gold

1800 gems divided by 100 gems = 18
18 times 19.99 gold = 359.82 gold

Of course, that amount of gold will be different by the time you try to buy gems and you will need to redo the math.

At this precise moment, it is 339g 40s. At least according to currency conversion.

Right now 100 gems costs 20g71s

So, 18 times that… 372g78s

Too much.

Tew much ’_`

Just a flesh wound.3589:

https://www.gw2spidy.com/gem

Currently, as I write, 100 gems costs 19.99 gold to buy.

1800 gems =X gold
100 gems =19.99 gold

1800 gems divided by 100 gems = 18
18 times 19.99 gold = 359.82 gold

Of course, that amount of gold will be different by the time you try to buy gems and you will need to redo the math.

Spidy has been wrong (reports higher costs for gems, lower for gold) for quite some time when it comes the exchange prices, since last August, it’s listing 100 gems at 19.74g. GW2TP is much closer to the actual cost per 100 gems. The API even closer.

Or you go to the exchange in game, click on the custom button and actually see what 1800 gems will cost you. And remember it’s a different rate than what you get selling 1800 gems.

You can find it out in game. Open up the TP, switch the conversion tab (second one, on the left). On the lower right of the panel, choose “Custom Exchange”. Type in the amount of gems you want.

As I type, it’s 326g 5s 54c, which is high relative to the last 48 hours, since gems are trading at 18g 16+/100 gems and ‘last night’ they were trading at 16g50 or so. (Plus a month ago or so, you could still get 100 gems for less than 14g, if you chose your time carefully.)

Behellagh.1468:

Just a flesh wound.3589:

https://www.gw2spidy.com/gem

Currently, as I write, 100 gems costs 19.99 gold to buy.

1800 gems =X gold
100 gems =19.99 gold

1800 gems divided by 100 gems = 18
18 times 19.99 gold = 359.82 gold

Of course, that amount of gold will be different by the time you try to buy gems and you will need to redo the math.

Spidy has been wrong (reports higher costs for gems, lower for gold) for quite some time when it comes the exchange prices, since last August, it’s listing 100 gems at 19.74g. GW2TP is much closer to the actual cost per 100 gems. The API even closer.

Or you go to the exchange in game, click on the custom button and actually see what 1800 gems will cost you. And remember it’s a different rate than what you get selling 1800 gems.

Didn’t the guy who designed spidy stop playing and updating that site? Maybe that’s why it’s inaccurate then.

how can something be wrong that is taking the data directly from the API, if anything, it is just delayed by a little bit, because it does not refresh in real time.

party buddy.4956:

how can something be wrong that is taking the data directly from the API, if anything, it is just delayed by a little bit, because it does not refresh in real time.

Possibly because the API shows a non-linear aspect to the exchange and Spidy is using input values to low. The current API only has a “how many gems can I get for X coins”.

For instance I’ll try to use the API to quickly get the rate for 1g, 10g and 100g (primed in three tabs and rapidly switch between them and hit return).

1g reports the rate as 20.00g per 100 gems (5 gems)
10g reports the rate as 17.85g per 100 gems (56 gems)
100g reports the rate as 17.60g per 100 gems (568 gems)

You can see that the per 100 price that the API returns is simply the amount you entered divided by the amount of gems that it will buy, disregarding any excess you paid.

The problem started when the new API came out. I don’t remember if the old API worked similarly or if it was more logical and you inquired the cost of X gems and got an exact amount of coin down to the copper.

You almost need to set it up recursively with the first result giving you the ballpark value to inquire a second time to get a more accurate result.

I’ve run spot checks on the API when spidy seems “off” — and spidy is off from what the API is telling me (on those occasions).

GW2Spidy queries roughly every 5 minutes and the day chart shows that. GW2TP queries every 1/2 an hour. If you compare the two numbers you will see a major difference at similar times.

Now at UTC 5:13 the API returned 17.24 gold with a 20 gold query. GW2TP has it’s UTC 5:13 price at 17.21 gold while GW2Spidy has it’s UTC 5:12/13 price at 18.89 gold.

GW2Spidy may be using the API but the value is high. I probably can figure out the query amount it’s using based on the values it’s charting if I put my mind to it but I think I demonstrated in my previous post that it’s currently well below the current 100 gem price so the number of gems it returns is well bellow 100 gems so the simple query price / gems received is causing significant error.

In short if you can’t fire up the game to check the current rate using the exchange itself, use GW2TP to get the price within the last half an hour or the API with a large enough coin query, like 20 gold (200,000 copper) for a more up to the moment price. GW2Spidy is inaccurate after Aug 10, 2014. It shows trend, up or down, but that’s it.