User talk:69.242.196.134

Waiting for an answer

You asked the same question in three different places. I reverted two. John Stumme is actively responding to posts and the question falls into his area of responsibility. If, for some reason, he does not respond (or other contributors do not offer alternative thoughts on the topic you raised), it might be worthwhile to contact others. Posting the same question repeatedly tends confuses the issue(s) and can delay a response. In the meantime, please be patient. Thank you.  — Tennessee Ernie Ford (TEF) 22:54, 19 February 2011 (UTC)

Ranged Weapon Glitch

→ moved from Feedback talk:John Stumme

John, I was wondering about the Ranged weapon Glitch on this page http://wiki.guildwars.com/wiki/Feedback:Bug_reports/Miscellaneous_bugs#Ranged_weapon_glitch_.28Obstructed_on_Bridges_and_Stairs.29 This has been in existence for so long, and been begged for fixing, I was wondering if you might address this issue? I bring it up here because I don't consider it just a small benign bug. This bug directly affects all Ranged weapon attacks and at times can cause major issues affecting game play and Ranged attackers efficiency. 69.242.196.134 20:43, 12 May 2011 (UTC)

There is no z axes for gw1 thus that bug will never be fixed.- Zesbeer 21:23, 12 May 2011 (UTC)

...What does it have to do with a z-axis? — Raine Valen 22:13, 12 May 2011 (UTC)

Has nothing to do with a Z axis, it didnt use to be in the game, if you read the post I noted it was introduced as a bug in an update long ago. But hey, No need to read the posts before you actually comment right? HungryArmadillo 22:19, 12 May 2011 (UTC)

(Reset indent) clearly i am the one who cant read: "It is possible for there to be areas that obstruct your view when they should not do so, but without specific maps and locations (preferably with the U map showing where you are in the map) we cannot fix them. If you can provide more details, I will be happy to get this looked at for you --Andrew Patrick 19:06, 6 January 2010 (UTC)"

"Some of the cases you guys are citing are legitimate times when you do not have Line of Sight. Yes, eles can cast spells that don't require line of sight when they do not have line of sight of their enemy, and yes, you cannot hit them if your attacks do require line of sight. Also keep in mind your foe having line-of-sight with you does not inherently mean you have line-of-sight with them, primarily at times when they have the high-ground. This is true in real life as well, which is why defending archers in towers/on walls could pew pew all day long without a significant risk of sustaining a hit from returned fire from below. Not to say every time a bridge or staircase acts funny it's intentional, I'm just saying it's not always a bug. "

"There are indeed times when a prop's line of sight extends past where the actual prop appears on your screen and I am by no means disagreeing that these issues do appear in the game. I simply want you to differentiate when you should and should not be obstructed. When these issues are reported they are fixed on a case-by-case basis, but in order to do that we need details about where the problem is occurring. Preferably with images. Pretty much every prop in every map has individual LoS/obstruction associated with it so the more specific information we have, the easier it is for us to locate the problem and have it resolved. Thanks! --Andrew Patrick 20:36, 9 March 2010 (UTC) "- Zesbeer 23:42, 12 May 2011 (UTC)

There are screenshots all over the linked thread. Did you even look at it? — Raine Valen 0:40, 13 May 2011 (UTC)

The main problem is that GW lacks a physics system. I hope it lacks a physics system, as the alternative is that the extant physics system sucks donkey balls. This isn't a bug that's going to be fixed, as fixing it with any degree of competence, correctness, or satisfaction would require re-writing the entire 3D graphics engine and the way projectiles calculate path trajectory, a project which would be at least as large as GW2. Now, in a few posts, assuming some admin in the middle of gargling on ANet's collective manhood doesn't move this page elsewhere, John is going to step in and deny this truth. He'll say something like "archers can't shoot up walls you jackass" or "even characters screw up sometimes," trying to justify this as a feature instead of a problem. That's because company policy is never to admit something is wrong unless it's already been scheduled for fixing. –Jette 00:49, 13 May 2011 (UTC)

For the cases that are actual bugs, I think this is caused by a mis-matching of the object's graphics (e.g., details), and the collision of said objects. For instance, you know where there are steps where you can "float" just off of them (e.g., Serenity Temple)? That's the same issue. The images are not lined up with the actual placement of the object (I don't know what the technical terms for such things would be). In turn, these have to be fixed on a case-by-case state. Will they be fixed? Sure, if they're accurately reported and the devs have time. Will they all be fixed at once? Is it one thing to fix? No. If you want every case fixed, you'll have to go and test and document every single corner of GW and report with said documentations which spots are bugged and how to recreate said bugs.

In short: It is possible to be fixed, but so tedious to fix it's improbable (I feel like linking the scene in Pirates of the Carribean when they say its not possible for Jack to be alive then he goes "not probably" - same situation :P). -- Konig/talk 01:04, 13 May 2011 (UTC)

Hi Jette, stop being a dick. -Auron 07:17, 13 May 2011 (UTC)

I don't think it is John's task to fix this. There are the people who made 'it' and those people are more at home with the nooks and crannies of the buggy system, so go and find them. Hope it won't be THIS bad in the gw2. --Boro 16:50, 13 May 2011 (UTC)