Being Worked On Automated Base Spawning

A plugin that will automatically spawn the selected copy/paste file in cfg.

Have options in cfg like:
is safe zone?
no decay - unlimited upkeep?
can building take damaged?
unlimited vendors? (if set to no, vendor stock will run out until next respawn)
if building is inactive how long to till next respawn?

and have it also announce the building spawn in chat (can be changed in lang file) for example: "A new town has spawned at (grid)"
 
So we're basically looking for a combination of Copy Paste and Zone Manager. For each base we paste, we create a zone around it, allowing us to set flags like NoDecay and SafeZone from the config

I'll try to work on this sometime this month (y)
 
I'm assuming this is something similar to Raidable Bases. I've had a desire to make a more natural feeling Raidable bases mod for some time now, but life just isn't giving me the free time for it. I'll try be very short in my thoughts:
  • Use Copy Paste plugin on a daily bases to randomly find bases that are flat (All foundations are at the same or similar level to avoid bases built around specifically weird terrain)
  • This will essentially give you an inventory of REAL player bases along with their progression that you can automatically spawn on the same day next wipe (or in a few wipes) so that the world feels more full.
  • Ideally you could add a sign to the base to signify it's a "Bot Base" so people know that they aren't wrecking someone's wipe on the more friendly servers out there. Could even be used in conjunction with offline raid protection to give people something to do at night rather than offline raid other players.

I've run servers using a DB of player created bases with raidable bases with offline raid protection on actual player bases to encourage a more casual server experience but unfortunately the loot ends up being crazy in those plugins and I'd love something that was a little more natural and copied ACTUAL player progression.
 
Back
Top
Chat commands start with a /, while console commands can be entered directly in the F1 console or server console. Use find <keyword> in console to search for available commands related to the plugin. Parameters in < > are required, while [ ] are optional.
This plugin uses Oxide's permission system. Grant or revoke permissions using oxide.grant and oxide.revoke. You can assign them to individual players or groups using their Steam id or group name.
Settings are stored in the config file found under the config/ directory. You can edit this file manually, then reload the plugin to apply your changes.
Persistent data is saved in the data/ directory. This includes things like saved settings, usage stats, or player progress depending on the plugin. Deleting a data file will reset stored progress or customizations.
Language files are located in the lang/ folder. To translate messages, copy the en.json file into your target language folder (e.g. fr, de) and edit the values. Reload the plugin after changes to apply new messages.
This section lists public methods exposed by the plugin for use in other plugins. You can call these via the CallHook method. Make sure the plugin is loaded before calling its API to avoid null reference errors.
These are custom hooks that other plugins can listen for. Simply define a method with the same name and expected parameters in your plugin to handle the event. Hooks are triggered at key moments and are useful for extending or reacting to plugin behavior.
These hooks are injected into the game's code using Harmony. They let the plugin run code at key points in the game's internal logic. You can return values to block or modify behavior. Use with caution — these are powerful and can affect core mechanics.
Cart