These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE General Discussion

 
  • Topic is locked indefinitely.
Previous page12
 

Someone lost a T2 bpo.
Author
Previous Topic Next Topic
Ralph King-Griffin
New Eden Tech Support
#21 - 2015-04-19 11:56:32 UTC  |  Edited by: ISD Ezwal
Untrained Capsuleer wrote:
well the ingame killmail does say they are bpos

*snip* Posting of kill reports outside of the Crime & Punishment forum channel is prohibited. ISD Ezwal.

i stand corrected

Murderers of Negotiable Motivations

=]|[=
Hemmo Paskiainen
#22 - 2015-04-19 23:07:11 UTC  |  Edited by: Hemmo Paskiainen
Hal Morsh wrote:
ahh can't post killmails as far as I know.

It's a Mjolnir rage rocket,


Yay 27 usesless Mjolnir's left! Roll

If relativity equals time plus momentum, what equals relativity, if the momentum is minus to the time?
Paranoid Loyd
#23 - 2015-04-20 00:11:04 UTC
Scipio Artelius wrote:
13kr1d1 wrote:
Almost like CCP needs to get off their collective lazy asses and code in a minimum locking time, regardless of ship type.

Just because an OP makes a claim, it isn't necessarily any more factual than anything posted in a reply.

There is no evidence presented that this involved an insta-locking Svipul, which wouldn't catch a blockade runner anyway unless something went wrong (eg. pilot error or lag).

The Sabre involved is a far more likely reason he was caught, but without the pilots involved giving an explanation, the claim in the OP is no more realistic than saying it was because of the Sabre.

This. There is no insta locking, there was either lag or a lazy pilot

"There is only one authority in this game, and that my friend is violence. The supreme authority upon which all other authority is derived." ISD Max Trix

Fix the Prospect!
Yun Kuai
Garoun Investment Bank
Gallente Federation
#24 - 2015-04-20 00:40:18 UTC
You know it's funny, a quick search of the pilots name Ingolfur Arnars leads to a wiki page reading this:
"Ingólfur Arnarson and his wife Hallveig are recognized as the first permanent Nordic settlers of Iceland. According to Landnáma he built his homestead in Reykjavík in 874."

sounds like someone got a freebie from a CCP dev a long, long time ago....so now I'm kinda glad he lost it Twisted

--------------------------------------------------------::::::::::::--:::-----:::---::::::::::::--------------:::----------:::----:::---:::----------------------:::::::-------:::---:::----::::::-------------------:::-----------:::--:::----:::---------------------::::::::::::----:::::::----:::::::::::::-------
Jenshae Chiroptera
#25 - 2015-04-20 06:27:05 UTC
That Viator is a fail fit.

MWD + cloak trick (to reduce chance of being decloaked)
Align time
Getting to warp time.

CCP - Building ant hills and magnifying glasses for fat kids

Not even once

EVE is becoming shallow and puerile; it will satisfy neither the veteran nor the "WoW" type crowd in the transition.
Aeana K
Republic Military School
Minmatar Republic
#26 - 2015-04-20 07:13:08 UTC
Paranoid Loyd wrote:
Scipio Artelius wrote:
13kr1d1 wrote:
Almost like CCP needs to get off their collective lazy asses and code in a minimum locking time, regardless of ship type.

Just because an OP makes a claim, it isn't necessarily any more factual than anything posted in a reply.

There is no evidence presented that this involved an insta-locking Svipul, which wouldn't catch a blockade runner anyway unless something went wrong (eg. pilot error or lag).

The Sabre involved is a far more likely reason he was caught, but without the pilots involved giving an explanation, the claim in the OP is no more realistic than saying it was because of the Sabre.

This. There is no insta locking, there was either lag or a lazy pilot


In my experience, there is insta locking.

Sometimes, you click faster the warp-cloak combo than the server's tick, and you receive a msg that "you cannot cloak coz bla bla bla". Then you need to click the cloak again. Meanwhile, the instalockers have a point on you.

I don't know if you consider this as a pilot's mistake, in my opinion it is not. It needs experience to learn the servers timers, but sometimes can also be just unlucky.

/A
Ivarr Kerensky
Kerensky Tactical Group
#27 - 2015-04-20 07:51:11 UTC  |  Edited by: Ivarr Kerensky
If done right then no, you can't be "insta locked" because it doesn't exist, UNLESS those "insta lockers" were exploiting. So assuming the target did everything right in regards to the timing etc (and didn't get uncloaked) I'd suggest to him to create a petition about it.

Excellence is an attitude.
March rabbit
Aliastra
Gallente Federation
#28 - 2015-04-20 08:24:48 UTC
Nalia White wrote:
13kr1d1 wrote:
Herzog Wolfhammer wrote:
Hal Morsh wrote:
Well... Viator with cloaky doesn't prevent instalocks now does it. Doesnt matter if your warp and cloak commands are right on top of each other, you will "still" be instalocked. Fly a inty? Well, instalock and you wont even be scrammed, a svipul will just instapop arty you due to murphies law.



Regardless, someone now has a T2 bpo because it dropped. I dunno if the guy who lost it was legitimately moving it through null, or was quitting eve and decided to give a good killmail before he left. Crazy though.




Funny. Before the Svipul, a Loki could to the instalock. So it's cheaper now I guess. Nothing changes.


Almost like CCP needs to get off their collective lazy asses and code in a minimum locking time, regardless of ship type.


er why? stupid people just will get caught, it's that easy. if you're not stupid or lazy, you will not get caught in eve.

well...
1) Eve Online is not twitch game (at least some people love to say it)
2) Eve Online is 'Online' game with very different internet connections of players

