Weird "comatose" timings (in General)
Yukk
November 11 2008 3:41 PM EST
I've been noticing that occasionally, my whole list will be comatose for 2 or more minutes while I wait for a chance to burn BA. Now, today, I burned a few and then went AFK to settle a crying baby and I come back to the following:
B Ark | Reda Luu | B Ark | 15 | 3:20 PM EST |
B Ark | Reda Luu | B Ark | 17 | 3:19 PM EST |
B Ark | Reda Luu | B Ark | 17 | 3:19 PM EST |
NWO | Reda Luu | NWO | 6 | 3:19 PM EST |
NWO | Reda Luu | NWO | 5 | 3:19 PM EST |
B Ark | Reda Luu | B Ark | 18 | 3:18 PM EST |
B Ark | Reda Luu | B Ark | 15 | 3:17 PM EST |
Reda Luu | Miscellaneous Debris | Reda Luu | 8 | 3:17 PM EST |
Reda Luu | Shadow Lord | Reda Luu | 6 | 3:17 PM EST |
Notice at then end how I was attacked 4x in one minute while away and not fighting. Has anyone else noticed weird timings on their fightlists in the last month or so ?
Sickone
November 11 2008 3:45 PM EST
Try for as long as I've been playing CB.
Since I usually come online to find myself staring at 160 BA and a 10-man fightlist usually (but sometimes as low as 5 and as high as 15, depending on period), I have noticed that the "30 seconds" rule doesn't really apply all that often, at least to me.
It's like the server "freezes" sometimes, and won't "respawn" the targets for up to two minutes, then suddendly afterwards it respawns them very fast, even in as little as 5 or 10 seconds.
The fightlog can also end up out of order. For example, when farming someone, you might notice that you have two fights in a row very often--far more than once every 30 seconds.
Yukk
November 11 2008 3:56 PM EST
Yeah, that's the other side of it. After a 2 minute wait, the list usually refreshes before I can get half way through it.
I just thought it odd that nobody had mentioned it before (as far as I knew anyway)
Sickone
November 11 2008 3:56 PM EST
Since you can easily go through targets at one-per-second (plus 2-3 seconds for botchecks, if any), it's very hard to miss it when your entire list won't respawn at all for a couple of minutes, or when all of them are miraculously alive and ready to be fought non-stop 3-4 times in a minute (and you're the only guy attacking them, and they're all offline, in both cases).
Doesn't happen all that often, but it does happen, and it's seemingly random.
winner winner
November 11 2008 4:02 PM EST
I think I went through 4 fights on the same person last week.
I've noticed that, if you fight and kill someone, and at the same time they fight someone else, you can get unlimited hits in on him. You just need to time it right. I've gotten 8-10 hits in a row on the same guy multiple times.
^i have always attributed that to the fact that your opponent is fighting comatose opponents and healing himself again each time he tries. how accurate that is i am not sure though.
Sickone
November 11 2008 5:08 PM EST
That's a completely different thing when the target is online - each time he clicks "fight", he heals himself, so you can keep attacking him a lot.
What we're talking about here however is your ENTIRE list (consisting of only/mainly characters that are offline) may take much longer or much shorter than the expected 30 seconds to revive.
It's because it's likke BA generation.
Players don't refresh 30 seocnds after you kill them, but on an internal 30 second tick.
o if you're lucky you could fight someone, then the global refresh happens and you get ot fight them (and the rest of your comatose list) right again.
It's why you might see a 1-2 BA refresh, if you spend your first BA right at the moment BA ticks.
But can GL explain why sometimes I wait for 2 minutes on a refresh?
Cube
November 11 2008 9:38 PM EST
Someone else has fought them.
Mikel
[Bring it]
November 11 2008 10:02 PM EST
"But can GL explain why sometimes I wait for 2 minutes on a refresh? "
Jonathan giveth, Jonathan taketh....
Lol Mikel, and no Cubicle, they have no battles on their battle log.
Server hiccup. Internal tick doesn't happen every 30 seconds would be my guess.
Stephen Young
November 12 2008 7:55 AM EST
I agree with GL. The server probably gets stuck every now and then running a cpu-intensive script, and all other scripts (like the one that refreshes the comatose list) get queued until it's over, or just run more slowly.
This thread is closed to new posts.
However, you are welcome to reference it
from a new thread; link this with the html
<a href="/bboard/q-and-a-fetch-msg.tcl?msg_id=002aV4">Weird "comatose" timings</a>