Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Ganthrithor
Caldari GoonFleet GoonSwarm
|
Posted - 2009.12.22 17:09:00 -
[1]
Edited by: Ganthrithor on 22/12/2009 17:12:56 Edited by: Ganthrithor on 22/12/2009 17:09:49 So, twice now I've been ****ed over by login/logoff mechanics in the past few days. There seems to be a problem with people being invisible on login.
The first time I noticed problems was the other day in Q-HESZ. A hostile was ratting in system in a Gila (a guristas faction cruiser). I jumped in, dropped probes and positioned them. The hostile logged off. I managed to get a result just as he landed from his logoff ewarp. I warped to the result, found his pilotless ship in space, scrammed it and started shooting with the small laser on MY BUZZARD. His ship disappeared about 30 seconds later (at about 95% shields).
We put a HIC and an inty on his logoff spot and I kept probes out on my covops character (so we could get a warpin on him if his ewarp proved to be uninterruptible). Lo and behold after a little while the hostile logged back in. Now the interesting part: the hostile never appeared where he disappeared. Not only that, he never appeared on the directional scanner or on probes either. He stayed logged in for a minute or two. Never appeared in space, on scan, or on probes. Then after a minute or so he logged off. He didn't appear on scan after he logged off either. Now, even if he had a cloak fit he should have both appeared in space where his ship disappeared (regardless of whether or not his logon e-warp was interruptible or not) and there's no way he could have cloaked for at least ~30 seconds since he'd have to ewarp and land before he could activate the cloak. He would also have appeared on scan once he logged off. Even ships with covops cloaks decloak when they logoff.
The same thing happened again tonight. A couple of us were on the AJI gate in Q-H waiting for a neutral hauler to come through. Eventually, a while after we emptied out AJI, the hauler (a Sigil-- Amarr T1 industrial) jumped into us. I was flying a bomber on my alt. 30 seconds after he jumped in, the Sigil dropped gate cloak and cloaked up. I started my bomber afterburning toward him. Before I could cover the 15km and decloak him, the Sigil pilot logged off and ewarped away (I couldn't scram him, he was "invulnerable.") We camped the gate he logged at with a HIC until downtime, then logged in immidiately after the server came up and kept camping.
An hour or so after DT, the Sigil pilot logged in again. He stayed logged in in Q-HESZ for about two minutes. He never showed up on directional scan, he never showed up on the scan probes my covops was running on the gate in anticipation of him attempting the logoff trip, and he never appeared on the gate where he had logged out.
As if this wasn't absurd enough, the guy managed to cross the system, get to the 6Q gate and jump out.
Ideas? I've petitioned both incidents but I've yet to get any sort of response from CCP.
|
Lork Niffle
Gallente External Hard Drive
|
Posted - 2009.12.22 18:49:00 -
[2]
I can't see an issue here. Logging features are working as intended. ------------------------------------- The system issues man. |
Ganthrithor
Caldari GoonFleet GoonSwarm
|
Posted - 2009.12.22 19:48:00 -
[3]
Originally by: Lork Niffle I can't see an issue here. Logging features are working as intended.
Yes just what this thread needs, a completely ignorant pubbie to come in and explain how someone logging in invisibly and not warping back to the spot they logged off at is normal or intended. You are literally ******ed, get out.
|
NightF0x
Gallente Intergalactic League of Terrorists
|
Posted - 2009.12.23 00:09:00 -
[4]
Edited by: NightF0x on 23/12/2009 00:10:20 Be thankful that he let you know that it was working as intended. I'm about half tempted to do the same thing just to tick you off even more. Instead I'll be the bigger person, well bigger than yourself at least, and explain why it's working as intended.
When a player logs off they warp off in a random direction, you obviously get that part. What your dense head doesn't realize is that when you log off while warping back to the spot that you logged off at that your ship stops and immediately warps off again. Do that a few dozen times and no one will find you. Now why you were still seeing him online is that the server doesn't always immediately show your character offline after you disconnect. Your ship may warp out but your 'presence' may still show as being online because the server hasn't updated your status to everyone that has you in their addressbook. Now knock off the elitist attitude and maybe someone other than me will actually give you a decent answer. Now shoo and cancel your petition so that they can get on to more important ones like all of the billing and GTC issues. ------------------------------------
|
Lork Niffle
Gallente External Hard Drive
|
Posted - 2009.12.23 00:46:00 -
[5]
Thank you for answering that.
Assuming that no combat timers are active when you log off it takes your current position as the warp in point, Regardless whether you are currently warping.
The Character Online status also does not always update as often as it should, meaning that players can appear to be offline or online for long periods of time after they have logged a session. ------------------------------------- The system issues man. |
NightF0x
Gallente Intergalactic League of Terrorists
|
Posted - 2009.12.23 01:24:00 -
[6]
Originally by: Lork Niffle Thank you for answering that.
Assuming that no combat timers are active when you log off it takes your current position as the warp in point, Regardless whether you are currently warping.
The Character Online status also does not always update as often as it should, meaning that players can appear to be offline or online for long periods of time after they have logged a session.
One part of the status update is because the server can't distinguish whether you hit CTRL+Q or disconnected so it keeps the connection 'open' until it times out. That cam be up to a minute I believe. ------------------------------------
|
Ganthrithor
Caldari GoonFleet GoonSwarm
|
Posted - 2009.12.23 07:32:00 -
[7]
Ok, I'm going to give you guys the benefit of the doubt and just assume you read the thread title, first line or two of the op, and then posted irrelevant responses.
I'm not a moron, I know what the ctrl-q trick is. If you'd read my post you would know that this was not a problem with status updates to the addressbook, that the people in question logged in and stayed logged in. You could see them in local for a minute in the first system and when they left local they appeared a system over. They DID NOT DO THE LOGIN TRICK. If you don't do the control-q trick there should be NO WAY to avoid warping back the spot where you logged out. Furthermore, even if they did do the ctrl-q trick their ships would still remain on directional scan for the 1 or 2 minutes (can't remember which) unaggressed ships float in space after a disconnect.
Ewarps are also 1m km. Last I checked, control-q trick or not, your ship is never going to go off directional scan unless you log in, complete your ewarp and cloak up, OR you login/logout and wait 60/120 seconds for your ship to disappear. Ewarps should have no way to take you out of scan range of where you logged off, unless you get the interesting "deep safespot" bug happening (where if you log off in warp and log back in your ship occasionally warps like 20-60au past where it was supposed to, for some reason).
Trust me, I've been playing this game for years, I know what the ctrl-q trick is, I've seen people use it, and it does make people almost impossible to catch, especially capitals who can do it a couple of times and then just jump out. The reason for the post is that people are getting some kind of similar effect without performing the ctrl-q trick. I don't care how you try and spin this, a hauler pilot who logs out on a gate and then logs back in without doing the ctrl-q trick is supposed to land back on the gate. End of story.
|
TheReverend
tr0pa de elite Triumvirate.
|
Posted - 2009.12.23 12:49:00 -
[8]
There are some strange things going on after patch with aggression. I must agree. That ships should appear on directional scanner
|
Lork Niffle
Gallente External Hard Drive
|
Posted - 2009.12.23 13:33:00 -
[9]
Let me explain much more how to prevent landing where you originally logged out.
You Ctrl-Q or log out. You then emergency warp pending all aggression timers 1 million KM in a random direction. When you log back on you proceed to warp the 1 million back to the point you logged off at. If you log off again while warping it takes your current position and emergency warps 1 million kms in a random direction pending all aggression timers. Now when you log back in it will proceed to warp you back to the new point in the line from the original 1 million kms and original log off point. This is all intended and working as the logging mechanics say. Local can take at least a few seconds to update meaning if the Logging is done quick enough i am sure you don't appear on local. ------------------------------------- The system issues man. |
Gajoleus
Gallente Center for Advanced Studies
|
Posted - 2009.12.23 14:40:00 -
[10]
Edited by: Gajoleus on 23/12/2009 14:42:13 And he should show on directional, Ganthrithor probably spammed directional as anyone would. And for person to get out off range of directional scanner would need around 2100 logs, and ship is there for one min after log, it doesn't vanish
|
|
Ribeye Jaksom
GoonFleet GoonSwarm
|
Posted - 2009.12.23 19:12:00 -
[11]
Heh check out this dumb goon trying to have a meaningful discussion with pubbies.
|
Pilk
Mother Lovers Violent Society
|
Posted - 2009.12.24 14:54:00 -
[12]
My best guess would be the cause you already identified, Ganth: namely, the system-created deep SS. Now, every time I've ended up in one, it's been because the server gave me "das boot". For your second instance of this happening, it might make sense that the person in question logged in right around DT, and was thus propelled to a deep SS by the server going down. That does not explain, however, the first instance. I don't suppose there was a node crash in there or anything?
If this happens again, I'd suggest having four combat probes out, set to minimum range, and four DS probes out, set to max range. If you can catch the person logging on well outside of where they should be, you might have something petitionable as an exploit.
--P
Kosh: The avalanche has already started. It is too late for the pebbles to vote. Tyrrax's bet status: PAID! |
nardaq
M. Corp Engineering
|
Posted - 2009.12.24 17:40:00 -
[13]
Edited by: nardaq on 24/12/2009 17:41:31 .mehh
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |