Frequently Asked Questions - notnightwolf/cleanopsT7 GitHub Wiki

Find answers to common questions and solutions for issues related to the Clean Ops T7 patch for Call of Duty: Black Ops 3.

---

Answer:

This is a common issue and is a false positive. Antivirus programs may flag cleanopsT7.exe or cleanops.dll because:

1. The launcher (cleanopsT7.exe) downloads files (cleanops.dll and others) and creates folders within your game directory.
2. It injects the cleanops.dll file into the Black Ops 3 process.
3. The cleanops.dll itself is obfuscated (intentionally made harder to read) to protect the code from misuse. These actions, while safe in this context, are sometimes used by actual malware, causing antivirus software to be cautious.

Solution:

1. Trust the Source: Ensure you downloaded the cleanopsT7.exe only from the official GitHub releases page.
2. Add Exclusions: The most reliable solution is to add an exclusion for the cleanopsT7.exe file, the cleanops.dll file (Call of Duty Black Ops III\cleanops\cleanops.dll) in your antivirus settings (Bitdefender, Malwarebytes, Avast, etc.).
3. Temporarily Disable AV (Use with Caution): You can temporarily disable your antivirus to download and run Clean Ops for the first time, then immediately add the exclusions and re-enable it.
4. Check Quarantine: If the file disappears, check your antivirus quarantine section and restore the file, marking it as safe.
5. Wait: Sometimes, after an update, it takes a few days for Windows Defender to recognize the new file as safe after being submitted for analysis.

Answer:

You can access the Ingame User Interface by pressing the "Insert" key on your keyboard.

If that doesn't work:

1. Check Injection: First, ensure Clean Ops injected correctly. Look for the "Clean Ops T7" text in the top-right corner of your main menu screen. If it's not there, Clean Ops didn't load properly (see FAQ #1 about antivirus or FAQ #10 about skipped intro).
2. 60% / Small Keyboards: If you have a keyboard without a dedicated Insert key (like many 60% keyboards), you might need to use a function key combination (e.g., Fn + another key like [ or ], check your keyboard manual) or change the hotkey FAQ 9#.

Answer:

The mandatory and preferred way to report a suspected cheater is through the Clean Ops in-game user interface while you are in the same live match as the cheater. Reporting from theater mode or only via Discord is generally not sufficient.

1. Open the Clean Ops menu (default key: Insert).
2. Navigate to the "Players" tab.
3. Find the player you suspect of cheating in the list.
4. Click the user icon (inside the wrench icon Column) next to their name.
5. In the window that pops up, click the "Report" button.

Why is this important?

• Reporting this way sends crucial information about the current game session, the reported player's verified SteamID64, and your SteamID64 directly to the Clean Ops team.
• This helps verify the report's legitimacy and ensures the correct player is investigated, preventing issues with spoofed IDs or false accusations.

Additional Steps (Optional but helpful):

• If you have video evidence (e.g., clips showing aimbotting, wallhacking, screen shaking), you can submit it by creating a Report Ticket in the #support channel on our Discord Server and attaching the video link (e.g., YouTube, Medal.tv) or file. This is supplementary to the in-game report.
• You can also use a Report Ticket for context if the situation is complex, but the in-game report is still needed first.

Note: Reporting players for reasons other than cheating (e.g., toxic behavior, using specific weapons/perks) will not result in action. Reporting the same player multiple times in quick succession is unnecessary.

Answer:

To maintain a fair and functional environment, Clean Ops enforces rules based on whether an action provides a clear, game-breaking advantage or requires external cheat software. The goal is to stop game-breaking cheats, not to police individual playstyles.

Bannable Offenses (Cheating): These actions will result in a user being added to the blacklist.

• Using external cheat software (e.g., Aimbot, Wallhacks, Spinbot, No Recoil).
• Using game-breaking exploits like God Mode classes.
• Maliciously and repeatedly crashing servers or kicking other players using exploits.

Non-Bannable Behavior (Discouraged but "Allowed"): These actions are part of the game's mechanics or are long-standing glitches that do not require external cheat engines. While they can be frustrating, they are not grounds for a Clean Ops ban. _{If Treayarch never banned anyone because of these, Clean Ops won't either}

• Modded Classes (Pick-10 Glitch): Using the in-game glitch to have more than 10 items in a class. This has existed since the game's launch and was never patched by the developers.
• Toxic Behavior: Trash-talking, insults in game chat, camping, or using "annoying" weapons (e.g., Brecci, Olympia, P-06).

