Guild Wars 2

Shadelang.3012:

ATM there is only experience. Alot of us wish we could see there timers while in DS however.

As you play it more and more you start to get the timing down without needing to actively think about it. Being wrong about that timing though has a tendancy of getting you killed >.<

Been playing deathshroud tank for about 4 days, every time i leave deathshroud, if my heal skill is not up, its basically gg :I but the build has so much potential, lots of times chill messes my estimations so hard

Anyway other than counting to estimate the cool down of the utility skills when in death shroud?

Guys, if you payed attention in season 1, you would have noticed the clues. Caithe is obviously Zhaitan.

Human – all the classes
Norn – guardian
Sylvari – green party
Char – chinese food
Asura – eating char

Does anyone know how Mug damage shown on the Mug trait is calculated?

Note: Weapon strength is always average weapon strength in these calculations because changing the weapon strength range did not effect the Mug Damage while changing the average did. From this, Mug damage fluctuates because the Mug Damage shown on the trait is an average damage based on your weapon damage. Furthermore, Mug damage infers average mug damage from here on.

When weapon strength = 0,
Mug Damage = 0.3997(Power)
I plotted 7 points, the Y intercept is -0.4481 so its safe to say that it is supposed to be zero since plotting damage shown is rounded to the nearest integer. This concludes that a portion of the mug damage is not dependent on weapon strength and directly proportional to Power.

Let weapon strength = w

While changing weapon damage and power
Assumption: Mug Damage = 0.3997(Power) + c(w), where c is an arbitrary constant
This was not the case as W did not increase linearly with
When weapon damage was kept constant, c(w) was not constant

Let x = Mug Damage – 0.3997(Power)

This leads to 2 options,
1. x is dependent on w to some exponent
2. x is dependent on w to some exponent and power to some exponent
Mug Damage = 0.3997(Power) + c(Power)^m(w)^n

I assumed m to be 1 and as a result, c = 0.000158 when w = 952.5 for my 7 data points; however, when w = 1000, c = 0.000179

From this, I know that a component of c must be dependent on w

Mug Damage = 0.3997(Power) + c(Power)(w)^n

For c I determined the value to be very small ~10^-12, while for n I found a value of ~3.45, which is also unlikely.

I am highly doubtful that these are the correct values, but it is possible

Does anyone know the value of c and n? If you found a mistake please point it out, it is also possible that there is an if, then line that completely ignores the (power)0.3997 part when a weapon is equipped

Ex.
If weapon damage = 0
Then Mug Damage = 0.3997(Power)
Other
Then “something else”

I don’t think this is the case as well.

On the spreadsheet, MD/Power is actually x/Power, its just labeled wrong.
n is simply calculated using ln(x1power2/x2power1)/ln(w1/w2), c is calculated simply through substituting back in.

Arcades Saboth.5139:

Fynd.4890:

Order of operations :

Base damage for terror is:

• 2 + (level * 1.5) = 362 @ 80
• it is not (2 + level) * 1.5 = 123 @ 80

Infact: 80 *1.5 = 120 + 2 = 122.
362 would be 80 * 4 + 2.
Where did you get 362?

Is the maximum number you can have the the TP Delivery Box 100? What happens if you surpass the max if a max exists?

Unstable Light.3649:

Right click join squad? Not hard

How is this even relevant?

Is it just me or is the new commander tag one of the most annoying things on the map since the Sept 9th update? Should there be some sort of limit to the use of this commander tag? Although this problem obviously existed before the patch (just not as often), it doesn’t excuse the fact that there is no solution.

For example, if you are in WvW and you have this tag up with no intention of leading, should you be allowed to leave this up with no repercussion?

It is easy to ask that person to turn off their tag, but what if they do not listen or care about why the tag can be annoying?

I recently experienced a problem where I was doing Teq and there was this one player who had his commander tag up but did not stack with the other commander who was leading. We had a total of 6 minutes to burn; however when we returned from the battery event, this commander stayed in his position which was close enough to make people think that this was the stacking position for the burn; however, this wasn’t and I noticed this ([EDIT] and I tried to tell people not to stack on him). People got sucked into the vortex and we failed the burn. This commander was told to turn his tag off many times prior to the burn but ignored it every time. Although the Teq fail was not completely his fault, he still shared this blame of losing because of the new commander tag functions.

I’m sure I am not the only player who is annoyed by all the abuse of commander tags. My personal/unlikely solution would be to implicate a report system for the abuse of using commander tags.