Fixing Net Shot : I need your help
Other stuff gets randomly obstructed too. Like pin-down. Just less often.
Yeh, that’s pretty much the point. Far less often.
It’s all depending on projectile speed and Net Shot is probably the slowest projectile in-game. Hence the problem. Hence my asking for a change
I gotchu uhta<3
I troll on all classes in gw2 and by far net shot is the most buggy kitten in the game(even mor than ele dagger3 in earth)
Anet plz
Plz
Plz
Plz
Welp I guess engineers don’t care about Net Shot, you just need to post on the topic I linked but I find it funny that nobody cares about a skill being bugged when we only have 3 weapon sets.
cause it’s not the only one, and – in addition – a well known issue with the game mechanic.
the skill is not homing and fires in an arc.
Actually it does not even get obstructed in most cases, it’s simply that there is only one flag for projectiles that did not connect: “obstructed”. In reality your target switched direction or movement speed, making it impossible for netshot to hit your target where it “should” be. Ofc terrain can destroy a projectile as well, making it also impossible for it to connect, hence the “obstructed” screen-print.
“missed” is occupied by the condition that you hit a target while blinded, while “evaded” is occupied by the condition that your target dodged in the right moment.
Basically the Gw2 engine is missing a flag for projectiles getting destroyed due to them reaching their maximum distance, hence you get the screen-print “obstructed” both for projectile death and -terrain block.
This is basically an issue for all projectiles in the game who are too slow to connect reliably, like Elixir F, FT #2, Guardian staff #2, a.s.o.
(edited by Arantheal.7396)
I can see you didn’t read the topic I linked, that’s nice. I never claimed it was the only one but that doesn’t mean we can just ignore it. I would also argue that the other skills you named are not as necessary for the mentioned weapons that Net Shot is for rifle. Simple because rifle is clunky and would greatly benefit from having a reliable Net Shot.
In any case, I don’t see the problem in letting anet know that we’d like to know their stand on the matter
Yea, I totally didn’t read a post about a topic I typed a in-depth explanation in…
And I don’t see why you would want to open a topic about a skill that suffers from a engine wide issue in the engi subforum.
That’s what the bug-report function is for, or the technical subforum.
You can find a dev post about misplaced bug reports on top of this sub-forum as well.
If you want to buff net-shot for higher projectile speed, then the answer on the matter will be something along the lines of the following: “We’re currently reworking the whole trait-system of the engineer, while going trough a mayor re-balance phase for all classes. We can not give you information about how any skill will turn out to function in particular, simply because we don’t know it yet with certainty. We appreciate your effort, and would like you to stay tuned for the next ready up / POI, to ask the dev’s directly (a.k.a. try to go trough the white noise of a thousand pointless posts per minute, given that they even scratch your topic)”
(edited by Arantheal.7396)
You pretty much said what I typed in prettier words so either :
1) You didn’t read it
2) You were being condescending and took the liberty to explain to me something I already knew
I assumed the former but it seems it was the latter.
I open a topic in the engi subforum about a topic in the bug subforum because not everyone reads the bug subforum
“2) You were being condescending and took the liberty to explain to me something I already knew”
You are not interesting enough to recherché about what you know or not, I was responding to the topic at hand, paying minor attention to the original poster. Until now.
The dev’s (or forum specialists) read the bug subforum, and these are the people which you want an answer from.
This topic is old and got discussed in numerous threads, and a quick use of the search-function could have revealed this for you. Instead you double-post – and further – act very unfriendly to any person that is not praising your very own (unnecessary) initiative, here, and in the other thread…
You know, obnoxious smilies don’t hide a lack of manners.
Anyways, I’m not interested enough in you to continue this beyond this point.
You are free to post whatever (that is not going against the TOS), but please understand that most will not praise you – nor join some weird campaign – over topics that already got dev-attention, just because it’s not going quick enough for your personal taste.
Farewell.
(edited by Arantheal.7396)
As someone who once curated a list of Turret issues (almost all of which have since been resolved): The devs won’t respond for a long time, if at all. Certainly not within nine days. They don’t. It’s just not how they do things. Did you notice how few posts on the bug board have a dev bubble? It’s far more than on most boards, for the first two pages, but every thread they’re posting in have views numbering in the thousands.
To get their attention to my thread, I essentially made a master-list of bugs affecting Turrets. I made secondary threads to report each bug, permalinked to them in the master thread, and kept compiling. And compiling. If you want them to post to your thread, or otherwise get a ‘We have our eyes on this issue,’ you can’t just try to wave and go “THIS ONE THING IS BROKEN.”
Odds are, they know about the thing being broken, and there’s just not enough hours in the day to go to every single bug thread and go “Hey, thanks for letting us know, for the umpteenth time, that this thing is broken.” Give them a reason to pay attention – maybe make a master-list of the various bugs afflicting Engineer weapons, if you really must try to get them to post. It adds value, if nothing else, because they can just look at the masterlist if you’re keeping on top of it.
Also, side-note, the search function on these boards has never worked. It’s kind of ridiculous, at this point.