If you encounter toxic behavior, the best course of action is to mute the player in-game or find a different server using the Server Browser.

Answer:

Game crashes can have several causes when using Clean Ops. Here's a troubleshooting guide:

1. Corrupted Config File: A damaged or incorrectly edited config.json file can cause crashes, often right after injection.

   • Solution: Close the game. Go to the Call of Duty Black Ops III\cleanops folder and delete config.json. Relaunch the game via cleanopsT7.exe. A new default config file will be generated.

2. Discord Rich Presence Issue: Some users experience crashes related to Discord integration, especially if Discord isn't running or running with different permissions (e.g., as Admin).

   • Solution 1: Ensure Discord is running before launching Clean Ops.
   • Solution 2 (If game crashes before UI opens): Close the game. Now you can either manually edit the config.json file in the cleanops folder by setting "DiscordRichPresence":false, or simply replace it with the premade config.json included in the repository (recommended). Then relaunch the game.
   • Solution 3 (If UI opens): Open the Clean Ops menu (Insert), go to Settings -> Discord, and uncheck "Discord Rich Presence".
   • Solution 4 (If none of the Above works): Try disabling the Discord Overlay.

3. Mod/Tool Conflict: Clean Ops conflicts with the original t7patch and potentially other mods/tools that modify game functions (like MXT). Running multiple can cause crashes.

   • Solution: Only run Clean Ops. Remove conflicting patches or tools.

4. Clean Ops Bug (Specific Scenarios):

   • Server Browser Crash: A known issue could cause crashes when interacting heavily with the server browser tab. Try avoiding that tab if crashes persist.
   • Rare/Unknown Crashes: Sometimes crashes occur randomly. A PC restart can occasionally resolve temporary issues. If crashes persist and produce an exception_*.txt file in the cleanops\logs folder, submit it in a support ticket for investigation.

5. Corrupted Game Files: Less common, but BO3 files might be corrupted.

   • Solution: Verify the integrity of game files via Steam (Right-click BO3 in Library > Properties > Installed Files > Verify integrity...).

Important: Always ensure you're running the latest version of the Clean Ops launcher (cleanopsT7.exe) downloaded from the official GitHub releases.

Answer:

This error message appears in the console window when launching cleanopsT7.exe and means the launcher could not download the necessary cleanops.dll file from GitHub.

Causes & Solutions:

1. Antivirus / Firewall Blocking: Your antivirus (e.g., Bitdefender, Malwarebytes, Avast, etc.) or firewall might be blocking the download connection to GitHub or flagging the download itself.

   • Solution: Check your antivirus/firewall logs. Add an exclusion for cleanopsT7.exe and cleanops.dll ALSO potentially allow connections to GitHub or temporarily disable the AV/firewall during the first launch to download the files, then add exclusions and re-enable. See FAQ #1. For some users a PC restart after adding exclusions will help for it to take effect.

2. Network Issues: A poor internet connection, VPN interference, or specific network settings could block direct downloads from GitHub.

   • Solution: Check your internet connection. Temporarily disable your VPN to see if it resolves the issue. Check if any network-level filters might be blocking GitHub downloads.

3. Permissions Issue: The launcher might lack the necessary permissions to write the downloaded file to the cleanops folder within the game directory.

   • Solution: Try running cleanopsT7.exe as an Administrator (Right-click > Run as administrator). This often helps if the game is installed in a protected location like Program Files.

4. Temporary GitHub/Network Outage: Although rare, the connection might fail due to temporary issues outside your control.

   • Solution: Wait a few minutes and try launching again.

Troubleshooting Steps:

