|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Garrett Blacknova
Codex Troopers
4028
|
Posted - 2013.09.16 21:55:00 -
[1] - Quote
You can always cancel it by hitting the driver while he tries to recall.
If the "victim" gets far enough away to park their vehicle in the path of your fire and it still has enough EHP to survive the recall process, you got outplayed and they deserve it. If they don't get far enough away, but you don't target the driver to interrupt the recall, and they finish before you kill it, the vehicle deserves to survive because you screwed up. |
Garrett Blacknova
Codex Troopers
4028
|
Posted - 2013.09.16 22:04:00 -
[2] - Quote
Nguruthos IX wrote:Garrett Blacknova wrote:You can always cancel it by hitting the driver while he tries to recall.
If the "victim" gets far enough away to park their vehicle in the path of your fire and it still has enough EHP to survive the recall process, you got outplayed and they deserve it. If they don't get far enough away, but you don't target the driver to interrupt the recall, and they finish before you kill it, the vehicle deserves to survive because you screwed up. So you're saying a tank with 20% shield left should be able to hop out quickly, use the vehicle as LOS, wiggle around a bit and recall it in 2 seconds, faster than 2 players might be able to finish it with AV, or trek the entire distance between the range of wherever they were shooting from, get to the tank, walk around it, line up some AP shots, and kill the pilot before it's recalled in that quick moment? And this is being out played? Or simply a broken mechanic that needs revised for that reason. The only revision needed is the amount of time a recall takes. It's currently a LITTLE faster than I think it should be.
If you're in close quarters and the driver hops out of their tank to recall, a Swarm Launcher can lock, aim over the tank and fire, the arcing shots will hit the driver as well as the tank, both damaging it AND interrupting the recall. I've done it before. If they had tried to retreat, I would have killed the tank before they got far enough, and because they didn't, I got to kill the tank first then melee its driver to death because I was running with no sidearm. |
Garrett Blacknova
Codex Troopers
4028
|
Posted - 2013.09.16 22:07:00 -
[3] - Quote
Master Jaraiya wrote:Shattered Mirage wrote:Master Jaraiya wrote:Garrett Blacknova wrote:You can always cancel it by hitting the driver while he tries to recall.
If the "victim" gets far enough away to park their vehicle in the path of your fire and it still has enough EHP to survive the recall process, you got outplayed and they deserve it. If they don't get far enough away, but you don't target the driver to interrupt the recall, and they finish before you kill it, the vehicle deserves to survive because you screwed up. I don't think vehicles take damage while being recalled. I have shot at flaming tanks, but they didn't blow up. Shortly after, they disappeared. They take damage... test it sometime if you need proof. Its when they turn invisible before leaving that I think they take no damage. I have. Call me crazy, but I don't think any burning vehicle could survive a blast from my Advanced Assault Forge Gun. Just sayin. I've had one of my Gunnlogis destroyed by a Forge Gun while I was in the middle of recalling it.
It's possible there was lag, or a hit detection glitch, or it was already recalled and starting to fade (at which point there IS momentary invulnerability, but that means you were late firing). |
Garrett Blacknova
Codex Troopers
4029
|
Posted - 2013.09.16 22:10:00 -
[4] - Quote
Also, you complain that people should have to swap fittings to get a full-health tank on the field... What if I have 5 of the same fitting? Why does it make sense to wait potentially for several minutes to send my damaged HAV in for repairs, then call THE SAME ONE back still damaged when I STILL HAVE FOUR FRESH ONES WAITING.
The game should track recalled HAVs and prevent them from being called in again during the same battle - in effect, recalling the HAV prevents you from requesting it again in that match. It isn't dead, but it's not combat-ready any more. |
Garrett Blacknova
Codex Troopers
4030
|
Posted - 2013.09.16 22:49:00 -
[5] - Quote
Monkey MAC wrote:Garrett Blacknova wrote:Also, you complain that people should have to swap fittings to get a full-health tank on the field... What if I have 5 of the same fitting? Why does it make sense to wait potentially for several minutes to send my damaged HAV in for repairs, then call THE SAME ONE back still damaged when I STILL HAVE FOUR FRESH ONES WAITING.
The game should track recalled HAVs and prevent them from being called in again during the same battle - in effect, recalling the HAV prevents you from requesting it again in that match. It isn't dead, but it's not combat-ready any more. So you have 10 of em in a hanger I get you to recall 4, but the match dont last any longer? So I die 20 times suppresing you, you loose nothing, when you would have lost 3! If I was stupid and didn't recall in time, I would have lost 3.
But if I WASN'T stupid, you still kept me supressed, and during the couple of minutes where I was without access to my tank, either you or your teammates had a nice easy target to kill because of your work.
And if I screwed up at any point and waited to long to retreat/recall, you get your kill which, unlike any of my kills on you, is worth over a million ISK because of a single miscalculation. |
|
|
|