Remineration (Legacy Thread)

I am going to be honest. I have AdminRadar on.. and i had somebody mine a Node in the middle of an open field... and i have it set to 1-5 meters.. at a 100% chance to spawn.. and absolutely nothing spawned... about 10 times i tested this. I must be doing something wrong.
 
I am going to be honest. I have AdminRadar on.. and i had somebody mine a Node in the middle of an open field... and i have it set to 1-5 meters.. at a 100% chance to spawn.. and absolutely nothing spawned... about 10 times i tested this. I must be doing something wrong.
They don't spawn instantly, there's a delay which can be configured in the config. If nothing spawns still, it likely means a valid spot couldn't be found within the Check Radius For Nearby Entities range
 
I tested it again and ores spawned as intended. For ores to spawn, the following conditions must be met:
  • The spawn location must not be on roads or rails
  • It must not be in water
  • It must be on solid ground
  • It must not be near any players or entities (controlled via the Check Radius For Nearby Entities config option)
 
Is there a place i can show you. Or send logs so you can help me find out if there's something interfering with it? Because everything that would interfere with it would also be interfering with Reforestation. Which works like a charm! But yet this Remineration isn't working.
 
Is there a place i can show you. Or send logs so you can help me find out if there's something interfering with it? Because everything that would interfere with it would also be interfering with Reforestation. Which works like a charm! But yet this Remineration isn't working.
Send me a message on Discord
 
Back
Top
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.
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.
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