And you don't need to be stupid or lazy if your connection does not allow you to warp + cloak in your bomber faster than somebody sitting on gate can lock and point you. I have lost my bomber this way - after pressing 'warp' was not able to start cloaking because 'your ship performs initial cloaking' (or what do they say when you are still in cloak after jump to the system) for few seconds. Yes, got pointed immediately and then killed. And it is all because of internet lags. Yes, CCP can not handle such things but they COULD make mechanic better suited for such things.

The Mittani: "the inappropriate drunked joke"
Ralph King-Griffin
New Eden Tech Support
#29 - 2015-04-20 08:32:19 UTC
Aeana K wrote:
Paranoid Loyd wrote:
Scipio Artelius wrote:
13kr1d1 wrote:
Almost like CCP needs to get off their collective lazy asses and code in a minimum locking time, regardless of ship type.

Just because an OP makes a claim, it isn't necessarily any more factual than anything posted in a reply.

There is no evidence presented that this involved an insta-locking Svipul, which wouldn't catch a blockade runner anyway unless something went wrong (eg. pilot error or lag).

The Sabre involved is a far more likely reason he was caught, but without the pilots involved giving an explanation, the claim in the OP is no more realistic than saying it was because of the Sabre.

This. There is no insta locking, there was either lag or a lazy pilot


In my experience, there is insta locking.

Sometimes, you click faster the warp-cloak combo than the server's tick, and you receive a msg that "you cannot cloak coz bla bla bla". Then you need to click the cloak again. Meanwhile, the instalockers have a point on you.

I don't know if you consider this as a pilot's mistake, in my opinion it is not. It needs experience to learn the servers timers, but sometimes can also be just unlucky.

/A

That's the pilot error . Iv lost ships that way and on both counts I knew it was my fault.

You're giving them an extra server tic or two to get a lock and it's often enough.

Having been on both the giving and receiving end of it I will say you have to **** it up or get decloaked to get caught, particularly with a covops.

Murderers of Negotiable Motivations

