Jump to content

CrypticRedHat

Creator Pro
 View Profile  See their activity

  • Posts

    136

  • Joined

  • Last visited

 Content Type 

Everything posted by CrypticRedHat

  1. CrypticRedHat
    More information about ""
    Hey! It is on the website which is linked in the description - currently it is £9.99 a month, and don't foresee a price change in the future.
  2. CrypticRedHat
    More information about ""
    Hey! It is on the website which is linked in the description - currently it is £9.99 a month, and don't foresee a price change in the future.
  3. CrypticRedHat
    More information about ""
    Sure, let me have a look over the next few weeks
  4. CrypticRedHat
    More information about "DemoPro - AntiCheat"

    Version 0.2.1

    70 downloads

    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 Coming Soon 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
    Free
  5. CrypticRedHat
    More information about ""
    Done now, released in v2
  6. CrypticRedHat
    More information about ""
    Yes, there is a permission which is needed for you to be limited. When you load the plugin you'll see the perms
  7. CrypticRedHat
    More information about ""
    Patched in 1.7.3 thank you
  8. CrypticRedHat
    More information about ""
    Ignore me, I see the issue - in the patch that was pushed by FP. Let me sort this and get back to you asap.
  9. CrypticRedHat
    More information about ""
    Looks like an image library thing, can you check you have the latest version of that, and reload it in the following order unload: OfflineraidLimiter SimpleStatus ImageLib load: ImageLib SimpleStatus OfflineRaidLimiter
  10. CrypticRedHat
    More information about ""
    I have DMd you
  11. CrypticRedHat
    More information about ""
    Okay thanks, I will investigate and test it now - do you happen to have discord, it may help with some questions I may need about your environment to reproduce?
  12. CrypticRedHat
    More information about ""
    Is this on Oxide or carbon? Are you using any other raid limiting tool?
  13. CrypticRedHat
    More information about ""
    Correct, it tracks if they were online or offline when the first entity was destroyed, based on that being online or offline, defines what it stays as. EG starts online and they log off half way through, it’s still and online, vice versa
  14. CrypticRedHat
    More information about ""
    SimpleStatus handles the placement etc, double check you are on the latest version and reload let me know
  15. CrypticRedHat
    More information about ""
    It groups. The default config is configured really well, and it considers multiple externals and a main as a single offline raid. So no need to worry about it counting as 2/3/4. It knows if a base has externals, or a small heli base next to it etc, which in reality is part of the same base.
  16. CrypticRedHat
    More information about "Discord Raid Alarm"

    Version 1.0.1

    30 downloads

    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.
    $29.99
  17. CrypticRedHat
    More information about ""
    I am posting v1.6.0 soon, I will look at this in more detail very soon - and potentially add it in a subsequent update. I will update you in the coming days.
  18. CrypticRedHat
    More information about ""
    It doesn’t allow you to set an overall limit per week or server wide. I could implement this if there was enough flak for it, although to be honest - I’d be surprised, I can’t see why this would be a good idea although I’m open to discussion, I think any players would be in uproar though. I can see a single team using the entire limit for the whole server every wipe or week
  19. CrypticRedHat
    More information about ""
    I do have discord, although I prefer any support/issues to be via codefling, as it helps other users - although if there is an issue and we need to speak or you need assistance setting up, you can pm me here and we can chat in discord.
  20. CrypticRedHat
    More information about ""
    You have full control via config on the qty of offlines you allow per 24 hours You can set this to 1, or 100, however you please We have an update soon where you can temp disable it too, which will release in the next week.
  21. CrypticRedHat
    More information about ""
    If someone starts a raid as an online, and the defenders log off once the raid has begun, it is not considered an offline, therefore is not counted. If they log off before anything's been destroyed, it is counted as an offline. There is no grace period. This is to avoid people tracking player with BM and waiting for them to log off and raiding immediately after to circumvent the plugins logic.
  22. CrypticRedHat
    More information about ""
    Its important to note, also taking your other comment into account, this is not an offline raid protection tool This tool limits the quantity a player or team can offline raid, it does not strictly protect a players base. However it does stop someone from offline raiding more than x bases per day. The plugin you may be comparing with, I'm my opinion offers a different use case for functionality. In theory your base may be protected against someone with more than for example say, 1 offline raid, but may be raided offline by another player who has not yet reached that limit. This tool is great to stop players mass offlining the whole server, while not taking the originality out of rust by blanket blocking offline raids, other plugins may and will perform differently
  23. CrypticRedHat
    More information about ""
    Yes this works correctly with raidable bases, as long as you have the latest version
  24. CrypticRedHat
    More information about "Base Guardian"

    Version 1.1.1

    194 downloads

    BaseGuardian ensures that sudden server restarts, forced crashes, or network drops won’t leave players’ bases vulnerable, by closes all doors. It also automatically boosts Tool Cupboard upkeep to a safe threshold, preventing unexpected decay. Designed for simplicity, fairness, and seamless integration with Rust’s native upkeep rules, BaseGuardian takes server management to the next level—now with added options for automated protection. Key Benefits Automated Crash & Network Handling BaseGuardian can automatically close all doors and top up Tool Cupboards whenever it detects a crash or network outage. No manual intervention needed—players stay protected even if you’re offline. Instant Door Security With a single command, any open door, gate, shutter, or ladder hatch across the map is snapped shut—especially helpful right after a server crash or restart. Accurate Upkeep Top-Ups BaseGuardian brings each qualifying Tool Cupboard’s coverage up to a pre-set number of hours (default: 12 hours). Because it taps into Rust’s own upkeep balance, each base pays only for the exact time and resources it needs. Fair for All Base Sizes Larger or higher-tier bases require more resources to stay protected; simpler bases need less. No one’s overpaying, and no hidden shortcuts are involved. Permission-Based Commands Two separate permissions let you decide who can close doors and who can top up TCs. This prevents misuse and keeps server management firmly in your control. No Leftover Resources Once upkeep is topped up, materials are seamlessly consumed to provide the extended coverage. Players don’t find unexpected piles of items in their cupboard—just the additional time they need. Minimal Disruption Although the plugin checks multiple entities, it’s designed as an on-demand tool for admins. Run it when needed (e.g., after a restart) with negligible impact on your server’s performance. Commands & What They Do Close All Doors Command: bg.doors Effect: Closes every door, gate, shutter, and ladder hatch on the server if they’re open. Use Case: Ideal after forced restarts or when an admin wants to ensure no player base is left open during downtime. Top Up Tool Cupboards Command: bg.tc Effect: Scans all non-abandoned TCs, and brings each one’s upkeep coverage to a default threshold (12 hours). The plugin accounts for each base’s size/tier, creating and using only the necessary resources. Use Case: Perfect for preventing mass decay after downtime or ensuring players have a fair buffer when forced offline. Frequently Asked Questions "Why don’t I see extra resources in the Cupboard afterwards?” BaseGuardian immediately converts spawned materials into extra coverage. You won’t see leftover items because they’re fully used to boost the TC’s timer. "How is the upkeep cost determined?” The plugin uses Rust’s own upkeep system to decide what’s required for the final hours. Larger or more complex buildings need proportionally more resources, while simpler bases pay less. "Can I change 12 hours to a different amount?” Yes. The plugin defaults to 12 hours, but you can adjust it to match your server’s rules—such as 8, 10, or 24 hours—ensuring any forced downtime doesn’t unfairly penalize players. "What if a TC has fully decayed already?” By default, BaseGuardian skips TCs with zero coverage. If you prefer to ‘rescue’ those TCs, you can modify the plugin’s settings to do so. "Does this run automatically?” Now it can! Besides manual commands, the new version detects crashes or network issues and handles door closures/TC top-ups automatically—keeping your server protected even when you’re not there. Permissions BaseGuardian’s two core features—closing doors and topping up TCs—are independently permissioned. This means you can give some staff the ability to secure doors, while only a few select admins can top up everyone’s upkeep, or vice versa. Check your server’s mod framework documentation for how to manage these permissions. Door Closure Permission: Allows the use of the door-closing command. TC Top-Up Permission: Allows the use of the upkeep top-up command. Why BaseGuardian? Defends Offline Players: Protects your community from uncontrollable downtime and forced restarts. No Game-Breaking Workarounds: Aligns with Rust’s native decay and upkeep standards without creating artificial advantages. Unobtrusive: Kicks in only when you command it, so normal gameplay is never disrupted. Transparent & Fair: Ensures players’ bases remain intact if they can’t reconnect promptly, boosting server reputation and trust. With BaseGuardian, your Rust server stays secure and fair—no matter how abruptly it reboots or how large the bases get. It’s a small but invaluable addition for any admin who wants peace of mind and a satisfied player community. A special thanks to EU Game Host for generously providing free server hosting to support the development and testing of BaseGuardian. Your assistance has been instrumental in helping this project flourish and ensuring the Rust community enjoys a smooth, reliable experience. UK Game Server Hosting - EUGAMEHOST
    Free
  25. CrypticRedHat
    More information about "Offline Raid Limiter"

    Version 2.0.0

    226 downloads

    Offline Raid Limiter Stop Unfair Offline Raids in Their Tracks Tired of seeing your Rust server overrun by offline raid abuse? Offline Raid Limiter steps in to restore balance and fair play. With powerful tracking and immediate damage blocking, your players can enjoy a more authentic Rust experience—and you can enjoy worry-free server management. Key Benefits Prevent Offline Raid Abuse Daily + Per-Wipe raid limits Run daily limits, wipe limits, or both at the same time (fully configurable). Proximity-Based Tracking: Only counts raids when attackers are within range of a Tool Cupboard (TC), ensuring offline raid limits don’t trigger prematurely. Smart Raid Session Management Team & Additional Raider Tracking: Keeps tabs on individual players as well as entire teams—even if they leave and rejoin. Plus, if additional players jump into the same raid, their involvement is recorded. Edge Case Handling: No more confusion or gaps in coverage if a defender goes offline mid-raid or when multiple attackers are involved. Offline Raid Limiter’s robust logic sorts out these scenarios seamlessly. Instant Damage Blocking Enforce Fair Play: Once a team or individual hits their daily offline raid quota, further damage is blocked automatically. That means no more sneaky workarounds or unstoppable raids. Modded Server UI In-Game Control: For modded servers, gain access to a simple in-game UI that displays raid history, player statistics, and real-time session data. Player-Friendly Features: Grant permissions so your players can check their offline raid counts with the /orl.mystats command—helping everyone stay within the rules. Detailed Alerts & Reporting Discord Integration: Offline Raid Limiter sends comprehensive alerts to Discord, making admin oversight a breeze. Export & Clear Sessions: Use /orl.export to log and share your entire raid history for deeper analysis, then wipe all sessions with a simple console command if you need a fresh start. Designed for Vanilla & Modded Servers Flexible Configuration: If you set your server to "Vanilla,” the plugin automatically disables UI and direct damage blocks, limiting itself to Discord notifications so admins can monitor raiding behind the scenes. Seamless Integration: Works hand-in-hand with Rust’s existing frameworks and requires only the Simple Status & Image Library for certain UI elements. Why Choose Offline Raid Limiter? Enhanced Fairness: Players can’t take shortcuts with offline raids for easy loot. Clear Oversight: Admins see exactly who’s raiding and how often, helping you enforce balanced gameplay. Configurable & User-Friendly: Tailor the plugin to your server’s needs in just a few clicks, with plenty of documentation to guide you. If you’re ready to level the playing field and protect your community from unfair offline raids, Offline Raid Limiter has you covered. Bring your Rust server to new heights of balance, transparency, and peace of mind! Commands & Usage Player Commands (permission based) /orl.mystats — Shows your overall stats (daily + wipe, plus active limits). /orl.mydaily — Shows your daily offline raids and daily limit. /orl.mywipe — Shows your wipe offline raids and wipe limit. Admin Commands /orl.disable <hours> — Temporarily disables enforcement for X hours. /orl.enable — Re-enables immediately. /orl.clearall — Clears all stored raid sessions (and fully resets tracking). /orl.clearplayer <SteamID64 or name> — Clears raids for a specific player/team. /orl.export — Exports raid sessions to JSON via the debug webhook. /orl.dailyall [top] — Shows a “top raiders” list for daily scope. /orl.wipeall [top] — Shows a “top raiders” list for wipe scope. /orl.dailyplayer <name/id> — Check a player’s daily count. /orl.wipeplayer <name/id> — Check a player’s wipe count. Damage / Raid Logic OfflineRaidLimiter checks incoming damage to building blocks, doors, external walls, and more. If a team or player has exceeded the daily offline raid limit, all further damage to offline bases is blocked—and you can optionally broadcast an alert to Discord. Key Points to Note About Commands Some commands differ depending on your permissions and server setup. For instance, if a player types /exportraidsessions in chat, it won’t work unless they have OfflineRaidLimiter.admin. For "Vanilla” servers (as set in the config), UI, damage blocking, and certain other features may be disabled—so commands like clearraidsessions and clearraidsforplayer will still work, but may only be visible to server admins via console. When Commands Might Defer Cleanup Commands: If the plugin detects that some raid sessions are still "cooling down” (meaning the raid window hasn’t fully expired), the system may defer clearing them until the next pass. This prevents conflicts with currently active raids. Blocking Logic: After the daily limit is reached, the blocking triggers immediately and remains in place until the next server reset or cleanup routine (depending on how you configure it).
    $14.99
2.3m

Downloads

Total number of downloads.

10.5k

Customers

Total customers served.

151.9k

Files Sold

Total number of files sold.

3.2m

Payments Processed

Total payments processed.

Customers

Providers

Resources

About Us

Codefling is the largest marketplace to buy and sell plugins, maps, tools, and more! Our modern platform makes it easy to find exciting new content while providing a feature-rich environment for creators to monetize their work!

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.