Fearthebuns Stream: Ursinites
- Thread starter Hunnybuns
- Start date
Revlo
A Sentient Pyramid
I'd say warrior or mage HB. Both are classes that I don't play, but have level 1s created an ready to go. It's always nice to get an idea of potential while getting into them.
Also, Bop and Sidney, I ran into the same thing in regards to playing healing specs. I started out my playing as dps specs and then got tired of having too few healers on my team in a good number of PuGs. In the end, I really liked healing so it worked out. I still get frustrated when I play a tank or dps and we might get 1 healer.
Sent from my iPhone using Tapatalk
Also, Bop and Sidney, I ran into the same thing in regards to playing healing specs. I started out my playing as dps specs and then got tired of having too few healers on my team in a good number of PuGs. In the end, I really liked healing so it worked out. I still get frustrated when I play a tank or dps and we might get 1 healer.
Sent from my iPhone using Tapatalk
OP
OP
Tyramissoux
Legend
Sorry I missed it. You were singing a lot with HB. Cursing and singing like a modern-day Marlene Dietrich.(Also lol at cat-whispering.)
You really think that was a lot of singing? Buddy... you have no idea....
Goesid
Twink Info Legend
OP
OP
You see about that....
A mishap video for the ages! Had a lot of fun tonight with BWL and Mok'Nathol and friends! This sums up the night
Sponsor
Achievement Hunting
Oh lord, thats the fail you were referring to when you asked me earlier... Hadnt noticed lol. Wish we could see the rogue's POV
Zehj
Legend
what happened was the rogue blocked the oop, so I passed it back out to the 3 point line, but then my team let me down
Bop
Remember the Treeline
I can't... I can't even... Blizzard needs to be more involved with fixing obvious gameplay errors in their battlegrounds.
A flag despawning with carry-able people in the immediate vicinity seems to be kind of bad gameplay. Granted, the situation that happened in this video is probably the .01% of all WSGs in terms of a flag timing out just as you get to it.
The worst offender, in my opinion, is a flag node in AB capping while people are trying to defend it. I personally believe the flag cap timer should stop if people are defending the flag, and that each player should have about a 5 second debuff after trying to defend a flag that prevents them from doing so again.
Bop
Remember the Treeline
But then that would remove all the fun of ninja'ing flags
Well, a rogue 1-man sapping to force a flag cap without any risk to himself is kind of sketch as far as balancing goes.
Besides, with the debuff he could still do so. It's just he wouldn't be able to count to 5 in his head before each sap to waste the maximum amount of time.
Revlo
A Sentient Pyramid
TBH, HB I had to look at the vid a couple times to figure out just what went down. I most likely would've missed the drop as well. Nice grab and jump on Zehj's part there. The rogue could've had a nice return there as well, heh.
Also, the thing that bothers me the most out of flag craziness is in AB, when you go to reclaim a node that has been assaulted and is in transition. Let's say it is within 6 seconds of being transitioning to the opposing team. It drives me nuts when I click the flag, start capturing the flag or "defending" it, and then because the timer for the opposing team to "claim" it hits 0 before my capping takes it, it interrupts my capping and I have to start all over again. If I run up to a flag that is in transition like that with up to 7 seconds left, I just don't even click it anymore until it switches, otherwise it's just a waste of time. It would be nice if it didn't interrupt me and allow the capture to finish. This could be altered to just change the result of the capture from a "defend" to an "assault", instead of the annoying, time-wasting interrupt.
Also, the thing that bothers me the most out of flag craziness is in AB, when you go to reclaim a node that has been assaulted and is in transition. Let's say it is within 6 seconds of being transitioning to the opposing team. It drives me nuts when I click the flag, start capturing the flag or "defending" it, and then because the timer for the opposing team to "claim" it hits 0 before my capping takes it, it interrupts my capping and I have to start all over again. If I run up to a flag that is in transition like that with up to 7 seconds left, I just don't even click it anymore until it switches, otherwise it's just a waste of time. It would be nice if it didn't interrupt me and allow the capture to finish. This could be altered to just change the result of the capture from a "defend" to an "assault", instead of the annoying, time-wasting interrupt.
Last edited by a moderator:
Bop
Remember the Treeline
that's my complaint (and solution to this problem) that I listed just a few posts above.
Bop
Remember the Treeline
Ya know, I had a feeling it might be, I just couldn't quite nail down if that's what you meant, hehe. /highfive
Edit: Yeah, is see it clearer now.
It's always been a huge problem. The first time I ever got my defend-100-nodes achievement in AB, I probably lost about half of the caps to this.
It's just extremely likely that you will be defending a flag that is about to cap, since you probably had to wipe a small group of enemies before being able to defend.