CrypticRedHat

Hello, As I have not had a reply, I will assume this was resolved by reloading. If you have any issues or want to come back to this please reply or open a new support case.

Update released that adds a flag to exclude them in config

Changed Fixed In to 1.5.20

Hello, Have you tried the above please?

Changed Status from Not a Bug to Feature Request

Thanks, odd, again it's struggling to talk with the simple status based on the error. I am happy to troubleshoot with you on your server if you want to hit me up on discord. Same name as here. else, I will need you to tell me if you are running Oxide or carbon. Then print the list of plugins and send them over Finally, do you have any other plugins that use Simplestatus? For Oxide: Oxide.plugins For Carbon: c.plugins Please also try and unload/load in this order: Unload: OfflineRaidLimiter Simple Status img library Potentially restart the server to clear caching here. Load: Img library Simple status OfflineRaid Limiter

Hiya, thanks for the report, please can you share the versions of both Simple Status & img library and a copy of your config redacting any discord hooks. The error is it using the simple status webhook, so it looks like it may be with an issue with the loaded simple status. Please share the above and I will assist.

Great thanks, I will add a flag in the config to IgnoreBasesWithNoVictim, this should stop it from blocking raids on raidable bases if set to true. I will post an update over the next few days

Can you possibly enable the raid blocked discord messages for me please, test it and send me a copy of who its defining the defenders are on one of the raidable bases?

Changed Status from Pending to Not a Bug

I will look into adding support to exclude these via a config setting on the next minor version

As in bases generated by the radiable bases plugin?

Changed Status from Pending to Fixed

I have been running it for a couple days now and no longer see this error, I have not had any feedback to say it is still an issue so will close this for now. If you notice any issues please open a new support log.

Changed Status from Work in Progress to Pending

Changed Status from Pending to Work in Progress Changed Fixed In to 1.5.19

Hi, sorry for the delay, please try v1.5.19 - this should resolve that issue, if it does not, please let me know.

I will run some testing with these plugins tomorrow

What other plugins do you have that use this hook please? Any other any other plugins that limit damage? I have used and tested this extensively and other people who have purchased have not reported this lag issue, so I am wondering if its interfering with another plugin? Can you also attach a copy of your config, and redact any discord info first please.

I haven't forgotten this, I am running this on some larger servers and still trying to replicate. Can you confirm when this exception was thrown, did it only lag the player or the whole server? Have you seen the issue since?

I have tried to replicate with fire damage, Moly, fire ammo etc but cannot reproduce, did this happen with a single player? or the whole server? Did they give you anymore info?

Thanks, I will look into this, I would assume its due to the high volume of calls made when fire damage is used. Although a couple things to note This shouldn't be an issue as it rate limits itself The errors isn't actually within the plugin itself, the error quoted above was actually just before calling the plugin, where it failed to call the hook itself. I will try and replicate this, and get back to you asap with the cause and a fix. Although this may take me some short time to try to replicate. I have it running on 10 servers myself, and have not seen this yet but will try today/tomorrow to replicate it.

Assume this was a bit of a one off, I would say it was trying to get the entity of something that was destroyed but delayed to failed. Can you confirm this is not consistent for me please? I doubt this would be common, however I will implement catch to throw out a this exception if it occurs in a hot fix for you within the next 24/48 hrs Thanks for the report.

Changed Status from Pending to Not a Bug

No problem glad you like it