Anti-Cheat Guide
How Refinery Caves 2 catches cheaters, what the script does about it, and what you should know before using risky features.
The Short Version
RC2 does not use a traditional instant-kick anti-cheat like some other games do. Instead, the game quietly logs what you do and sends that data to a Discord server where moderators look through it by hand. If something looks off, a mod reviews your account and bans you manually.
This means you will not get auto-kicked the moment you press a button. But it also means that doing anything obviously inhuman, especially farming or earning money at an unnatural pace, can get flagged and reviewed later. Private servers do not protect you from this either, since the logging happens on the server side.
What The Game Logs
There are two separate layers of detection in RC2. The first is server-side, and the second is client-side.
Server-Side Logging
This is the main threat. The game server directly tracks your actions, things like how much you mine, how often you sell, what fish you catch, and how fast your money goes up. None of this can be blocked from the client because it all happens on the server. This is what moderators actually look at when they decide whether to ban someone.
The things the server tracks include:
- Mining actions and how often they happen
- Sell transactions and the amounts involved
- Item pickups and inventory changes
- Fishing activity and fish catch rates
- Harpoon and big fish kills
- Movement patterns tied to interactions
- Overall currency velocity, basically how fast your balance climbs
If any of these numbers look way too high or way too consistent, it gets flagged. A moderator then checks the logs and decides whether to ban.
Client-Side Telemetry
On top of the server logs, the game also runs a few client-side scripts that report extra data back to the server. These are less important than the server logs, but they give moderators more information.
- WeakSecurity1 – Checks your backpack for tools tagged as forbidden. If you somehow have a tool you should not have, it reports the tool names to the server.
- NetStatsReporter – Reads your network stats every few seconds and sends them to the server. This can flag unusually high data rates or other network anomalies.
- CoreUI – Uses a detection trick to see if certain persistent UI elements exist in CoreGui. If it catches one, it kicks you from the game. This one is a local kick, not a server ban.
What The Script Does About It
The RC2 script handles the client-side telemetry automatically when it loads. You do not need to toggle anything on for this. Here is what happens behind the scenes:
- The WeakSecurity1 and NetStatsReporter scripts are disabled and removed before they can run.
- All remotes in the Security folder and the NetStatsReport remote are intercepted. Any calls to them get silently blocked so they never reach the server.
This means the client-side reporting layer is effectively gone. But here is the part people often misunderstand: blocking these scripts does not stop the server-side logging. The server still sees every mining action, every sell, every fish you catch, because those happen through normal gameplay remotes that the game needs to function. Blocking those would break the game.
Risk Levels
Not every feature carries the same risk. Here is a rough breakdown.
Low Risk
Features that only change what you see or give small quality-of-life improvements. These do not create any unusual server activity.
- Runestone ESP and Big Fish ESP
- Fullbright, no fog, anti-underwater effects
- Anti storm shake and anti storm visuals
- Clock overlay
- Vehicle fly and click teleport
- Waypoint system and location teleports
- Hookling-8 speed launcher and cooldown bypass
- Harpoon aimbot and mounted harpoon aimbot
- Auto reel and auto pull
- Instant machine fix
- Blue Moon finder
Higher Risk
Features that automate earning money or resources. These are the ones that create obviously abnormal patterns in the server logs.
- Auto Farm, the full mine-and-sell loop
- Auto Mine on its own
- Fish Farm, the automated fishing loop
- Shoot Nearest Big Fish automation
The script shows a warning popup before enabling any of these features. That warning is there for a reason. These features work, but the more aggressively you use them, the higher the chance that a moderator notices the pattern in the logs and bans you.
Warning Popups
When you try to enable Auto Farm, Auto Mine, Fish Farm, or Shoot Nearest Big Fish, a warning modal appears. It explains what the risk is and asks you to accept it before the feature turns on. You can check a box to suppress the warning for the rest of that session, but it will come back next time you run the script.
These warnings exist because we do not want anyone thinking these features are safe just because they technically work. They do work. They also leave a trail in the server logs.
Staffwatch
Staffwatch is a protective feature that monitors for game staff joining your server. It checks if any player in the server is a member of the RC2 staff Roblox group or the developer team group. It also checks for chat tags that indicate staff roles.
When staff is detected, Staffwatch does a few things depending on your settings:
- Visual alert – Shows a notification on screen with the staff member's name and role.
- Sound alert – Plays an alert sound so you notice even if you are not looking at the screen.
On top of the alerts, you can set an automatic action that triggers when staff is detected:
- None – Just alerts you. You decide what to do.
- Kick Self – Immediately kicks you out of the game.
- Server Hop – Finds a different public server and teleports you there. Tries up to five different servers before falling back to a random one.
- Rejoin – Teleports you back into the same server. Useful if you just want a fresh connection.
- Disable Cheats – Turns off every active cheat feature instantly. Everything goes back to normal gameplay, so if a mod is spectating you, there is nothing to see.
Staffwatch runs continuously while enabled. It checks all current players on load, watches for new players joining, and re-scans every few seconds in case group data was slow to load the first time.
What This All Means In Practice
- Visual features, movement tools, and quality-of-life stuff are generally fine. The server does not care that you turned on fullbright or teleported across the map.
- Automation features that earn you money or resources are the risky ones. The more you use them, and the more extreme the earnings, the more likely a moderator notices.
- Private servers do not help. The server logging is the same regardless of server type.
- Bans from RC2 are manual. That means there is no appeal to a false positive algorithm. A real person looked at the data and chose to ban.
- Staffwatch gives you a safety net, but it is not a guarantee. A moderator does not have to join your server to review your logs.
- Reports from other players suggest that light usage can survive for days, while aggressive farming can lead to bans the same day.
- Using alts is not a reliable workaround. There have been reports of linked bans across main and alt accounts.
Summary
The script blocks the client-side reporting that it can reach and gives you staffwatch to stay aware of moderators. But the biggest risk in RC2 comes from server-side behavior logs that no client-side script can touch. If you use the risky features, keep it moderate and know what you are signing up for.