open All Channels
seplocked EVE General Discussion
blankseplocked Strangest thing I've ever read.
 
This thread is older than 90 days and has been locked due to inactivity.


 
Pages: 1 [2]

Author Topic

Dark Assassin15
Failed Diplomacy
B A N E
Posted - 2007.10.05 04:45:00 - [31]
 

Edited by: Dark Assassin15 on 05/10/2007 04:46:21
I dont think the can agression works. Ive tried it b4. But ive also agressed someone who logged off then they werent on scan, they log back on, and logoff again before they warp back and get agression, i probe him and kill. Eve game mechanics FTW.

Xaen
Caldari
Aperture Harmonics
K162
Posted - 2007.10.05 13:03:00 - [32]
 

Quit logging to escape combat perhaps?

Shevar
Minmatar
Target Practice incorporated
Posted - 2007.10.05 13:41:00 - [33]
 

Quote:
Note that your onscreen timer countdown may not take into account events that cause the timer to get refreshed.


Euhm? So there is a proper mechanic keeping by exactly how long it lasts but the one showing on your screen is faulty? So why show that timer at all?

OneSock
Crown Industries
Posted - 2007.10.05 13:56:00 - [34]
 

I thought wreck shooting was classed as an exploit and fixed ?

They should make displaying the correct agro timer a priority.

Stork DK
Minmatar
Risky eXplosion
Death or Glory
Posted - 2007.10.05 13:59:00 - [35]
 

They might have shot your drones after you engaged. that would renew the timer.

Inspiration
Posted - 2007.10.05 14:04:00 - [36]
 

Edited by: Inspiration on 05/10/2007 18:00:23
Originally by: CCP Greyscale
This particular mechanic has been documented in the knowledgebase for quite some time. Note that the timer updates every time you commit a hostile act against another player or another player commits a hostile act against you.


Thats making an assumption on what actualy happened. I got it several times that even without wreck, logging off after the timer was gone, and stay offline for another 30 minutes, then logging back on, would cause my timer to reset! This happened both when docked and when not, both in high sec and low sec.

After a while a GM moved me to another node, to see if that solved the issue. I could undock fine without timer, but after 1 jump I got concordoned and got a new global criminal flag timer. Random criminal flagging occurs, stuck criminal flagging occurs (as was in my case). But by assuming something known caused the issue based on the symptom of a timer reset, you fail to spot new causes and subsequently they get ignored and never fixed.

This is what ****es players off, expect more of these kind of threads in the coming weeks. The whole issue is at least a month old, as it happened to a buddy of mine after our first real low sec operation. Since then I had TWO cases of my own.

The problem goes away after downtime and no matter what you do before that (including following up all GM suggestions....they dont got a clue either) it will not go away! And everyone in EVE will have the RIGHT to kill you without repurcussions. And concord will happily help to make ur life miserable by poping you and giving every1 free loot that wont get reimbursed.

Your reply realy ****ed me off, let me make that crystal clear!

Shaundra
Posted - 2007.10.05 14:34:00 - [37]
 

If a prober has a 20au probe out, there is a good chance you won't see it as your onboard scanner only sees about 12au.

When you log out, even when not aggressed, your ship stays in space for a minute or two before it disappears.

It takes me 30 seconds to probe a target down, then I warp the entire fleet in to attack the target. Takes even less time if I happen to have started a scan before the target logs off.

FYI if you drop a bubble on the target, the pod will not warp off and can be popped immediately once the surrounding vessel has been destroyed.

Offline targets seldom last longer than 15 or 20 seconds with a 5-6 man gang pounding on the hull.

My point is that even if you wait for your timer to expire, a hostile fleet still has a window (albeit very small) to find and destroy you. I suspect what happened is this:

Prober drops probe and starts scan. 15 seconds later, you log off. Prober gets hit, warps fleet to the location, interdictor bubble is deployed as the fleet destroys your ship, then they pod you. All of this occurs in 1 minute.

Regards,

Shaundra


N1fty
Galactic Shipyards Inc
Huzzah Federation
Posted - 2007.10.05 14:54:00 - [38]
 

Originally by: Shaundra
If a prober has a 20au probe out, there is a good chance you won't see it as your onboard scanner only sees about 12au.

When you log out, even when not aggressed, your ship stays in space for a minute or two before it disappears.

It takes me 30 seconds to probe a target down, then I warp the entire fleet in to attack the target. Takes even less time if I happen to have started a scan before the target logs off.

FYI if you drop a bubble on the target, the pod will not warp off and can be popped immediately once the surrounding vessel has been destroyed.

Offline targets seldom last longer than 15 or 20 seconds with a 5-6 man gang pounding on the hull.

My point is that even if you wait for your timer to expire, a hostile fleet still has a window (albeit very small) to find and destroy you. I suspect what happened is this:

