|
|
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Beren Hurin
OMNI Endeavors
190
   |
Posted - 2013.02.28 15:15:00 -
[1] - Quote
1) I know with my current hacking skills, in my logi suit, can counter hack the thing after it has cycled half way through its timer.
2) Every hack 'contests' for 1 minute.
3) For that minute the null cannon is still shooting at its original target
4) see my research on MCCs and NC damage here
5) If you wait to hack the null cannon after it has flipped you are basically letting it do 1.3% damage to your MCC.
6) 1.3% damage requires you do do 2x that to the enemy to make up for your loss and/or kill >2 clones for every minute the null cannon is not friendly.
7) You are denying the other team 100 points and a possible new spawn point.
IOW a counter-hack is worth around 100 to 150+ points strategically (>2 kills and strategic advantage of the objective). Realistically, the value of a counter-hack would have to be more than an actual hack in order to incentivise it. What you have to think about though is what you are denying the other team.
The problem with giving points to the counter hack is a slippery slope. If you give points for it, then what happens when you see someone hacking it...then you wait for them to hack it so you can get the points to counter hack and the kill. So then people would be just waiting for hackers to kill/counter hack. Then nobody would want to hack because it wouldn't be worth the effort if you are likely to be stopped so often. |
Beren Hurin
OMNI Endeavors
191
|
Posted - 2013.02.28 15:53:00 -
[2] - Quote
Kray Dytt wrote:Beren Hurin wrote:
The problem with giving points to the counter hack is a slippery slope. If you give points for it, then what happens when you see someone hacking it...then you wait for them to hack it so you can get the points to counter hack and the kill. So then people would be just waiting for hackers to kill/counter hack. Then nobody would want to hack because it wouldn't be worth the effort if you are likely to be stopped so often.
Hmm hadn't really thought of that though... that's a point I guess. On the other hand, killing someone when they are hacking is much more reliable reliable than waiting for them to finish. But yes, people would probably do this. Of course, to counter this you could grant +150WP for killing someone who is hacking... but that would just be silly ;)
Lol, then giving points for the hacker kill would result in hack camping, you would just wait to kill the guy until he goes up to hack it. He'd look at you like...you gonna shoot me bro, and you shake your gun 'No!'. He'd try to shoot at you and you get behind cover, he'd chase you a bit, and lose you. He'd go back to start hacking only to see you on radar again, then he'd stop hacking just to f*** with you, then one of your teamates would mercy kill him. |
Beren Hurin
OMNI Endeavors
191
|
Posted - 2013.02.28 15:58:00 -
[3] - Quote
Kray Dytt wrote:I totally agree. It should just count as any other hack, +100. It's silly now, because you have people waiting for the enemy hack to complete, so they can take it back. Which leaves you vulnerable to counter-hacking again and means you have less NULL canon time for your team.
It's like the game is asking you: "do you want personal gain, or team benefit?" Whereas I think these two should go hand in hand.
This conflict over personal gain/team gain is everywhere you look for it though.
-Snipers getting KDR
-Teamates yelling "you got my kill!!!" when you get their kill
-Teamates yelling "Stupid blueberry, wtf protect me!" ...when 'their kill' kills them because you were letting them get their kill.
-Dropship pilots...
-masochistic logibros who needle you alive under HMG fire
-most logibro actions
-being a dedicated AV
-destroying all installations
Personal gain and team benefit is REALLY hard to mix perfectly. |
|
|
| |
|