Talk:Game updates:September 2007
Please use the relevant update's talk page to discuss.
Yes! Love that they fixed the drop rate of Destroyer Cores! 『♥LadyTemp♥』 03:36, 5 September 2007 (UTC)
"Bug in which the hero's handbook doesn't update with the completion of the required quests, even when you beat GWEN."
What exactly is this referring to? Do you mean that sneak peak players who completed quests now have them show where they did not before? or is this something different? If it is the former then does it apply to dungeons completed too? --Bta 09:44, 5 September 2007 (UTC)
- Something completely different. Apparently this build -added- a bug that isn't recording primary quests into the Hero's Handbook. Had it fixed the quests the Sneak Peak players had done, my Handbook would be full right about now. Also, the HoM armor is still bugged. Dye on armor you are currently wearing still affects the dye on the armor placed in the Hall of Monuments, and you still can't place Silver Eagle armor into the Hall of Monuments.71.204.219.99 15:13, 5 September 2007 (UTC)
Pre-Searing Pulling[edit]
Thanks for fixing this. Finally we won't have to be worried about be pulled into Post.
bug[edit]
superior runes in armor dont seem to be reduceing health i dont realy know the exact problem so heres my armor setup elite charr hide armor (full) infused survivor insigneas on head boots and gloves raidient insigneas on chest and legs major rune of vigor on gloves sup rune of swordsmanship on headgear with +1strength sup tactics rune on boots vite rune on chest and minor strength rune on legs my weapon gives +24 health and sheild gives + 30 i may have missed somthing but this should be exactly 450 hp atm its 600hp....
- Doesnt matter if u did ur math right or wrong, it is impossible as far as I kno to run with a supirior and have more then a base 600 health. (660 is max so -75 is under 600) --72.74.237.104 02:44, 19 September 2007 (UTC)
- Wow. Misspelled words: dont reduceing dont realy heres insigneas raidient insigneas sheild vite somthing doesnt u ur kno supirior then. And the first poster doesn't understand punctuation. I know this is a talk page, but, c'mon. Proofread please. --72.211.152.118 03:20, 29 September 2007 (UTC)
update[edit]
how often is this updated
anti-leech[edit]
wootsauce -Desi 23:42, 27 September 2007 (UTC)
Brilliant feature. However, I have a question: I run a filtering software (CyberSitter, specifically) which occasionally blocks content in Guild Wars from downloading when zoning to new areas, meeting players in PvP with previously unencountered skills or armor, or updating areas and code. I can usually request a temporary disabling of the software if it's causing me trouble, but I do not always have access to that. So, the question: if I disconnect while loading a match, will I earn Dishonor points? Glenforder
- I don't know. Probably. But if you do get 10, it's only a short ten minute time out. :) No worries - Drago 01:29, 28 September 2007 (UTC)
Me and my friend spent at least an hour giggling at all the people complaining about this feature in Random Arenas, including people who hadn't read the update and thought they could pass off that the system was unfair, etc. People claiming that they were disconnected (or lagged out because anets servers are teh suck and lagged them out)then got dishonored were particularly amusing because it would have to be a recurrent thing before they get the time-out, yet they claim they did nothing wrong or didn't leave.
Also, quite a few people complained that you got dishonour for leaving after party was defeated and before the game auto ports you. Because I wanted to see the hex I tried this since it seemed the best way to get dishonor without actually screwing my teammates. Well 5 losses and immediate zone after, no disonour, anyone else able to reproduce that? 69.235.26.201 04:08, 28 September 2007 (UTC)
- Confirmed ^, when it says " Congratulations to the victorious ____ team ", in RA you can leave unpunished. --66.130.10.27 18:20, 28 September 2007 (UTC)
How about mid-match when your team's ranger uses firestorm and your whammo starts firing off orison of healing? That's where the biggest failure in this policy becomes apparent. -Auron 03:32, 29 September 2007 (UTC)
- Play TA then! No one's forcing you to play RA, are they? Learn to compensate for bad players and become a better player yourself. --82.33.10.119 05:42, 29 September 2007 (UTC)
- No one's forcing the firestorm rangers to play RA either. That logic is just about as flawed as it gets. -Auron 08:20, 29 September 2007 (UTC)
- Don't be ridiculous Auron. The point being that the other poster was complaining about the policy failing based on the Firestorm Rangers and Orison Wammos, due to him not being able to ragequit early obviously. Your response is silly and is completely off the point. --82.33.10.119 09:22, 29 September 2007 (UTC)
- "Learn to compensate for bad players and become a better player yourself." <-- last time I checked, monks can't kill the enemy team. I can only sit and heal these retards as they fuck around and die. The only thing firestorm rangers manage to kill is... oh, wait, nothing at all. Countering the badness of these players would basically take a prot/healing/smiting bar with a as-yet-unreleased 1 second res spell with no recharge, and a one-hit-kill spell so I can do the job the firestorm ranger is failing at. Please think through your comments before typing; Guild Wars is a team game, in PvE and PvP. A single character cannot turn the tides in the drastic proportions you're pretending possible (especially on offense when he's monking). -Auron 04:50, 30 September 2007 (UTC)
- Then don't play the RA, you belong in TA. It's called Random for a reason, and if you don't want to accept a random factor(Like teaming with a Firestorm Ranger), then don't play. I'm sure you'd rather fight the Firestorm Ranger(Which is why you cwant to ragequit and rejoin, so you get a superior team makup to kill said Firestorm Ranger and Orison Wammo). Either accept the random factor, or play TA. Your choice.69.119.169.41 16:26, 30 September 2007 (UTC)
- There's a difference between people who are bad and people who refuse to acknowledge the nature of GW as a team game by bringing res sigs, or running ridiculous self-defense bars that don't do anything useful. The first should be taught to play better; the second should not play. --72.211.152.118 06:50, 24 October 2007 (UTC)
- Then don't play the RA, you belong in TA. It's called Random for a reason, and if you don't want to accept a random factor(Like teaming with a Firestorm Ranger), then don't play. I'm sure you'd rather fight the Firestorm Ranger(Which is why you cwant to ragequit and rejoin, so you get a superior team makup to kill said Firestorm Ranger and Orison Wammo). Either accept the random factor, or play TA. Your choice.69.119.169.41 16:26, 30 September 2007 (UTC)
- "Learn to compensate for bad players and become a better player yourself." <-- last time I checked, monks can't kill the enemy team. I can only sit and heal these retards as they fuck around and die. The only thing firestorm rangers manage to kill is... oh, wait, nothing at all. Countering the badness of these players would basically take a prot/healing/smiting bar with a as-yet-unreleased 1 second res spell with no recharge, and a one-hit-kill spell so I can do the job the firestorm ranger is failing at. Please think through your comments before typing; Guild Wars is a team game, in PvE and PvP. A single character cannot turn the tides in the drastic proportions you're pretending possible (especially on offense when he's monking). -Auron 04:50, 30 September 2007 (UTC)
- Don't be ridiculous Auron. The point being that the other poster was complaining about the policy failing based on the Firestorm Rangers and Orison Wammos, due to him not being able to ragequit early obviously. Your response is silly and is completely off the point. --82.33.10.119 09:22, 29 September 2007 (UTC)
- No one's forcing the firestorm rangers to play RA either. That logic is just about as flawed as it gets. -Auron 08:20, 29 September 2007 (UTC)