FakeNinja

Changed Fixed In to 2.5.8-beta3

Hi @Ghosty, Thanks for reporting this. I was approached earlier about this issue and have now already released a fix in 2.5.8-beta3. You can find it on the plugin page. Please do let me know if you run into any issues or if that also completely solves it for you.

Changed Fixed In from 2.5.8-beta2 to Next Version

Changed Status from Pending to Work in Progress Changed Fixed In to 2.5.8-beta2

Changed Status from Pending to Work in Progress

@TinjaI sent a DM req to you on Discord so we can have a look together.

Changed Fixed In to 2.5.8-beta2

Changed Status from Can't Reproduce to Closed Changed Fixed In from 2.5.8-beta to 2.5.8-beta2

Thanks, I think I found the issue, try this one (2.5.8-beta2) version

Can you send me a copy of your config file?

Check your config file, you need to put the webhook URL scroll down a bit to this part: "Discord Settings": { "Webhook URL - Post Warnings to Discord (Leave blank to Disable)": "Put your webhook url here", "Webhook URL - Post Autobans to Discord (Leave blank to Disable)": "Put your webhook url here" },

Hi @Tinja, What Discord plugin are you using? SW supports DiscordMessages and DiscordAPI? Do you get any error in the server console?

Hi, this should be resolved in the latest version. Let me know if you encounter any issues

Changed Status from Pending to Can't Reproduce

Changed Status from Work in Progress to Pending

Changed Status from Pending to Can't Reproduce Changed Fixed In to 2.5.8-beta

Hi @Natz, Which version did you upgrade from? It can be caused due too old config file. Please try wiping your config file & data file and reload the plugin. If you compare the new and old config file (see plugin page) you can also paste in the new parts to save some time.

.

Changed Status from Pending to Work in Progress

Thanks for that, I'll see if I can reproduce it. So just to get everything straight, this appeared after enabling the Battlemetrics API? Will you please verify these things: API token scope, what permissions does your API have currently? (See plugin page for info which to set) What player did you try to warn, does this player exist in BM (identity + steamid exists within your Server + Org in BM)? The reason for the latter question is that the integration is dependent on the BM identity to be associated with the steam id. The plugin will do a lookup based on the steam id to make sure it is the correct player. The error can occur if the player has never been recorded by BM, or for some reason, the player is not indexed in the org yet. I'll reach out to you in Discord DM to make communication easier for us, if you prefer that

Changed Status from Pending to Closed

It can happen if you run other plugins that override the default mute command. Try unloading all plugins (o.unload *) and unmute "steamid" then load them back again and execute the same command. The SmartWarnings plugin does not perform any logic inside of it to mute, it is simply executing the command, so this is not caused by the plugin.

Hi @Irish, there's no issues with your config. I take it that you didn't send any error logs (from console or log files) because you did not have any errors, or? If there's any error caused by the plugin there should be output.