Discuss Rust — Alkad & Tirify Launcher Ban Evasion Traces

[byte_corvus]

Anyone else digging into the Alkad ban logic lately?
Getting clapped on Alkad 1.5x servers is one thing, but the way their launcher handles identities is becoming a headache for those running cracked builds. If a fresh Steam account and a new IP haven't worked, you're likely being tracked via client-side artifacts rather than a standard server-side HWID flag.

Tirify Launcher & Rust Trace Locations
Using Process Monitor to sniff out what RustClient.exe and the Tirify launcher are touching reveals several persistence points. If you're trying to bypass a ban, nuking these is the bare minimum before attempting a rejoin:

1. Global Rust Config: Rust\config.dat
2. Microsoft Cache: AppData\LocalLow\Microsoft\CryptnetUrlCache\
3. Facepunch Identity: AppData\LocalLow\Microsoft\Facepunch\
4. Registry Keys:

   HKEY_CURRENT_USER\Software\Facepunch
   HKEY_CURRENT_USER\Software\Tirify

5. Launcher App Data: AppData\Roaming\tirify-launcher-app

Spoiler: The Tirify Factor

The Tirify launcher seems to generate its own unique identifier and stores session data in AppData\Roaming\tirify-launcher-app. Deleting this folder often allows a temporary rejoin, but if you're getting flagged again within hours, they might be cross-referencing your disk serials or volume IDs alongside these traces. The diff between the original copy (which logs in fine) and the crack suggests the launcher-level tracking is the primary culprit.

Experimental Fixes & Troubleshooting
Testing confirms that Alkad's ban system behaves differently depending on the client integrity. If you can log into the server on a legit copy but get kicked on the crack using the same hardware, the Tirify wrapper is clearly flagging your environment.

1. Nuke the registry keys mentioned above before every launch—don't let them persist.
2. Use a clean MAC address and verify your disk serials aren't being logged via a basic spoofer.
3. Always clear the Cryptnet cache—it's a common "hidden" trace point for custom AC implementations that people often overlook.

Anyone found any deeper hooks in the Tirify assembly or specific offsets being checked? Drop your crash logs or success stories below.