Abusing the range of melee cones.
[ QUOTE ]
That was more of a PvP issue and how Auto Follow works, and Auto Follow is the best way to deal with moving foes in pvp if you are melee. Not that it made huge difference there, you still have to rub shoulders but now you don't have to do it so darn close.
[/ QUOTE ]
This was most certainly not a PvP issue on pre-release weekend of CoH. The problem I describe came out with the game and persisted for a decent while. I don't remember when they actually fixed it.
I do not now and did not ever use autofollow on mobs. It was not an issue spcific to autofollow.
[ QUOTE ]
In pve it was just a bonus as pve critters rarely move a much.
[/ QUOTE ]
You do realize that we're talking about "runners," right? By definition, those are mobs that move, and move away from you. Hitting mobs that stood still was never an issue.
Blue
American Steele: 50 BS/Inv
Nightfall: 50 DDD
Sable Slayer: 50 DM/Rgn
Fortune's Shadow: 50 Dark/Psi
WinterStrike: 47 Ice/Dev
Quantum Well: 43 Inv/EM
Twilit Destiny: 43 MA/DA
Red
Shadowslip: 50 DDC
Final Rest: 50 MA/Rgn
Abyssal Frost: 50 Ice/Dark
Golden Ember: 50 SM/FA
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
To be more precise: it was an issue with Gauntlet in tankers (and to a lesser degree all targeted aoe attacks with very small radius.) True single target attacks never had the "impossible to hit moving targets" issue.
[/ QUOTE ]
Single-target attacks had a different issue. You couldn't get them to activate reliably. You could queue an attack and chase after a running opponent, and it was significantly unlikely that the attack would actually activate unless you ran past the opponent, rubbing shoulders with it the whole time.
[/ QUOTE ]
That was more of a PvP issue and how Auto Follow works, and Auto Follow is the best way to deal with moving foes in pvp if you are melee. Not that it made huge difference there, you still have to rub shoulders but now you don't have to do it so darn close.
In pve it was just a bonus as pve critters rarely move a much.
[/ QUOTE ]
...
Issue 0, release, whatever the hell you want to call it, had PvP? You still aren't getting it.
Blue: ~Knockback Squad on Guardian~
Red: ~Undoing of Virtue on [3 guesses]~
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
There goes your chance at the bug hunter badge
[/ QUOTE ]
If I thought badges were worth anything I might find that disheartening.
[/ QUOTE ]
It's also not true.
[/ QUOTE ]
Finding a bug that the devs find worthy of a bughunter badge will only yield the badge if you keep it quiet and report it. That was the original point and it does is true.
[/ QUOTE ]
i thought i read somewhere (badgehunter.com?) that Bughunter is no longer rewarded..
perma jump is ---> /up 1
I remember being unable to melee running mobs (without predicting their path and standing there with an attack queued) well before PvP was ever introduced to the game, which they later patched to be far more lenient.
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
To be more precise: it was an issue with Gauntlet in tankers (and to a lesser degree all targeted aoe attacks with very small radius.) True single target attacks never had the "impossible to hit moving targets" issue.
[/ QUOTE ]
Single-target attacks had a different issue. You couldn't get them to activate reliably. You could queue an attack and chase after a running opponent, and it was significantly unlikely that the attack would actually activate unless you ran past the opponent, rubbing shoulders with it the whole time.
[/ QUOTE ]
That was more of a PvP issue and how Auto Follow works, and Auto Follow is the best way to deal with moving foes in pvp if you are melee. Not that it made huge difference there, you still have to rub shoulders but now you don't have to do it so darn close.
In pve it was just a bonus as pve critters rarely move a much.
[/ QUOTE ]
...
Issue 0, release, whatever the hell you want to call it, had PvP? You still aren't getting it.
[/ QUOTE ]
I figured we were still talking about the issue that encouraged melee attacks to be moved from 5ft to 7ft.
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
There goes your chance at the bug hunter badge
[/ QUOTE ]
If I thought badges were worth anything I might find that disheartening.
[/ QUOTE ]
It's also not true.
[/ QUOTE ]
Finding a bug that the devs find worthy of a bughunter badge will only yield the badge if you keep it quiet and report it. That was the original point and it does is true.
[/ QUOTE ]
i thought i read somewhere (badgehunter.com?) that Bughunter is no longer rewarded..
[/ QUOTE ]
It is still awarded, much more often than before, though. They used to be a bit more picky with rumors saying if you dared mention the badge you would not get it even if they were considering to give you one to begin with. It has been claimed this is not true. The badge is, in big part, used to lure people into quietly reporting potentially exploitable bugs.
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
There goes your chance at the bug hunter badge
[/ QUOTE ]
If I thought badges were worth anything I might find that disheartening.
[/ QUOTE ]
It's also not true.
[/ QUOTE ]
Finding a bug that the devs find worthy of a bughunter badge will only yield the badge if you keep it quiet and report it. That was the original point and it does is true.
[/ QUOTE ]
I misread the statment. For whatever reason, I thought asking for the Bughunter badge was the issue.
Sorry about that.
Not a bug, not an exploit. It is WAD (working as designed) though it may not necessarily be WAI (working as intended). Although changing the engine to make this not happen might increase server load to an unfeasible degree.
Basically, there is approximately a 1-1.5 second 'grace-period' to still be able to hit any targets that initially were valid targets. This is how that Blaster's nuke that is activated within that grace period can still hit all the targets that were already knocked away by that Warshade's Gravitic Emanation.
This is no more an exploit than a -def enhancement effecting +def. It's the way the current engine works, and the Devs would prefer that fewer people know about it rather than more.
.
.Driver Sweeper * CohHelper * HijackThis * TweakCoH * CPU-ID
* Defraggler * Program Security Scan * PC Performance Scan *
[ QUOTE ]
Not a bug, not an exploit. It is WAD (working as designed) though it may not necessarily be WAI (working as intended).
[/ QUOTE ]
i'll go with this.
Dr. Todt's theme.
i make stuff...
[ QUOTE ]
Once, playing my BS/Inv Scrapper, I pulled so many Jaegers of them around a crate and used Headsplitter on them all, the resulting explosion and screenshake was so loud and disruptive that for a moment, I wasn't sure what had happened. I seriously thought that the Fire/Fire Blaster who was on my team had used Inferno, but she hadn't; it was all the exploding bots.
I also nearly died from the damage they deal when they explode.
Some passers-by actually applauded in /local.
[/ QUOTE ]
Good times!
A couple of times my kat/regen bit off more than he could chew and his Golden Dragon finisher did him in too.
My favorite though was my buddy's dm/regen. Nothing like landing Shadow Maul on a stadium full of bots...
The Nethergoat Archive: all my memories, all my characters, all my thoughts on CoH...eventually.
My City Was Gone
[ QUOTE ]
Make sure you /bug it. And don't use it intentionally... the devs get annoyed at exploiting bugs.
Though this does make me wonder... if you had someone time Recall Friend exactly right, could you fire off a two mile long Golden Dragonfly?
[/ QUOTE ]
They can get a [censored] annoyed as they want I'm still going to do it until they say or do something about it. I've been doing this since before that "arcanatime" post and after that post I knew why and how to abuse it much better. /em devilhorns
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
There goes your chance at the bug hunter badge
[/ QUOTE ]
If I thought badges were worth anything I might find that disheartening.
[/ QUOTE ]
It is worth something: the powa to tell badge hunters you, who could care less about badges, have a badge they will likely never get
[/ QUOTE ]
If he doesn't think it's worth something, then he doesn't think it is worth something. DUH.
i do not beleive this is an exploit it is more a delay of damage being applied to targets targeted within range of the attack at the time of firing it off. your joustiung motion and their chasing motion happens before the damage is applied. works with sands of mu and ripper also
I've known about this for a while. Sands of Mu vet power is famous for it, especially combined with superspeed. I find myself doing it and not even realizing that I've chosen to do it sometimes. And though the power may have a 5 target max, i think u may be able to hit more people because of the lag or whatever. Try doing it on a tank jumping over a big group.
And yea, my gosh doing it with recall friend would be awesome, if u could hit that many.
<QR>Now on test: Fixed a bug where cones could hit significantly more enemies than intended.
And in response to a request for clarification Castle posted: [ QUOTE ]
[ QUOTE ]
[ QUOTE ]
Fixed a bug where cones could hit significantly more enemies than intended.
[/ QUOTE ]
Could we get some clarification on what, exactly, this means? Were cone powers hitting more than the target cap, cones being a larger size than intended, the 'cone warp' due to movement?
[/ QUOTE ]
The 'cone warp' due to movement.
[/ QUOTE ]
So i guess it was unintended and fixable. Assuming the fix works correctly, that is. It would probably be a good idea to test it and make sure it didn't bork melee cones in some way.
Dr. Todt's theme.
i make stuff...
Y'know, the timing here isn't exactly something that I can get rid of by a long hot shower.
Is it any coincidence that some of the coolest stuff you can do with game mechanics also happens to be exploitable?
"One day we all may see each other elsewhere. In Tyria, in Azeroth. We may pass each other and never know it. And that's sad. But if nothing else, we'll still have Rhode Island."
[ QUOTE ]
Y'know, the timing here isn't exactly something that I can get rid of by a long hot shower.
[/ QUOTE ]
Maybe a song would help.
Dr. Todt's theme.
i make stuff...
I'm going to miss you, 10+hitshalfbeingacriticalGD!
[ QUOTE ]
Y'know, the timing here isn't exactly something that I can get rid of by a long hot shower.
[/ QUOTE ]
Who says the devs don't read the forums
[ QUOTE ]
Who says the devs don't read the forums
[/ QUOTE ]
...a lot of paranoid schizophrenics in the tanker forum.
Did "cone warp" allow you to break the target cap for cones? You can routinely hit 8 targets with powers like Ripper if you stack foes properly... I'd love to have the old skool broken AE cones that hit EVERYONE, but I'm ok with the current dmg output it offers.
[ QUOTE ]
Did "cone warp" allow you to break the target cap for cones?
[/ QUOTE ]
No
[ QUOTE ]
Did "cone warp" allow you to break the target cap for cones? You can routinely hit 8 targets with powers like Ripper if you stack foes properly... I'd love to have the old skool broken AE cones that hit EVERYONE, but I'm ok with the current dmg output it offers.
[/ QUOTE ]
No, it just allowed cones to cover a much greater area than originally intended.
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
There goes your chance at the bug hunter badge
[/ QUOTE ]
If I thought badges were worth anything I might find that disheartening.
[/ QUOTE ]
It's also not true.
[/ QUOTE ]
Finding a bug that the devs find worthy of a bughunter badge will only yield the badge if you keep it quiet and report it. That was the original point and it does is true.