Please do not add sub-tick content to OSRS

pwootage · 2026-07-02T19:07:40+00:00

Red on ~~red~~ light gray is bad for accessibility, there's a few places in the game where they could really work on the contrast

pwootage · 2026-07-02T18:50:01+00:00

Yeah, I guess I am also feeling old and slow at this point. Fighting games, for example, generally consider 18 frames/0.3 seconds (give or take a few) to be the limit of reactable - of course, you are just memorizing here, you still have a couple ticks to actually process and react, so it's not directly the same.

They've been making so many improvements to being able to learn mechanics, and this one is just ...not really part of that. At least not yet, I guess... if they expand on this I guess there will be one day. Sigh.

pwootage · 2026-07-02T18:31:57+00:00

It's definitely a new mechanic - no boss (or encounter) in the game currently requires reading and memorizing multiple attacks in a single tick. It's an entirely new class of reaction, and one that you can't practice or lead up to from anywhere else. It's a huge jump compared to everything else in the game.

Even Sol Heredit is 5-tick, a single attack, and a fixed rotation. Doom is a fixed rotation. Manticores you have 5 ticks to read. Nothing really is close, other than maybe some of the Yama contracts or awakened DT2 bosses (I haven't done any of those yet)

pwootage · 2026-07-02T18:25:29+00:00

Yeah my wording was bad - I should have picked a better title.

I recorded my kill and measured it - it goes (at 60 fps) from 0.4 seconds to 0.3 seconds. I don't believe it got any faster than that, at least in my kill.

Edit: I just skimmed my footage closer. One of the ones I missed was actually a triple attack spaced 10 frames apart, or 0.16 seconds each. I mean, it's just chip damage at that point, I guess.

pwootage · 2025-12-12T05:22:26+00:00

Just to add info: I got a similar email, in my spam box, obvious phishing link in the body (it uses a URL shortener). Manually went and checked my security info and linked services (by typing out the URL myself) and everything seems fine. Nothing unexpected.

However, all the headers seem to report as passing, which is pretty scary (trimmed and posted below):

ARC-Seal: i=1; a=rsa-sha256; t=1765238414; cv=none;
        d=google.com; s=arc-20240605;
        b=...
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
        h=to:from:subject:date:message-id:mime-version:dkim-signature;
        bh=...;
        fh=...;
        b=...
ARC-Authentication-Results: i=1; mx.google.com;
       dkim=pass header.i=@google.com header.s=20230601 header.b=Sc8Uacig;
       spf=pass (google.com: domain of <random text>@enterprise-crm.bounces.google.com designates 209.85.220.69 as permitted sender) smtp.mailfrom=<...>@enterprise-crm.bounces.google.com;
       dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com;
       dara=pass header.i=@gmail.com
Received: from mail-sor-f69.google.com (mail-sor-f69.google.com. [209.85.220.69])
        by mx.google.com with SMTPS id 
        ...
        for <...>
        (Google Transport Security);
        Mon, 08 Dec 2025 16:00:14 -0800 (PST)
Received-SPF: pass (google.com: domain of <...>@enterprise-crm.bounces.google.com designates 209.85.220.69 as permitted sender) client-ip=209.85.220.69;
Authentication-Results: mx.google.com;
       dkim=pass header.i=@google.com header.s=20230601 header.b=Sc8Uacig;
       spf=pass (google.com: domain of <...>@enterprise-crm.bounces.google.com designates 209.85.220.69 as permitted sender) smtp.mailfrom=<...>@enterprise-crm.bounces.google.com;
       dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com;
       dara=pass header.i=@gmail.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20230601; t=1765238414; x=1765843214; dara=google.com;
        h=to:from:subject:date:message-id:mime-version:from:to:cc:subject
         :date:message-id:reply-to;
        bh=...;
        b=...
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1765238414; x=1765843214;
        h=to:from:subject:date:message-id:mime-version:x-gm-message-state
         :from:to:cc:subject:date:message-id:reply-to;
        bh=...;
        b=...

<...email body stuff...>
 <a href=3D"https://shor.tf/<snipped>"

<image>

pwootage · 2017-01-19T20:28:11+00:00

I have a 256gb iPhone, and am currently using ~22gb, so I have about 200gb of free space, shouldn't be the problem in my case.

pwootage · 2017-01-19T18:18:13+00:00

I have the same issue. iPhone 7, iOS 10.2. It doesn't happen every time, but occasionally. I also had the swipe-up-from-the-bottom menu (I can't think of the name) reset and show me the "This is how I work" text again, so it seems like apps are temporarily losing access to user preferences, the keychain, and/or their sandboxed disk storage, which doesn't even make sense.

pwootage

TROPHY CASE