Recomended on Terrible Software

What Actually Survives a Memory Scanner

Thu, 29 Oct 2026 12:00:00 +0000

What Actually Survives a Memory Scanner

Scott Davis · October 2026

A follow-up to Securing Game Data in the Agentic Age.

Building it, then attacking it

In the last post I argued that client-side protection only slows attackers down, and that “AI is making the slowdown barely matter.” I ended with a sketch of a small masked type that re-keys on every write and moves its storage around.

I built it. I also built a memory scanner and pointed it at my own game.

Securing Game Data in the Agentic Age

Tue, 27 Oct 2026 12:00:00 +0000

Securing Game Data in the Agentic Age

Scott Davis · October 2026

Client-side protection has always slowed attackers down without stopping them. AI is making the slowdown barely matter.

To run, a game has to keep a lot of information on the player’s computer that the player is not supposed to use. It knows where every monster is, including the ones nobody has walked up to yet. It knows the real hit points behind a health bar that only shows a sliver of red. It holds the keys that encrypt its own network traffic. The player is not meant to see any of this, but the game needs it to work, and anything the game can read, the person who owns the computer can read too. While this has always been true in the past, what is new is how cheap it has become to take advantage of it with AI.

How I Built a System One Option Scorer like Jev

Sun, 20 Sep 2026 12:00:00 +0000

How I Built a System One Option Scorer like Jev

Scott Davis · Hecaton Labs · September 2026

On September 15, 2026, TypeSafe AI came out of stealth and released Jev, its first System One model, into early access. Jev is not a chatbot. It takes a situation (state), scores a short list of allowed moves (options), and returns a structured choice software can act on. No essay. No tool-call monologue. A decision.

Automating Cursor Updates on Omarchy

Thu, 19 Dec 2024 10:00:00 +0800

Automating Cursor Updates on Linux: A Bash Script Solution

This script has saved me countless hours of manual updates and ensures that I am running latest version of Cursor.

Feel free to modify the script to suit your specific needs, and let me know if you have any improvements or suggestions!ss

As a someone who uses Cursor daily, I found myself manually downloading and updating the application whenever new versions were released. This could me a few times a day. It was super tedious, so I created a comprehensive bash script that automates the entire process. In this post, I’ll walk you through the script and explain how it works.

TDIL: The Magic of Callable.bind in GDScript

Wed, 11 Dec 2024 09:34:12 +0800

TDIL: The Magic of Callable.bind in GDScript

Today I learned (TDIL) about a super helpful feature in GDScript: Callable.bind. If you’re working with signals in Godot and find yourself needing to pass additional data to a single handler, Callable.bind is your new best friend.

The Problem

In many UI setups, you might have multiple buttons that trigger the same function. However, these buttons often represent different actions or carry unique context. For example: A list of character abilities with each button corresponding to a specific skill. A menu system where each button navigates to a different scene or executes a unique task. The usual approach is to connect each button’s pressed signal to the same function. But how do you tell which button triggered the signal? And what if you need to pass more data (e.g., an ID, name, or reference) to your handler?

Terrian 3D: Doing in game actions based on the texture the character is standing on

Wed, 11 Dec 2024 09:34:12 +0800

Terrian 3D: Doing in game actions based on the texture the character is standing on

Enhance gameplay by triggering actions based on terrain textures. Use Terrian3D to fetch texture IDs at the player’s position:

get_texture_id() returns a Vector3 containg Vector3(base texture id, overlay id, blend value).

    @export var terrian:Terrain3D)
    func _physics_process(_delta: float) -> void:
        var texture_pos: Vector3 = terrian.data.get_texture_id(PlayerManager.get_player().get_position())
        print_debug("Texture ID: {0}".format([texture_pos]))

        var base_texture_id = int(texture_info.x)  # Base texture ID (e.g., 1 = Grass, 2 = Dirt, 3 = Sand)
        # base_texture_id is the index of the texture in the terrain from the Terrian3D inspector
        # in my case 1 is grass, 2 is dirt, 3 is sand
        print_debug("Base Texture ID: {0}, Overlay ID: {1}, Blend: {2}".format([base_texture_id, texture_info.y, texture_info.z]))

        match base_texture_id:
            1:
                print_debug("Grass")
                # Trigger grass-related actions
            2:
                print_debug("Dirt")
                # Trigger dirt-related actions
            3:
                print_debug("Sand")
                # Trigger sand-related actions

Use this to adjust movement speed, trigger sounds, or create particle effects for immersive gameplay. It’s simple yet powerful!