My point was essentially that the graph showed plenty of two-hour cycles (and some one-hour naps). I went through the trouble of counting them and got 44 in the first 10 days:



A lot of the slightly red-shaded boxes could mean: Was logged in 1 minute right after the hour started, and then logged in at :59 of the next hour (that's how I do my b/n runs for example). This would basically be equal to 2 hours of sleep on every instance. Definitely more than 9 hours.

Where is the evidence for our scripts? How do you even know that he always scripts when he plays? You don't even know who it is. Please don't pretend you do.

I've stated before that a script for this game that is automated in a way that would make busting feasible (i.e. OCR) is not profitable anymore in this day and age. No one would be crazy enough to either write an OCR for a private script or hire someone to do it, it's quite hard and requires a lot of domain knowledge in various areas of computer science. Add to that the fact that apparently other families, some of them on the other side, didn't have any problems busting that fast and with similar or more ontime as well, and your entire private script theory falls apart.

I wont comment on your claim that I'm buddies with the "main boy" in this game other than saying that I was a) (rightfully) akilled a few years ago when I already knew him, b) Siberia was akilled multiple times since then and c) you would be crazy if you think someone who's invested a good part of his life in this game would risk the future on this game to help some (more or less) random guy he knows online for no apparent gain. It's always fun to see morons like you make those claims, whether it's regarding Bramble or, now that she's gone, KCode. When we're actually losing a version, or get akilled, or get suicided, you people are somehow very quiet. But whenever we end up winning, you come out of your holes like rats and spread your bullshit lies and accuse us of whatever comes to your dimwitted brains. OKAY TURNS OUT I DID COMMENT AFTER ALL. Brb killing puppies.

I don't wanna comment on your other claims, but sustaining a sleep schedule where you wake up every 2 hours is not that hard on your body. It's actually quite close to your natural sleep cycle. To quote:

I've done this myself quite often while ranking and it's manageable for 2 weeks or so. Might be harder if you're someone who has trouble falling asleep again after completely waking up. With that in mind, if you look at the online graph again, you'll see that there was definitely more than 9 hours of sleeping potential.

I like playing with myself. :$

Unfortunately at this point in the version even 15 revived accounts wouldn't make a dent. If any top accounts is gonna be in some kind of dangerous situation, all the other possible shooters are dead by the time those accounts are out of sh. I do get your point though. Just not possible unless akills and revives happen faster.

This particular one had 5 kills I think. Revive policy is generally a pretty hard thing to get right. Realistically, there's no point in reviving those accounts now, as we've seen with the previous revives. Don't get me wrong, a lot of people would be quite happy about a big revive wave, as that would give them something to shoot while waiting for the reset, but that's a pointless exercise and won't change anything.

The only time it would make sense to revive someone would be a) while the version is still open and b) as early as possible after the kill, i.e. detect cheaters sooner. When those criteria are met, I think revives should not be time-limited (which is a policy that is not applied consistently anyway), but rather count for the entire version or, if it can be determined when the cheating begin, starting from that point.

In this particular case the claim is that the two akilled accounts (a soldier and a CDC) were sharing; well, if that's true (and I won't even bother commenting on that, since no one here would give a fuck about what I say anyway), then they should've been sharing all version long and not now that no one is even doing any kind of manual ranking anymore. I find it hard to believe that whatever evidence they claim to have dug up only appeared just now. Oddly, it seems that sharing is something that they quite often only detect very late in the version (not always to our detriment - Hi Daniel and Ari ;().

That logic goes both ways.

Apparently the fee increased in 2016, we didn't get the memo. ;(

Indeed, we pay well.

Yeah it's not like they ever got sharing akills wrong before.

We're happy to accept contributions from anyone via GitHub: https://github.com/OmertaBeyond/OBv2
WIP support for more languages, if anyone wants to pick this up: https://github.com/OmertaBeyond/OBv2/tree/i18n

Support for v5 is very spotty at the moment. We don't have any devs playing v5 currently, so no ETA on when we might have a working version.

I shall go reset .pt (and .nl) in a few minutes; that should fix the testament issues once you clear all OB data on the preferences page.

May I offer you some of my KCode-approved extreme expert sheats?

Free extreme expert safehouse sheats at #Siberia.Recruit

+1

http://downforeveryoneorjustme.com/http://omerta.pt/

Maybe fix your crappy connection or something.

What we have here is a demonstration that evolution is a rather slow process.

I'm afraid I currently don't have access to the necessary drugs to even attempt this mental exercise.

Where's your Service Level Agreement with Omerta Ltd.?

(I know, sorry. Can't help it.)

¯\_(ツ)_/¯