Guild Wars 2

Since my server went down in rankings to servers that sucks in WvW, I would like to take this time to research about traveling in WvW since my server capped every single objective in WvW before my server fight the bigger leagues.

The purpose of the thread: I want to know more about the mathematics in traveling in WvW before I waste time that has already been researched. Like, how long will it take to get from tower a to tower b. How long is it from point a to point b. How fast does a character move at without swiftness? The radius of the lake in each Borderland. The average rate it takes to take down an unupgraded/upgraded tower or keep while undefended. What is the gate/wall’s hp? etc etc…

Why it matters: Mobility is one of the key part of WvW. If there was a more information on mobility, commanders can easily judge if they can make it in time or not. Commanders can also see crossed swords on the map and judge if they can take over this keep/tower before the zerg comes in. After all, war is ruled by logistics.

Goals: Create a website that allows commander to inputs two points and outputs the time it takes to reach there, for example, If a Commander orders everyone to rally at Ogre camp, he can use the website to determine how long he should wait for. The commander can also use it to determine if resupplying is worth the trouble. Another goal is to create another website where commanders input data and the program outputs results if they can save the tower/keep possible. Obviously is there for heroic saves or ninjaing keeps/towers.

I’m willing to wager that the time it takes to travel from A to B on one map, will average out to a trivial difference compared to the time it would take to switch to this app, submit the data and get the result.

This reminds me of the “supply camp” timer project someone started… the windows of time involved are simply too narrow for this info to be that useful in practice.

runeblade.7514:

Since my server went down in rankings to servers that sucks in WvW, I would like to take this time to research about traveling in WvW since my server capped every single objective in WvW before my server fight the bigger leagues.

The purpose of the thread: I want to know more about the mathematics in traveling in WvW before I waste time that has already been researched. Like, how long will it take to get from tower a to tower b. How long is it from point a to point b. How fast does a character move at without swiftness? The radius of the lake in each Borderland. The average rate it takes to take down an unupgraded/upgraded tower or keep while undefended. What is the gate/wall’s hp? etc etc…

Why it matters: Mobility is one of the key part of WvW. If there was a more information on mobility, commanders can easily judge if they can make it in time or not. Commanders can also see crossed swords on the map and judge if they can take over this keep/tower before the zerg comes in. After all, war is ruled by logistics.

Goals: Create a website that allows commander to inputs two points and outputs the time it takes to reach there, for example, If a Commander orders everyone to rally at Ogre camp, he can use the website to determine how long he should wait for. The commander can also use it to determine if resupplying is worth the trouble. Another goal is to create another website where commanders input data and the program outputs results if they can save the tower/keep possible. Obviously is there for heroic saves or ninjaing keeps/towers.

That’s kind of silly when you consider the many other factors that come into play when making such decisions. It’s kind of like wanting precision to two decimal places when you can only choose a whole number between six and nine. And what good does it do to know to the second how long it takes to get from point A to point B when you don’t have ANY idea what represents being “in time” since that is a function of what the other side is doing.

Besides, any commander worth his sigil has a pretty good idea of how long it takes to get anywhere on the map anyway … certainly to the accuracy that would be relevant.