hooking?)

Hi everyone,

I'm playing an old Flash game that originally ran on the web using an embedded .swf file. However, nowadays most users play it using auto clients (bots) instead of the original game client provided by the publisher.

These auto clients are far more optimized and feature-rich than the official client. What really puzzles me is that they somehow add new UI windows and features that never existed in the original game. I'm guessing they may have modified the .swf file somehow to inject these new interfaces, but that raises a big question:

The game is still active and updates weekly (with new events and data). If the UI is being added by modifying the .swf, wouldn't that mean the devs of the auto client have to patch their version every single week? That doesn’t seem to be the case—I don’t have to download a new auto client every week.

A few more technical details:

• The auto clients are usually just two .exe files—no .dlls or anything extra.
• There’s sometimes an .ocx file bundled, likely to support Flash runtime in case the system doesn’t already have Flash installed.
• I highly doubt these clients are written in C# or Java (again, no extra runtime files).

So, my questions:

1. How do these EXEs hook into the game logic and add new UI/windows that weren’t there originally?
2. Are they modifying the .swf at runtime? Injecting into memory? Hooking Flash API calls?
3. How do they stay compatible with weekly updates if the .swf content is constantly changing?

If anyone has experience with Flash internals, reverse engineering, or making auto clients, I’d really appreciate some insight. Thanks in advance!