Join the Game4Freak Discord Get exclusive plugin sneak peeks, talk directly with VisEntities, never miss important updates, and unlock special discount codes!

Bug Unfortunately deletes player from server still

Return to plugin
hakonjj

hakonjj

Customer
Hi again and thank you for the recent update to version 1.5.0.
While this seemed in the beginning to work out very nice, there is still something that ended up completely removing a player from our server somehow (again).
I will try to break down in details how this happened (my players are testing this to the limit it appears);
  • Player noticed a raidable boat was closing in on ending (we have set max lifetime to 180 minutes)
  • Player went to start raid it and got a warning that it will despawn in 2 minutes (while onboard) – which essentually means that it didn't reset the countdown while raid was active (while player was looting it)
  • Player was still on the boat when the boat got removed and was stuck in the air with no possibility to communicate in chat or voice
  • Checked server logs where I see the error when trying to save that there was invalid items + the player.

Also attached a short video from the player himself (just redacted names) where he was stuck in the air unable to move nor communicate.
I haven't been able to be online right when it happened, so I'm reporting based on what he told me happened.
To also further give you more on our setup, I have attached our config as well (who knows - maybe I'm the one to blame?)

Hope to hear from you again.
 

Attachments

  • clideo_editor_b78bf2ac399c4630bec20871a035169c.mp4
    9.7 MB
  • RaidableBoats.json
    RaidableBoats.json
    48 KB · Views: 2
Last edited:
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 -