=]|[=
Solecist Project
#30 - 2015-04-20 08:38:53 UTC
Link got removed.
Can confirm t2 BPOs.
Saw the original.

Kudos for him trying to find the corp with new chars ...
... just to verify it.

That ringing in your ears you're experiencing right now is the last gasping breathe of a dying inner ear as it got thoroughly PULVERISED by the point roaring over your head at supersonic speeds. - Tippia
Sturmwolke
#31 - 2015-04-20 10:16:39 UTC
Eh, fail fit Viator. WCs, no prop mode in Bubble Land.
5-6s align (makes it easy for frig/dest to ping last position) and no prop mod to help throw their aim off after gate cloak.

That Sabre had plenty of time to drop a bubble when they see him de-cloak, from there on, it's just a matter off pinging his last location.
Takes 3-4 secs for anything running at ~5000m/s to close the 15km max gap, in practice, this gap can sometimes be a lot smaller (10-15km).

Use the proper T3 next time for small packages, then you only have to worry about proximity de-cloaks.
Fairly easy to mitigate. Inties are also applicable, but that opens up an extra weakness - gate smartbombers.
War Kitten
Panda McLegion
#32 - 2015-04-20 11:23:56 UTC
Confirming that really fast locking is possible, but not insta-locking. I've gatecamped more than a few times with lots of remote seboing, and you just can't catch a cloaky (or properly nano'd inties, or pods, or....) unless they screw up.

Achieving the message that your cloak fails to activate due to the cloaking you're currently doing is indeed screwing up.

I don't judge people by their race, religion, color, size, age, gender, or ethnicity. I judge them by their grammar, spelling, syntax, punctuation, clarity of expression, and logical consistency.
Soldarius
Dreddit
Test Alliance Please Ignore
#33 - 2015-04-20 14:58:40 UTC
Confirming that unless the covops screws up or the RNG gods spawn it within 2000m of something, he should get away clean. No prop mod means no MWD/cloak trick = dead covops.

http://youtu.be/YVkUvmDQ3HY
Solecist Project
#34 - 2015-04-20 18:53:26 UTC
Soldarius wrote:
Confirming that unless the covops screws up or the RNG gods spawn it within 2000m of something, he should get away clean. No prop mod means no MWD/cloak trick = dead covops.

Bob giveth ...
... Bob taketh.

That ringing in your ears you're experiencing right now is the last gasping breathe of a dying inner ear as it got thoroughly PULVERISED by the point roaring over your head at supersonic speeds. - Tippia
Jenshae Chiroptera
#35 - 2015-04-21 04:29:08 UTC
Ivarr Kerensky wrote:
If done right then no, you can't be "insta locked" because it doesn't exist, UNLESS those "insta lockers" were exploiting. So assuming the target did everything right in regards to the timing etc (and didn't get uncloaked) I'd suggest to him to create a petition about it.
2550mm is all it takes for an "instant" lock, this is where the server tick makes it 50/50% chance of being locked or escaping / cloaking.
Bubbles + drones + immediate align + prop mod on.

CCP - Building ant hills and magnifying glasses for fat kids

Not even once

EVE is becoming shallow and puerile; it will satisfy neither the veteran nor the "WoW" type crowd in the transition.
Ivarr Kerensky
Kerensky Tactical Group
#36 - 2015-04-21 11:29:55 UTC
Jenshae Chiroptera wrote:
Ivarr Kerensky wrote:
If done right then no, you can't be "insta locked" because it doesn't exist, UNLESS those "insta lockers" were exploiting. So assuming the target did everything right in regards to the timing etc (and didn't get uncloaked) I'd suggest to him to create a petition about it.
2550mm is all it takes for an "instant" lock, this is where the server tick makes it 50/50% chance of being locked or escaping / cloaking.
Bubbles + drones + immediate align + prop mod on.


I've been a covops scout since 2006, I've never EVER been caught unless I messed up in regards of timing/lag or proximity uncloaking. Chances of that happening if with normal game mechanics it would be possible, zero.

Excellence is an attitude.
Previous page12