CrypticRedHat

DemoPro: The Anti Cheat That Works DemoPro turns F7 reports into a single evidence bundle with timeline markers + jump points, so you can jump straight to the key moments fast. It captures footage Before / during / after the f7 report is made Cheaters can’t hide from this system — no more relying on outdated anti-cheat plugins. This is clear video evidence that makes decisions easier, faster, and fairer. 100% accurate, No False Positives Key Features Converts **F7 reports** into a single evidence bundle Records BEFORE, DURING, and AFTER every F7 report. You NEVER miss what happens. Saves you and your admins loads of time. No more wasting hours spectating players Smart sorts demos with Timeline markers + jump points to reach key moments fast Private portal access for you and your admins with **Steam sign-in** Assignments, notes, outcomes (keeps reviews organised) Server-friendly: all data is stored off-site on your account, not on your game server, keeping things lightweight and smooth. Can be use as a content tool, you can make cinematic videos from the demos you receive. Fully compatible with all Rust server setups. Proof it works: join our Discord and check out the #cheater-clips channel https://discord.gg/2DCfVFFgvW 7-day free trial: https://rustdemopro.com RustAdmin Integration: https://www.rustadmin.com Visual snippet of recoil mapping with each attack in timeline Shareable filtered portal links Discord ban feed + global portal search Redesign the portal + dashboard for a more modern and fluid feel New portal is now live Future Updates AI Integration Introduce an AI/ML system that analyses demo files to learn the difference between normal players behaviour vs a cheaters behaviour All Seeing Eye An AI powered monitoring layer that automatically flags suspicious players and triggers evidence capture without relying on F7 reports. Set Up Guide Step 1 — Create Your DemoPro Space Sign in at https://rustdemopro.com using your Steam account Create your community space Choose monthly or annual billing (includes a 7-day free trial) Step 2 — Install the Harmony Mod Copy the DLL into: server_root/HarmonyMods/ Start the server once to generate: server_root/HarmonyConfig/ (this contains the config) After editing the config, run: rdm.reloadcfg to apply changes Step 3 — Connect Your Server In the portal, generate a Server Key Paste the key into the plugin config Make sure uploads are enabled in the config Reload the config, enter this command in your console rdm.reloadcfg Step 4 — Reports Create Cases When an in-game report (F7) happens, DemoPro automatically builds an evidence bundle The bundle is uploaded to your portal as a case for review Step 5 — Review & Decide Open the case, assign it, and add notes Download the bundle, jump to the timeline markers Mark the outcome as Reviewed (Clear) or Reviewed (Cheating) with notes for your team If you need any help setting up DemoPro, please open a ticket on our Discord. How it works Server records players in 15-minute chunks with ~30 minutes rolling history. When someone is F7 reported, Demo Pro grabs the “before” buffer and keeps recording. 15 minutes later it adds the “after” clip and uploads everything to the portal. If a player disconnects/reconnects, chunk lengths can be shorter than 15 minutes—that’s normal. Portal statuses Players reported → Clip uploaded → Needs Review → Admin downloads → Admin reviews → Mark result Needs Review — new or reset incidents. Downloaded (Needs Review) — someone pulled the bundle but hasn’t finished. Reviewed — Clear / Reviewed — Cheating — finished decisions. Opening & assigning a report Click Open on a card to see details. Assign it to yourself immediately and add notes as you investigate. Set the review state to Reviewed (Clear) or Reviewed (Cheating) when done. Assignments and outcomes keep other moderators from duplicating work. Finding the action fast Timeline dots: hits/shots, kills, report moment. Use the event feed to jump to notable damage or kill events. Report marker shows where the F7 report landed inside the clip. Downloading the bundle Use Download bundle for a ZIP containing .dem files and a README. The README points to the first demo and the timestamp to jump to—start there. Clip lengths can vary if players disconnect; that’s expected. Load demos into Rust Copy the suggested .dem into C:\Program Files (x86)\Steam\steamapps\common\Rust\demos. If the demos folder doesn’t exist, create it (restart Rust once if needed). Playing + controls From Rust main menu, open the Demo browser, refresh, pick the file, and play. Use Alt to toggle cursor, Tab for UI, and debugcamera to free-fly. Cycle nearby players with Spacebar; pause/rewind/fast-forward as needed. Review guidance Use the README timestamps as a starting point; check other demos if nothing obvious. If cheating is confirmed: capture proof, upload to the usual place, mark Reviewed (Cheating), and leave clear notes. If clean: mark Reviewed (Clear) and add a quick note (e.g., desync, valid prefire). long story short, when someone f7 reports, you can get a clip, you replay in rust of exactly why, and it shows footage before and during the report. For tips and useful keybinds to help you get the most out of DemoPro, check out the dedicated channels in our Discord. Discord: https://discord.gg/2DCfVFFgvW Website: https://rustdemopro.com/ Youtube: https://www.youtube.com/@RustDemoPro Cheater Videos

