Project1998 · tester setup

The No-Clip Companion

Walking through walls takes two halves: the server's @clip command, and a small companion program on your PC. The server half opens water, cliffs, mobs and players — but the 5.33 client checks building walls on its own, locally, before it even asks the server. The companion opens that last door. It changes nothing on disk and only acts while its window is open — close it and your game is instantly back to normal.

What you need first

One-time install

  1. Double-click Install-Once.bat. It installs the one component the companion needs — Frida, the instrumentation toolkit the script uses to attach to the game.
  2. Wait for it to say Done, then close it. You never need to run it again.
Antivirus heads-up. The companion attaches to the game the way a debugger does, which some antivirus software flags. If Windows Defender or your AV blocks or deletes it, add an exception for the folder. It modifies no files — everything it does lives in memory and ends when its window closes.

Every session

  1. Start NexusTK and log in like normal.
  2. Double-click Start-NoClip.bat. A small black window opens and says it attached to NexusTK.exe. Leave that window open while you play.
  3. In game, type @clip. Walls open up. Type it again to turn them back off — the companion watches for the server's No-clip :ON/OFF status line and flips itself to match, so one command toggles both halves together.
  4. Done testing? Close the black window. Normal collision is restored instantly.
Order doesn't matter: you can start Start-NoClip.bat before or after logging in — it waits for the game and attaches on its own, and if you restart the game it re-attaches automatically. From a terminal, python frida_noclip_533.py is the same thing.

How it works (the short version)

Before the 5.33 client sends a walk, it runs its own collision check against the map's object walls and refuses the step locally — the server never even sees the attempt, which is why @clip alone can open terrain but not buildings. Reverse-engineering found the client's single collision primitive, and the companion hooks it live: while @clip is ON, the check reports "walkable"; while OFF, the hook stands down entirely (so there's no rubber-banding). It's a live, in-memory override, not a patch — nothing is written to the game's files, ever.

Is this cheating? Can a normal player use it?

No. No-clip only actually works when the server lets you through, and that is switched by the staff-only @clip command per session. On its own, the companion does nothing that lets a normal player pass real walls — the server still stops them. It's a testing convenience, not an exploit.

Troubleshooting

SymptomFix
@clip says "Unknown command" Your character isn't on the tester list yet. Ask the admin to add it, then relog.
@clip toggles (you see ON/OFF) but walls still block The companion window isn't running, or it didn't attach. Start Start-NoClip.bat and check it says "attached to NexusTK.exe".
"Python was NOT found" Install Python 3 with "Add Python to PATH" ticked, then run Install-Once.bat again.
Antivirus blocks or deletes it Add an exception for the folder — see the heads-up above.
The game crashes on toggle, or nothing happens at all You're probably on a different client build than the one the companion was made for. Use the client you were given for this server.