Guild Wars 2

so i don’t really have any pictures to show, but this seems like an easy enough bug to repro.

the gist of it is that after i lay the static field, if i run away from it (or even if i lay it too far away), i’ll get “out of range” from enemies going through it, instead of actually damaging, as if the calculation checked the range after the field was laid as well as before.

i imagine that to reproduce it, you’d just have to ask someone to go through your static field while you’re far away from it, and then have the person go through it while you’re close to it.

additional data: have only noticed it today (though i haven’t played my ele since way before the last free trial), while playing on the WvW green borderlands, against a moderately sized group (5-10 people, half of which went through my field only for me to see “out of range” popping over them). i have blasting staff traited.

EDIT: check the 4th post for more information.

Happened to me last night, I do NOT have blasting staff traited, but still got the same Out of Range error after laying a static field and using burning retreat.

Shouldn’t these function like necro marks? Has anyone noticed the same issues with any other AoEs from the staff?

i tried to pay attention, but i haven’t really noticed it doing that with other AoEs. it definitely does not affect the glyph of storms (attuned to earth), but i don’t think i got to test on other AoEs from the actual staff (since i was playing around with frost bow for the most part, after laying my static field).

UPDATE:

tested the bug on the heart of the mists. no traits, no armor, no sigils, nothing except the PvP staff straight out of the vendor.

what i found:

• this bug happens regardless of having blasting staff traited or not
• this bug only affects static field (though i only tested static field and lava font, i must say)
• static field works as intended when within range
• static field will still stun, but not damage, an enemy that passes through the static field while the elementalist is out of range.
• a single dodge roll back after casting at max range is enough to make the field not damage a person entering the field from the furthest point away from the elementalist.

so in short: this bug affects exclusively static field. the problem is likely within the skill’s coding, probably due to calculating the range check based on the elementalist’s current distance from the target. the range only affects the damage part of the skill, not the stun. reproduction is as easy as casting static field from max range, dodging backwards, and having someone go through the field.

Will this fix also mean I can drop static from on top of a tower/keep wall, drop to the other side and not just get “Obstructed” if someone walks through it?