| Author |
Thread Statistics | Show CCP posts - 0 post(s) |

RubyPorto
Profoundly Disturbed RED.Legion
183
|
Posted - 2011.12.22 18:54:00 -
[1] - Quote
To stay alive: iStabbed CovOps (visible for one 1s tick = impossible to lock, no bubble = next to impossible to decloak)
To kill CovOps in lowsec: Smartbombs, or get lucky vs a shitty covops pilot.
Other frigs you have a shot with a bunch of Sebos if their align time is over 2s (1s to lock, 1s for module activation). |

RubyPorto
Profoundly Disturbed RED.Legion
183
|
Posted - 2011.12.22 20:50:00 -
[2] - Quote
Lady Spank wrote:Don't encourage remote sebo horseshit please.
I'm not a sentry gun, popping frigates, how can I encourage rSEBO horseshit?  |

RubyPorto
Profoundly Disturbed RED.Legion
183
|
Posted - 2011.12.22 22:21:00 -
[3] - Quote
Lady Spank wrote:RubyPorto wrote:Lady Spank wrote:Don't encourage remote sebo horseshit please. I'm not a sentry gun, popping frigates, how can I encourage rSEBO horseshit?  I was referring to the whole gatecamping bullcrap, not the post directly above mine.
Gatecamping beats the hell out of ratting when I'm too tired or drunk to roam. |

RubyPorto
Profoundly Disturbed RED.Legion
183
|
Posted - 2011.12.22 23:51:00 -
[4] - Quote
Lady Spank wrote:To spell my point out a little more clearly... Creating an event encouraging and promoting stupid gatecamping techniques which damage solo/v small gang roams is pretty bad.
I think OP is trying to set up another fight like the one they did with their Moros. Encouraging a Lots-O-Frigs killing a Dreadnaught, but trying to help people get their with less getting dead.
That said, Gatecamps are annoying to pass through, lazy to be in, and a poor mechanic for Lowsec and NPC Null. Sov null needs them help define borders (like RL border patrol, but worse at it). But they're pretty well inevitable without some way to pick fights on the path between gates. |

RubyPorto
Profoundly Disturbed RED.Legion
184
|
Posted - 2011.12.23 02:11:00 -
[5] - Quote
Marlona Sky wrote:Lady Spank wrote:What part of solo don't you understand. All of it probably. I understand that solo PvP has been dead for a very long time now. The only thing that comes close is fake solo PvP which means using RR alts, bonus alts and scout alts to help. Anyways this is straying away from the topic. So it is my understanding is that if the frigate can align and warp in under two seconds; anything outside of another frigate won't be able to catch it?
Discussion Time.
Eve operates in 1 second ticks. That's why you can't lock a cloaky before it cloaks. The following is roughly how I understand it to work.
Tick 1: Send Warpto Command. Tick 2: Uncloak, initiate warp (align time starts) > Send Cloak command. Begin Targeting (assume <1s targetting time) Tick 3: Cloak dissapears you. Targetting cancelled instead of completed.
Without a cloak: Tick 1: Send Warpto Command. Tick 2: Uncloak, initiate Warp (align time starts). Begin Targeting, Point Hot. Tick 3: 1s into align time. Target locked, tell point to activate (not 100% sure the point can never activate this tick). Tick 4: Align time completed, Enter warp. Point attempts to activate, target is in warp, target unlocked. |

RubyPorto
Profoundly Disturbed RED.Legion
212
|
Posted - 2011.12.27 18:08:00 -
[6] - Quote
Stalking Mantis wrote:You could just grow a pair and learn how to actually PvP frigate versus frigate and feel the rush of a close fight where you barely make it out in structure.
Oh wait you mean you want to shoot frigates in a T3 or a Battlecruiser?
And here I was thinking this was a PvP thread.
I also get angry when people play in the Sandbox wrong. Shall we form a support group?
Wait, this isn't the miner tears thread.... where am I? |

RubyPorto
Profoundly Disturbed RED.Legion
216
|
Posted - 2011.12.27 23:03:00 -
[7] - Quote
Taedrin wrote:No matter how high your scan res is, you can still have difficulties catching frigates due to lag (and possibly human reaction times if you don't have your overview set up correctly).
It's not lag, it's Eve operating in 1s ticks and not real time.
1st Tick: Targeting time (assuming not longer than 1s) 2nd Tick: Module Activates. |
| |
|