Jump to content

Code Brothers

Creator
  • Posts

    95
  • Joined

  • Last visited

Everything posted by Code Brothers

  1. Code Brothers

    Bad things happened!

    Haha, good to hear man, hope you enjoy it!
  2. Code Brothers

    Bad things happened!

    Dude, I am honestly stumped here, are you on oxide or carbon?
  3. Code Brothers

    Bad things happened!

    Try unloading all other plugins, and try just the excavator event.
  4. Code Brothers

    Bad things happened!

    I honestly do not know what could be wrong, all my plugins load fine, as far as my knowledge other buyers haven't encountered this problem. It also could be interacting with other plugins running on your server.
  5. Code Brothers

    Bad things happened!

    Changed Status from Pending to Work in Progress Changed Fixed In to 1.2.0
  6. Code Brothers

    Bad things happened!

    In game currently, everything seems to be working fine, make sure you're using it correctly.
  7. Unloaded plugin ArmedDeployment v4.1.1 by CodeBrothers Loaded plugin ArmedDeployment v4.1.1 by CodeBrothers now to get the cleanup working better.
  8. Code Brothers

    Bad things happened!

    try o.grant group admin excavatorevent.admin
  9. Code Brothers

    Bad things happened!

    I am confused, did it ever compile?
  10. Code Brothers

    Bad things happened!

    It's all lowercase, most likely why it never worked.
  11. Code Brothers

    Bad things happened!

    Alright, try downloading 1.2.0 again, I have added permissions, before it used admin check, also make sure you're on the newest version of oxide/carbon.
  12. Code Brothers

    Bad things happened!

    I guess I will have to add permissions then, it should just work if you're admin/owner on the server, we just were using the plugin today with no problems.
  13. Code Brothers

    Bad things happened!

    Pretty sure you need auth level two, but I will check once I am at my computer later.
  14. Code Brothers

    Bad things happened!

    Once the plugin is loaded, simply start excavator and fight!
  15. Code Brothers

    Bad things happened!

    Auto, but in addition there is the option to manually do so.
  16. Code Brothers

    Bad things happened!

    Good to hear, let me know what happens. Also you're able to configure the plugin through the /excavator command, it is a full admin panel.
  17. Code Brothers

    Bad things happened!

    Must be, we never had any structure damage upon loading the plugin. Also don't use excavator.spawn in console, just use the /excavator panel and the auto trigger via starting the excavator. (Just released a new version with the *.json file generation. )
  18. Code Brothers

    Bad things happened!

    Ah, I know exactly why the *.json file isn't being generated, and I will get this fixed immediately, but I am confused on what you mean by player structures being destroyed?
  19. Fixing, for now end the event before unloading, thank you.
  20. I will definitely look into these things, thank you!
  21. Version 1.5.1

    96 downloads

    Transform the Giant Excavator monument into a high-risk, high-reward dynamic hotspot, without replacing or disrupting vanilla gameplay. When the excavator is fueled or activated, resource-rich ore nodes spawn around the monument and hostile scientists roam the area to secure it. Players must push through NPC resistance while competing with others, naturally encouraging PvP, counter-play, and contested control of the site. Rather than turning Excavator into a scripted event, this plugin reacts directly to existing excavator usage, making the monument feel alive, volatile, and worth fighting over. Designed to feel fully integrated with Rust’s systems, Excavator Event automatically starts and stops with the excavator itself and cleans up when activity ends. Features • Automatic activation when the excavator starts • Enhances (does not replace) vanilla excavator behavior • Resource-rich ore node spawns (metal, sulfur, stone) • Hostile scientist NPCs with controlled roaming • Configurable spawn radius and density • Periodic node respawning while active • Clean despawn when the excavator shuts down • Modern in-game admin control panel • Server-wide event alerts and UI notifications • Performance-aware spawning logic • Fully configurable values Chat Commands (Admin Only) /excavator Opens the Excavator Event control panel Permissions excavatorevent.admin Required to start, stop, or configure the Excavator Event Configuration { "NodeCount": 30, "NPCCount": 50, "EventRadius": 80, "MinNodeDistance": 5, "NodeRespawnTime": 300, "NodeSpawnDelay": 0.15, "NodeRiseTime": 1.5, "NPCSpawnDelay": 0.2, "NPCRiseTime": 2 } Default values are tuned for balanced risk, server performance, and rewarding gameplay. Notes Excavator Event is built to enhance vanilla Rust, not override it. The monument functions exactly as expected — this plugin simply raises the tension, increases contesting, and makes excavator runs more meaningful. Ideal for PvP-focused servers, progression-based gameplay loops, and servers looking to make monuments feel more alive without immersion-breaking mechanics. Created by CodeBrothers Check out our other work on Codefling
    $19.99
  22. Changed Status from Pending to Fixed Changed Fixed In to 1.4.0
  23. Just put the correct version in.
  24. Also the choice of a banner or message will be in 1.4.0, along with discord webhook support, and loot table configuration, which I am working on now,
  25. Ah, I think I made a mistake with the version I put in for update, might have been a broken one. I just uploaded the exact version I just tested, try that and let me know!

About Us

Codefling is the largest marketplace for plugins, maps, tools, and more, making it easy for customers to discover new content and for creators to monetize their work.

Downloads
2.7m
Total downloads
Customers
11.5k
Customers served
Files Sold
163.8k
Total sales
Payments
3.5m
Processed total
×
×
  • 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.