DiscordRaidAlarm is a fully vanilla-friendly Rust plugin and Discord integration that alerts defenders when their base is under attack. It does not rely on Rust+ or any external "seismic sensors.” By detecting building damage in a standard Rust server (Oxide/uMod or Carbon), the system sends raid data to a PHP script with a MySQL database, and a Discord bot delivers real-time notifications to defenders via direct messages. You can either host your own single-tenant bot or register with our public multi-tenant bot (no hosting required). Once Steam-to-Discord mapping is in place, your players receive automated alerts about raids, even on completely vanilla Rust servers.If you need help configuring it, message me on Discord: CrypticRedhat. 1. Overview DiscordRaidAlarm notifies Rust players on Discord if their base is under attack. Its core components: Rust Plugin: Captures damage events and posts them to a PHP script. PHP Script + MySQL: Stores raid data in a raid_events table. Discord Bot: Reads the table and DMs defenders. You can either use: Our Public Multi-Tenant Bot (simplest; no hosting required), or A Self-Hosted Single-Tenant .exe (full control, optional). This guide focuses first on the public multi-tenant bot approach—especially how to invite the bot and use /registertenant. 2. Prerequisites Rust Server supporting Oxide/uMod or Carbon. A web host or cPanel environment for PHP + MySQL. A MySQL database (username, password, DB name, etc.). Token generated from it-tools.tech/token-generator (used across plugin & PHP script, and you’ll provide it to the multi-tenant bot). If you choose to self-host your own bot: A Windows machine and optionally a Discord Developer Portal application for a custom bot token. 3. Token Generation & Matching Go to it-tools.tech/token-generator → click generate. Use that random string for: Rust plugin config (API Auth Token), PHP script (API_TOKEN), And you’ll also provide it to the multi-tenant bot in /registertenant or your self-hosted bot config. All must match exactly or you’ll see 401/403 errors. 4. Rust Plugin Setup (Oxide/uMod or Carbon) Obtain DiscordRaidAlarm.cs. Place in your Rust server’s plugin folder: Oxide: oxide/plugins/ Carbon: Carbon/Plugins/ 3. Load the plugin: Oxide: oxide.reload DiscordRaidAlarm or restart. Carbon: c.reload DiscordRaidAlarm. 4. Config: Check oxide/config/DiscordRaidAlarm.json or similar. Set "API URL" to your DiscordRaidAlarm.php location, e.g. https://yourdomain.com/DiscordRaidAlarm.php. Set "API Auth Token" to the same token from Step 3. Verify no errors. Run oxide.plugins or carbon.plugins to confirm it’s loaded. 5. PHP API Setup Upload DiscordRaidAlarm.php to your web host. Edit lines like: define('DB_HOST', 'localhost'); define('DB_NAME', 'my_database'); define('DB_USER', 'my_db_user'); define('DB_PASS', 'my_db_pass'); define('API_TOKEN', 'YOUR_RANDOM_TOKEN'); Make sure API_TOKEN matches your plugin. Ensure you can reach DiscordRaidAlarm.php in a browser (it may show an error, that’s normal with no parameters). 6. Database Creation Create a MySQL DB or use an existing one. Import create_table.sql: mysql -u my_db_user -p my_database < create_table.sql 3. Check for raid_events: SHOW TABLES; If it’s there, you’re set. 7. Using the Public Multi-Tenant Bot If you don’t want to host a .exe, our public multi-tenant Discord bot can poll your raid_events for you. Below are the two main steps: inviting the bot, then registering your tenant via the /registertenant slash command. 7.1 Invite the Bot to Your Server Click this invite link: Invite It’s pre-configured with minimal but necessary permissions, including Send Messages (crucial for DM or channel posting) and other relevant scopes. Select your Discord server and authorize it. The bot will now appear in your server’s member list. If it can’t send messages or you want slash commands to work, ensure it has the right role/permission in the server. Typically "Send Messages,” "Embed Links,” "Read Messages History,” and "Use Application Commands” are enough. 7.2 Register Your Tenant with /registertenant Open a text channel (or any channel) in the same server where you invited the bot. Type /registertenant. You’ll see a form for: api_url (required) – The URL to your DiscordRaidAlarm.php. api_token (required) – The same token from your plugin + DiscordRaidAlarm.php. steamlink_url (required) – If you’re using a steam-to-discord link system. steamlink_secret (required) – Also for your steam link system. bypass_token (optional) – For some advanced steam link usage. poll_interval (optional) – How often the bot checks your raids, in seconds. Defaults to the global fallback if omitted. Fill out each field carefully: api_url: e.g., https://yourdomain.com/DiscordRaidAlarm.php api_token: your random token. steamlink_url / steamlink_secret: If you do not have a steam linking system, just enter placeholders. (Optional) bypass_token or poll_interval if needed. Press Enter. The bot will respond ephemerally with either "Tenant registered/updated successfully!” or an error message if something went wrong. If successful, the bot automatically logs your server info (guild_id + config) in its multi-tenant DB. From this point on, the bot polls your raid_events table. Done! Whenever your plugin logs a raid, the bot sees it and DMs the defenders (assuming you have steam-to-discord mapping set up). Important: You must run /registertenant from within the server that the bot is invited to. The bot automatically captures your guild_id from the slash command, linking that guild to the api_url + api_token you provided. 8. Self-Hosted Bot (Optional) If you prefer hosting your own single-tenant .exe, skip Section 7 and do this: Create a Discord bot in the Developer Portal. Invite it with permissions like Send Messages, etc. Edit appsettings.json or .config: { "BotSettings": { "BotToken": "YOUR_BOT_TOKEN", "RaidApiUrl": "https://yourdomain.com/DiscordRaidAlarm.php", "RaidApiToken": "YOUR_RANDOM_TOKEN", "PollIntervalSeconds": "10" } } Run DiscordRaidAlarmBot.exe. It polls your raid_events table, DMs defenders. 9. Testing & Verification Trigger a test from your Rust server plugin if it supports a test command (like /raidalarm.test). Otherwise, damage a building block. Check your MySQL raid_events table: SELECT * FROM raid_events; If a new row is added with processed=0, the bot should see it next poll cycle (every 10–30 seconds or your chosen interval). The bot (public multi-tenant or your own) sends direct messages to any defenders with known Discord IDs. If you see "Tenant registered/updated successfully!” from /registertenant but no raids are processed, check Troubleshooting. 10. Troubleshooting No DMs: Possibly defenders’ privacy settings block DMs from that server’s members. The user might not be in the same Discord server. Steam ID → Discord ID mapping is missing if you rely on external link systems. "Tenant registration failed” or 403/401 messages: Mismatched api_token between the Rust plugin, the DiscordRaidAlarm.php, or the data you entered in /registertenant. Typo in the api_url or server didn’t load the plugin. Bot Not Sending: For the public multi-tenant bot, confirm you typed /registertenant in the correct server, and it responded with success. For your self-hosted bot, ensure the .exe is running, the token is valid, and it’s in your server with Send Messages permission. Plugin Not Logging: Check the console logs for DiscordRaidAlarm.cs loading errors. Possibly it’s in the wrong folder for Oxide/Carbon, or you didn’t set "API Auth Token” in the plugin config.