Prober drops probe and starts scan. 15 seconds later, you log off. Prober gets hit, warps fleet to the location, interdictor bubble is deployed as the fleet destroys your ship, then they pod you. All of this occurs in 1 minute.

Regards,

Shaundra




Welcome to Eve, logging off to avoid combat will not save you from determined foe Twisted Evil

Kruel
Beyond Divinity Inc
Posted - 2007.10.05 15:02:00 - [39]
 

Well that's just stupid. What if you gotta take a **** or go to bed and someone keeps taking pot-shots at your wrecks? Razz

uoY delliK
Detached Regiment
Posted - 2007.10.06 19:58:00 - [40]
 

A) there was 6 pilots, none were in a dictor.
B) all 6 pilots were on scan, when I did my final scan... None of them were in recon, or cov ops ships... All were BC/BS/HAC.
C) i stand by my statement, there is no way they probed me in the minute or 2 it took for my ship to warp after i logged. Especially since I logged mid-warp... It initiates the "omg warp out" sequence before you come out of warp, and generally you immediately warp out when you come out of your initial warp.

DeadProphet
Black Eclipse Corp
KenZoku
Posted - 2007.10.06 20:16:00 - [41]
 

I've had this exact same thing. I was fighting in a fleet, warped to friendly POS, afk'd for more than an hour before deciding to log. I warped to a personal safe and logged (remember more than an hour since last action) Logged back in to find i had been killed 23 minutes after logging out (with no aggro anyway)

it took a long fight through the petition process and escalation to a senior GM, but i eventually got my ship back (and implants, which was a nice touch) back.

i recommend you file a petition also :)

DP


Originally by: uoY delliK
Originally by: CCP Greyscale
This particular mechanic has been documented in the knowledgebase for quite some time. Note that the timer updates every time you commit a hostile act against another player or another player commits a hostile act against you.



While I appreciate your response, it still doesnt address the issue. According to my in-game log, it was 16 minutes, 30 seconds since my last combat action. For those 16 minutes, I was afk at a safespot. I then warped to a planet at 100, making a new bookmark mid-warp. I then started warp, to new safespot. During which time, I scanned for probes, and saw none. About 1/2 way through that warp, I logged off... Assuming, since it'd been nearly 17 or 18 minutes since I'd committed a combat action it would take me to an offgrid safe, and I'd log back in, to my ship. However, I was killed... and podded.

That is my issue... The timer had worn off, without a doubt in my mind.

Dao2SKP
Perkone
Posted - 2007.10.06 20:19:00 - [42]
 

yeah actually this is why cyvok lost the first titan ;p it became known right then ^^

Arushia
Nova Labs
New Eden Research.
Posted - 2007.10.06 22:36:00 - [43]
 

Originally by: uoY delliK
A) there was 6 pilots, none were in a dictor.
B) all 6 pilots were on scan, when I did my final scan... None of them were in recon, or cov ops ships... All were BC/BS/HAC.
C) i stand by my statement, there is no way they probed me in the minute or 2 it took for my ship to warp after i logged. Especially since I logged mid-warp... It initiates the "omg warp out" sequence before you come out of warp, and generally you immediately warp out when you come out of your initial warp.

Were those the only 6 other pilots in local? Covops can probe while cloaked, and don't show up on scans when cloaked.

ReaperOfSly
Gallente
Underworld Protection Agency
South Pole Dancers
Posted - 2007.10.06 22:44:00 - [44]
 

Originally by: uoY delliK
Hi,

If a player logs out with a aggression timer, it renews. This is intended game mechanics.

From a GM, in response to my petition, that I waited 16 from my last combat action according to my in game log. Started warp to a new safespot I had just made, flashed scanner once for probes (saw none), then logged. Somehow I was probed down, killed and podded. In two years of playing, I've never heard, that an aggression timer renews if you log out... THAT IS INSANE. If anyone else has heard this unbelievable tale, please let me know.


On a side note, is anyone else getting fed up with cookie-cutter petition responses, that never answer your petition issue, and always end in "no"?


It's an extremely irritating game mechanic. I still don't know what is gained by it, but I guess CCP moves in mysterious ways. Razz

Those cookie-cutter reesponses I think are meant to deal with the majority of petitions - the ones about trivial matters. If you have a non-trivial matter, just reply to their message and you might get to talk to a human being instead of a copy-paste machine.

Mr Friendly
The Lost and The Damned
Posted - 2007.10.07 18:03:00 - [45]
 

From the kbase section, "Note that your onscreen timer countdown may not take into account events that cause the timer to get refreshed."

Anyone else find this incredibly lame? How else are we to avoid being killed if we don't have the information needed?

Wow, that's just plain old crappy design on CCP's part, tbh. Why have a visible timer at all if it's not spot-on correct, 23/7?


Pages: 1 [2]

This thread is older than 90 days and has been locked due to inactivity.


 


The new forums are live

Please adjust your bookmarks to https://forums.eveonline.com

These forums are archived and read-only