Scritchy Scratchy: Complete Guide To Gadgets

The recent patch for Scritchy Scratchy, version 3.4.7, introduced numerous performance tweaks that were intended to enhance gameplay experience on lower-end hardware configurations. As of March 2026, however, upon testing the game with a GTX 1060 GPU and an Intel i5-9600K CPU under Windows 10 Pro, I encountered some unexpected issues. Running with medium graphics settings and V-Sync enabled, average frame times during the initial levels of Scritchy Scratchy were expected to hover around 42ms; however, they spiked up to 75ms due to what appears to be a bug introduced in this patch.

Performance metrics

The most noticeable performance bottleneck occurred when utilizing the new Spell Book gadget. With it set at level four and the Scratch Bot operating at maximum capacity, my average frame times nearly doubled compared to the levels without active gadgets. This increase from 45ms to 80ms was particularly pronounced during rapid scratch sequences.

Storage impact

Since upgrading to version 3.4.7, there has also been a significant uptick in storage consumption. From an initial size of around 1GB for the base game, post-patch usage jumped suddenly by approximately 500MB, bringing total disk space requirements to roughly 1.5GB.

Scratch that: what’s missing in the patch

Sure, the 3.4.7 update slaps some performance tweaks on paper, but let me tell you, under the hood it feels more like a band-aid job than a comprehensive fix. I noticed the frame time improvements during initial levels were supposed to help lower-end systems, but instead of buttery-smooth 42ms frames, users are stuck with janky 75ms spikes; why even bother claiming progress when the baseline is worse?

And don’t get me started on the Spell Book gadget. In my testing, cranking it to level four felt like playing with fire. The frame times went from a manageable 45ms to an eye-watering 80ms during rapid scratch sequences, what kind of quality-of-life improvement is that It’s more like a downgrade for anyone who actually uses gadgets.

How about the storage hit From 1GB to 1.5GB overnight; ouch. I know some gamers last week had to delete entire game libraries just to make space, and we’re talking about a $30 indie title here. That’s not exactly the goodwill move the developers were aiming for.

Oh yeah, speaking of missed opportunities: what about VRAM usage The patch notes barely mention it, but during testing, I saw VRAM spikes that would cripple systems with less than 4GB. And don’t even get me started on shader compilation stutter—this isn’t addressed at all. It’s like they patched half the game and forgot to finish the job.

Rhetorical question: Why is it always “next patch” for stability when the current one barely holds together We saw a few weeks ago on Discord someone reported crashes during loading screens, and guess what They’re still happening. The forced frame cap promises were supposed to help low-end users, but what good is that if their frames are all over the place?

While we’re at it, let’s talk about something I found frustrating: the patch notes mention “optimized” assets, but in reality, they feel more like bloated ones. And honestly, why isn’t there a rollback option for the users who installed it Some of us didn’t ask for this.

One last thing: the community has been vocal about input lag in certain levels—Reddit had a thread last month about this—and yet, the patch doesn’t even acknowledge it. It’s like they heard our complaints but didn’t feel the need to address them. Meanwhile, we’re left with an update that feels more like a tease than a solution.

Technical synthesis: scritchy scratchy patch 3.4.7

Patch 3.4.7 for Scritchy Scratchy introduces performance tweaks aimed at improving gameplay on lower-end hardware, but in practice, it falls short of its promise. While the 42ms average frame time target during initial levels is commendable, I observed significant spikes up to 75ms due to what appears to be a bug introduced with the Spell Book gadget.

Using the Spell Book at level four and maxing out Scratch Bot capacity resulted in an almost doubling of average frame times from 45ms to 80ms during rapid scratch sequences. This substantial increase raises concerns about optimization, especially when considering lower-end hardware struggling with the baseline performance.

Furthermore, storage consumption has significantly increased post-patch, jumping by approximately 500MB and bringing total disk space requirements to around 1.5GB. While this might not seem catastrophic for users with ample storage, it presents a major hurdle for those with limited drive capacity. Patching shouldn’t mean sacrificing available storage on your system.

The lack of addressing shader compilation stutter, VRAM usage spikes requiring at least 4GB VRAM and reported loading screen crashes further underscores the patch’s incomplete nature. While the forced frame cap might help certain users, the inconsistent frame times negate its effectiveness altogether.

Recommendation:** I would recommend playing Scritchy Scratchy version 3.4.7 only if you have a system capable of handling the increased VRAM requirements and storage overhead (a GTX 1060 and a minimum of 4GB VRAM with at least 1.5GB free disk space). Otherwise, it might be best to skip this patch entirely and wait for future updates that address these concerns.