1. Ensure cleanopsT7.exe is in the main Black Ops 3 directory (not inside the cleanops subfolder).
2. Check your antivirus quarantine and add necessary exclusions (FAQ #1).
3. Try running cleanopsT7.exe as Administrator.
4. Temporarily disable VPN/Firewall for testing.
5. Restart your PC (this has surprisingly fixed download/injection issues for some users).

Answer:

This error typically occurs shortly after launching the game with Clean Ops and prevents the patch from fully initializing, often closing the game.

Causes & Solutions:

1. Interference from other Programs: Software modifying the Steam client (e.g., certain overlay tools) might interfere with Clean Ops reading your SteamID.

   • Solution: Try closing any such third-party programs related to Steam before launching Clean Ops.

2. Temporary Steam Client Issue: Sometimes the Steam client itself might be in a state that prevents the ID check.

   • Solution: Restarting your PC can often resolve temporary glitches with the Steam client or related processes.

Answer:

Getting kicked or disconnected can happen for several reasons:

1. Being Kicked by Other Players: Some players (often cheaters) can kick other players from the lobby using exploits. Sometimes specific players target Clean Ops users or anyone they dislike.

   • Can Clean Ops prevent this? Clean Ops patches some kick methods, but not all are patchable, especially ones that drop your connection server-sided.

   • Solution: Unfortunately, there's often little you can do other than try joining a different server or waiting for the disruptive players to leave or get bored. Keeping a low profile (e.g., not using provocative names) might help avoid being targeted, but isn't guaranteed.

2. Server Crash: Sometimes the entire server crashes, kicking everyone. This can be caused by cheaters using server crash exploits or just server instability.

3. Steam Server Maintenance / Disconnects: Occasionally, Steam itself has temporary connection issues or maintenance, which can cause a "Lost connection to host" or similar message. This usually affects multiple players.

   • Solution: This resolves itself. Wait a few minutes and try rejoining.

4. Playlist Update: When the game's featured playlist updates, you might get kicked and see an error about "game settings have changed."

   • Solution: Restart your game to get the updated playlist data. You might need to queue normally for the first match instead of using the server browser immediately after an update.

5. Kicked by Clean Ops (False Positive/Bug - Rare): In very rare cases, there might be a bug causing Clean Ops itself to kick you (e.g., a false positive on the spoofed ID check).

   • Solution: If it persists, open a support ticket on our Discord Server with details.

6. Kicked for DLC Map (If Spoofing DLC): If you enabled "Spoof DLC" in Clean Ops settings (Tools -> Spoofing) but don't actually own the DLC files, you will be kicked when a DLC map loads.

   • Solution: Disable "Spoof DLC" if you don't have the map files, or acquire the necessary files (Clean Ops does not provide these).

If you suspect a specific player is repeatedly kicking you unfairly, reporting them may eventually lead to them being blacklisted if they are also found to be cheating, but Clean Ops cannot directly stop all kick methods.

Answer:

You can change the key used to open/close the Clean Ops menu (default is Insert) in two ways:

1. Using the In-Game UI (Recommended if possible):

   • Open the Clean Ops menu with the current hotkey (default: Insert).
   • Go to the "Settings" tab.
   • Expand the "System" submenu.
   • Find the "Hotkey Value" text field.
   • Click the "available hotkeys" button next to it. This opens a Microsoft webpage listing Virtual-Key Codes.
   • Find the key you want to use on the webpage and copy its hexadecimal value (the column starting with 0x..). For example, F1 is 0x70.
   • Paste or type this hexadecimal value (including the 0x) into the "Hotkey Value" text field in the Clean Ops menu.
   • Crucially: Click the small arrow button (->) to the right of the text field to save and apply the new hotkey.

2. Editing the Config File (If you cannot open the UI):

   • Close Black Ops 3 completely.
   • Navigate to your Black Ops 3 installation folder, then into the cleanops subfolder (e.g., C:\Program Files (x86)\Steam\steamapps\common\Call of Duty Black Ops III\cleanops).
   • Open the config.json file using a text editor (like Notepad).
   • Locate the line that looks like "Hotkey":"0x...". The default value is "0x2D" for the Insert key.
   • Replace the existing hexadecimal value (the part starting with 0x inside the quotes) with the new hexadecimal value for your desired key from the Microsoft Virtual-Key Codes page. For example, to set it to F1, change it to "Hotkey":"0x70".
   • Ensure you only change the value inside the quotes and keep the 0x prefix. Do not enter the key name (like "VK_F1").
   • Save the config.json file.
   • Relaunch the game using the Clean Ops launcher. The new key should now work.

Answer:

If you launch the game using cleanopsT7.exe but the "Clean Ops T7" text doesn't appear in the top-right corner and pressing Insert (or your custom hotkey) does nothing, the cleanops.dll likely failed to inject properly.

Causes & Solutions:

1. Intro Animation Skipped/Missing: Clean Ops injects the DLL during the game's initial startup/intro video sequence (Treyarch/Activision logos etc.). If you have renamed or deleted the video files (e.g., bo3_global_logo_logosequence.mkv in the video folder) to skip the intro, the injection timing will fail.

   • Solution: Restore the original intro video files. If you deleted them, verify game files via Steam (Right-click BO3 > Properties > Installed Files > Verify integrity...).

2. Antivirus Interference: Your antivirus might be blocking the injection process itself or deleting cleanops.dll silently.

   • Solution: Double-check your antivirus quarantine and ensure cleanops.dll and potentially cleanopsT7.exe are excluded. See FAQ #1.

3. Incorrect Launcher Usage: You must launch the game using the cleanopsT7.exe file placed in your main Black Ops 3 directory. Launching BlackOps3.exe directly or via Steam library will not load Clean Ops. Injecting manually with tools like Process Hacker/System Informer is possible but requires specific timing (during intro) and bypasses the launcher's update checks.

4. Incomplete/Corrupted Clean Ops Files: If the cleanops folder or its contents are missing or corrupted (e.g., due to failed download or AV action), injection might fail.

   • Solution: Delete the cleanops folder entirely and relaunch using cleanopsT7.exe to allow it to redownload necessary files.

5. Game/System State: Rarely, a lingering game process or system state might interfere.

   • Solution: Check Task Manager for any BlackOps3.exe or crashuploader.exe processes and end them. Try restarting your PC.

Verify the "Clean Ops T7" text appears in the top-right corner as confirmation of successful injection.

Answer:

Clean Ops includes a fix specifically designed to improve FPS by disabling constant Steam DLC checks. However, some users, particularly those with older or lower-spec hardware, have reported experiencing FPS drops or stuttering with Clean Ops enabled, while vanilla BO3 runs smoother (though potentially at a lower overall framerate).

Possible Causes & Solutions:

1. Hardware Limitations: Black Ops 3 can be CPU-intensive. Clean Ops adds some overhead (checking player lists, running protections, UI rendering). On older CPUs that might already be near 100% utilization, this extra load could cause stutters or drops.

   • Solution: Monitor CPU/GPU usage via Task Manager or overlay software. If the CPU is constantly maxed out, the hardware might be the bottleneck. Lowering in-game graphics settings might help free up resources. Performance improvements are considered by the developers, but significant gains on very old hardware may be limited.

2. Background Processes: Other applications running in the background could be consuming resources.

   • Solution: Close unnecessary background applications while playing.

3. V-Sync / Frame Limiters: While intended to smooth gameplay, certain settings can sometimes cause issues.

   • Solution: Try toggling V-Sync off in-game. If using an external frame limiter, try disabling it or setting it slightly below your monitor's refresh rate. Clean Ops itself doesn't directly control these settings.

4. Clean Ops Feature Interaction (Less Likely): It's possible a specific feature (like the blacklist check or UI rendering) is less optimized on certain hardware configurations.

   • Solution: We occasionally work on performance optimizations. There are no user-configurable settings within Clean Ops to specifically reduce its performance impact besides closing the UI when not needed.

If performance is significantly worse only with Clean Ops compared to vanilla BO3 on capable hardware, consider creating a support ticket with your PC specs and details about when the stuttering occurs.

Answer:

Clean Ops identifies and removes cheaters based on a manually curated database.

1. Identification: Cheaters are typically identified visually in-game by moderators, administrators, or reported by users (using the in-game report function, see FAQ #3). Obvious cheating behaviours (aimbotting, wallhacking, spinbotting, godmode, etc.) are the primary criteria. Reports must be verifiable (e.g., through live spectating, theater mode review if clear enough, or video proof). Modded stats/levels/classes alone are not grounds for adding someone to the blacklist.
2. Database: Verified cheaters' SteamID64s are added to a central, secure database maintained by the Clean Ops team.
3. Detection & Kicking: When a player using Clean Ops joins or is in a multiplayer lobby, the patch checks the SteamID64 of every player present against the blacklist database.
4. If a match is found (i.e., a blacklisted player is in the lobby), Clean Ops automatically initiates an action to disconnect that specific player from the server session. This happens regardless of whether the cheater is using Clean Ops or not.
5. A log message like [anti cheat] PlayerName | SteamID64 usually indicates a successful kick initiated by Clean Ops.

Difference from t7patch by serious:

• The old and outdated t7patch primarily focuses on patching security vulnerabilities (like RCE exploits) and fixing some game bugs (like FPS drops).
• Clean Ops T7 includes all the essential security and bug fixes PLUS the automatic cheater removal feature based on its blacklist database, the server browser, the reporting system, and other quality-of-life features.
• Because Clean Ops replaces t7patch's features, they are not compatible and should not be run together. Clean Ops is intended as a complete replacement, especially for multiplayer.

1st Answer:

This issue is typically related to the IP-Spoofing feature in Clean Ops, which is designed to protect your real IP address. Black Ops 3 requires players' real IP addresses to establish direct connections for party invites/joins in the main multiplayer menu.

Symptom: You cannot invite friends, or they cannot join you.

• Solution:

  • Temporarily change the "Networking Protection" setting (Settings -> Protections) to "Friends Only" or "Everyone" but this partially defeats the purpose of IP spoofing while the setting is active. Remember to set it back to your preferred protection level afterwards.

Symptom: You cannot join a public match as a party.

• Solution:

  • The "Advanced IP-Spoofing" feature, while providing extra security, is known to prevent parties from joining a public match together. In the Clean Ops menu, go to Settings -> Protections and uncheck this option.

2nd Answer:

• NAT Type Mismatch: If problems persist, it could be a NAT Type mismatch. All players should ideally have an "Open" NAT type. This may require configuring port forwarding on your router. You can find the specific ports on the Activision Support Page.

Answer:

No, Clean Ops T7 does not include an "Unlock All" feature for weapons, camos, specialist gear, levels, Black Market items, etc.

• Its primary focus is on security, anti-cheat, bug fixes, and quality-of-life improvements for multiplayer.
• Adding unlock tools is considered outside the scope and philosophy of the project.
• Using external tools like MXT for unlocking items while running Clean Ops may cause conflicts or crashes (see FAQ #15) and has led to players being added to the Clean Ops blacklist for cheating if aimbot/other cheats were used, even briefly.

While we have mentioned potentially considering such features far in the future, it is not a current priority. If you received free Black Market packs upon first launching Clean Ops, this was likely an unintended side effect of the DLC spoofing feature (used for FPS fixes) interacting with how the game grants promotional items, not an intentional unlock feature.

Answer:

Clean Ops T7 is generally not compatible with other mods or tools that modify Black Ops 3's core functions.

• t7patch by serious: Clean Ops includes all necessary security and bug fixes. Running both simultaneously will cause conflicts and likely crashes, as they try to modify the same parts of the game. Do not use both.
• Cheat Menus (MXT, etc.): Injecting other menus alongside Clean Ops will cause instability and crashes. Furthermore, using cheats provided by these menus will get you banned by Clean Ops.
• Zombies Mods (e.g., All-around Enhancement): Compatibility varies. Simpler mods might work, but complex mods like All-around Enhancement, which heavily modify game scripts and functions, have been reported to cause issues or prevent Clean Ops features from working correctly (or vice-versa). Use caution and expect potential instability. Clean Ops is primarily designed for multiplayer.

Recommendation: For the best stability and intended functionality, run Clean Ops T7 standalone without other DLLs, injectors, or major game modification mods active.

Answer:

If Clean Ops prevents you from playing multiplayer and displays a message indicating you are banned, it means your SteamID64 is on the Clean Ops blacklist.

Reasons for Being Banned:

• Cheating: The primary reason is being caught cheating in a multiplayer match (aimbot, wallhack, spinbot, godmode, etc.) and subsequently reported via the Clean Ops UI and verified by the team.
• Malicious Actions: Repeatedly crashing/kicking other players using exploits can also lead to a ban.

How to Appeal:

1. Go to the #support channel on the Clean Ops Discord Server.
2. Click the dropdown to create a new ticket.
3. Select the "Appeal a Ban" ticket type.
4. Provide your Steam Profile URL or SteamID64.
5. In the "Additional Information" section, politely explain why you believe the ban might be incorrect or request reconsideration.

Important Considerations:

• Behavior: Threats, insults, or demanding behavior towards the support team will likely ensure your appeal is denied and may result in removal from the Discord server.
• Ban Scope: A Clean Ops ban only prevents you from playing in lobbies where at least one other player is running Clean Ops. It does not affect your Steam account or vanilla BO3 access (though vanilla is unsafe).

---

If your issue is not covered here, please check the entirety of the GitHub Wiki or ask for help in the #support-public channel or create a ticket in the #support channel on our Discord Server.