Guild Wars 2

Hi, ever since the update recently ori has stopped spawning and I have scoured the maps, as well as checked node sites to find them. They are never there and im getting confused. Did something happen to ori nodes and ancient nodes since this patch that we are not aware of or is this an isolated occurrence. I need my moneys and this is a big setback…

They are on timers. Also I believe when new builds are released the nodes are reset and most likely appear somewhere else.

Ori and saplings are on daily cooldowns per character. Example: you mine an ori node on a thief, you can’t access that node until reset (5PM server time) or you can switch to another character and mine that node.
Also, every new build moves resource nodes, so whatever site you’re using to track the nodes are probably still gathering info/not up to date.

Maybe it’s a coincidence, but yesterday I ran through the Orr maps on my server [RoF] and I didn’t found any orichalcum ore. I found many orr saplings though.

There are usually some bugs and problems with the nodes after builds and updates, I’d recommend to wait a few hours after a new update.

Pages like this are often helpful to look where the nodes are after an update.

http://www.gw2nodes.com/

There were actually 3 updates over the past few days that cause a LOT of confusion on these nodes. The site above (gw2nodes.com) was VERY incorrect for my server (Yak’s Bend) for quite a while during the confusion.

As of last night, all locations checked out for me.

Brother Grimm.5176:

There were actually 3 updates over the past few days that cause a LOT of confusion on these nodes. The site above (gw2nodes.com) was VERY incorrect for my server (Yak’s Bend) for quite a while during the confusion.

As of last night, all locations checked out for me.

The spots on that page have of course to be updated by players. So short after a patch you should maybe wait for a while and click on the spots to check the date when it was last updated.

Beldin.5498:

Brother Grimm.5176:

There were actually 3 updates over the past few days that cause a LOT of confusion on these nodes. The site above (gw2nodes.com) was VERY incorrect for my server (Yak’s Bend) for quite a while during the confusion.

As of last night, all locations checked out for me.

The spots on that page have of course to be updated by players. So short after a patch you should maybe wait for a while and click on the spots to check the date when it was last updated.

The site is missing a crucial feature. It should automatically clear all node locations after a new build. That is fairly easy to track with the API.

New builds will change node locations but they will not reset the nodes.
Nodes respawn in around 8 hours, not a full day.

Even T6 nodes? I know that the other ores/saplings respawn more than once a day, but I figured that the ori and saplings were daily

Yeah, I know GWnodes.com is updated by players and can be a PitA to keep 100% accurate during update periods. It also doesn’t help that the map overlay itself seems to be a tad buggy and I often have to reload the page several times to get a valid display (the site DOES say BETA all over it, so I’m not complaining…..it’s a highly useful resource in general).

I’m not exactly sure of the resupply timing, but I have noticed that T6 nodes seem to take longer to resupply than the lower tiers. I’ve seen plenty of other players indicate the same observations.

Mystic Starfish.2586:

Even T6 nodes? I know that the other ores/saplings respawn more than once a day, but I figured that the ori and saplings were daily

Around 8h for t6, 1h for others.
Possibly 24h for rich veins and plant patches.
Most people won’t play enough for it to really matter.

I do Frostgorge daily for ori and saplings. What I’ve seen is they respawn at reset, unless you harvested them less than 6 hours before reset, then it’s reset plus early harvest time. For example if you harvested them 5 hours before reset it’s reset and one hour, 4 hours before reset it’s reset and 2 hours.

Very rarely they may respawn again about 8 hours later, but that’s probably a bug.