Solved Volcano Does Not Spawn Fireballs or Loot Crates

Return to plugin
Mala

Mala

Customer
After the wipe and update, the volcanoes no longer throw fireballs and their associated loot crates, and once the eruption is triggered according to the time in the config, they stay active with the lava field permanently expanded. I noticed this on wipe and then saw your update and thought it was fixed, but it looks like that was a fix for True PVE. I'll include a copy of the main volcano data config I am running.
 

Attachments

Recent First Highest Voted
That's happening because you're missing the crater settings. In your JSON, this line is missing:
JSON: 
"Crater": null,

You need to create one using the command:
volcano crater <position> <radius>

Check the Quick Start section on the plugin page for proper instructions
 
Last edited:
Upvote 0 Downvote
This was totally my bad on not seeing that. The volcano is working as before. I still have an issue where my crates vanish when the volcano is done, despite the config setting for 20 minutes. I am using Better Loot and that may be what has stopped this from working correctly, even though I have it set to use the custom loot table.
 
Upvote 0 Downvote
Mala said:
This was totally my bad on not seeing that. The volcano is working as before. I still have an issue where my crates vanish when the volcano is done, despite the config setting for 20 minutes. I am using Better Loot and that may be what has stopped this from working correctly, even though I have it set to use the custom loot table.
Click to expand...
Actually Better Loot has nothing to do with it. The thrown loot crates get cleaned up after the eruption finishes. But thinking about it again, yeah they probably shouldn't disappear so fast since players won't have time to loot them, I'll adjust that

Just a heads up though, after I make that change, try not to let too many crates pile up or sit too long, heli crates can impact performance if left around, so keep it within reason
 
Upvote 0 Downvote
You must log in or register to reply here.
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. Ensure 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

Cart

Total -