Jump to content

FakeNinja

Creator
  • Posts

    85
  • Joined

  • Last visited

Everything posted by FakeNinja

  1. FakeNinja

    mute

    Hi @Darryl James, Remove the entire "Mute on 2 warning points" portion of the config file.
  2. FakeNinja

    Update issues

    Hi @Irishwould you mind sending me your config file, any error output (from console or logs in oxide/logs/SmartWarnings) and I'll take a look asap. Please do so via DM if it contains any sensitive information.
  3. Changed Status from Pending to Closed Changed Fixed In to 2.5.5
  4. If you upgrade from a previous version you will have to add this part to your config file. NOTE: If you add it to the bottom of the config file you need to remove the comma, or it will be invalid JSON. "Battlemetrics Settings": { "API Token": "", "Organization ID": "", "Server ID": "", "Banlist ID": "" }, Four values are needed as you can see. 1. API Token 1.1 - OAuth 2.0 Bearer tokens are used for authorization. You may create personal access tokens from the developers area. 1.2 - Click "New Token" and grant it Ban Lists, Bans, Player Flags, Player Notes permission scopes. 2. Organization Id 2.1 - Go to https://www.battlemetrics.com/rcon/orgs, click into the org 2.2 - Check the address bar in your browser, the address will be ending with the Organization Id, for example: https://www.battlemetrics.com/rcon/orgs/edit/123456 means 123456 is the Organization Id. 3. Server Id 3.1 - Go to https://www.battlemetrics.com/rcon, click into the server 3.2 - Check the address bar in your browser, the address will be ending with the Server Id, for example: https://www.battlemetrics.com/rcon/servers/123456 means 123456 is the Server Id. 3. Banlist Id 3.1 - Go to https://www.battlemetrics.com/rcon/ban-lists, click "View Bans" 3.2 - Check the address bar in your browser, the address will be ending with the Banlist Id, for example: https://www.battlemetrics.com/rcon/bans/?filter%5BbanList%5D=abcdef-123456-example-banlist-example91011 means abcdef-123456-example-banlist-example91011 is the Banlist Id. If you do not have any banlist, simply create an empty one.
  5. Version 1.1.1

    252 downloads

    SmartWarnings Lite simplifies and streamlines your server moderation by providing means to consistently Warn your players for misconduct. Gone are the times when you leave manual notes at sleeping players, for this plugin creates a smooth but intimidating chat warning displaying clearly to the player what they've done wrong and how to learn from it. Rule enforcement has never been easier before. If you enjoy the Free lite version of the plugin, please consider supporting the developer by upgrading to the Full version. In return you get many more useful features & fast developer support, it's a win-win. Link here: https://codefling.com/plugins/smart-warnings Commands /warn (player name or id) "reason" Dispatches a warning with a custom reason or presetRequires permission: smartwarnings.admin /warn info (player name or id, leave blank to see your own) Shows the amount of warnings, warning points and the individual warning details in chat.Requires permission: smartwarnings.admin to see other players. Default permission can only see their own warnings. /warn clear (player name or id) (id or ALL) Clear a specific warning ID by specifying the warning number, or specify ALL to clear all player warnings. Requires elevated permission: smartwarnings.admin.canclear Below command is only supported in the full version /warn clan (clan tag) "reason" Dispatches a warning with a custom reason or preset to an entire clan (Requires Clans plugin)Requires permission: smartwarnings.admin Configuration { "System Settings": { "Max Warnings": 5, "Default Warning Expiration time (Days)": 7, "Announce Warnings in Global Chat": true, "Show players who issued the warning": true, "Server Name": "MyRustServer", "Clear all Warnings on Server Wipe": true }, ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// ///// Below configuration is only supported in the full version @ https://codefling.com/plugins/smart-warnings ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// "Warning Presets": { "spam": { "Reason": "§1 - Spamming", "Points": 1, "ExpirationDays": 3.0 }, "toxic": { "Reason": "§2 - Toxic behaviour", "Points": 2, "ExpirationDays": 7.0 } }, "Autoban Settings": { "How many points until automatic ban (Set 0 for Disable)": 0, "How many warnings until automatic ban (Set 0 for Disable, Recommended: Same as Max Warnings)": 0, "How long to ban in minutes (Set 0 for Permanent)": 2880, "Clear the players Warnings on AutoBan (Default: True)": true }, "Discord Settings": { "Webhook URL - Post Warnings to Discord (Leave blank to Disable)": "", "Webhook URL - Post Autobans to Discord (Leave blank to Disable)": "" }, "AutoMod Settings": { "Mute on 2 warning points": { "PointTrigger": 2, "ExecuteCommand": "mute {0} {1}", "ClearPointsOnTrigger": false }, "Kick on 4 warning points": { "PointTrigger": 4, "ExecuteCommand": "kick {0} {1}", "ClearPointsOnTrigger": true } } } SmartWarnings Full vs Lite Below are the additional features provided by the full version of the plugin. Warn entire clans using /warn clan No need to dispatch a warning to every individual player if the whole clan has been misbehaving. The full version integrates with Clans. Create custom presets for common violations Presets can be made for example to reflect the server rules, it can be configured so that your admins can type /warn joe rule1 and it will spell out the entire rule 1 in the warning. Presets can have an Expiration date which will remove the warning, allowing non-repeating offenders to be cleared if they're well behaving in the long term. Presets can have a Warning Point weight which will give them different severity that can influence when to trigger an Automatic Ban (if enabled). Automatically Ban players with X amount of Warnings or Warning Points With this feature Enabled a player will be Automatically Banned when reaching the configured Warning amount or Warning Points. For example, configure 3 warnings to be max and enable auto ban will ban a player when the third warning has been dispatched. Supports Temporary Autobans If you're the kind of type that believes in second chances, when configured it bans the player lets them know when they're welcome back! Optional feature: Clear the player's warning when autobanned (True by default), This can conveniently be set to False if you want the player to be instantly auto banned next time a warning is dispatched. Extensive Logging both File based and Discord Configure Discord Webhook links to log Warnings and/or Autobans to Discord. Customizable Branding GUI-popup warning with Server Logo branding AUTOMOD: Fully customizable command actions on X warning points Define any custom command to be executed at X warning point. This allows you to integrate with any other plugin for example mute, jails or whatever really. For example: set to mute on 2 warning points, kick on 4 warning points, teleport to jail on 6 warning points.
    Free
  6. In case I haven't reached out to you before, this is now available in the new version /warn clear <player name or id> <id or ALL> Clear a specific warning ID by specifying the warning number, or specify ALL to clear all player warnings. (NEW in v2.5.0) Requires elevated permission: smartwarnings.admin.canclear
  7. Hi @GamingHQ, The renewal term is OPTIONAL, only required to receive new features of the plugin. You purchase it once and can use the version you purchased forever. The reason a small renewal term was added from v2.5.0 was due to the expanded feature set, much larger than the original scope of the plugin. It was being heavily requested by happy customers. The renewal term will ensure the continued development of the plugin. I intend to release any bug fixes of previous versions free of charge without requirement of renewal. I hope that clears up any misunderstanding. Your reasoning makes it seem like a subscription model which it clearly is not.
  8. Changed Status from Work in Progress to Can't Reproduce Changed Fixed In to 2.5.0-beta2
  9. Hi, Can you send me (in private message): the oxide/data/SmartWarnings_PlayerData.json and tell me the exact command you used. I will try to recreate it and patch it if there is an issue with the plugin. Thanks
  10. Changed Status from Pending to Work in Progress
  11. Hi, since v2.5.0 due to the expansion of features, a renewal term is applied for any feature updates. This is intended for new purchases though, not sure if that went through like it supposed to. I'll check for your case. EDIT: You should have access to all versions up until now (Do not expire).
  12. FakeNinja

    Failed to run a 3.00 timer

    Changed Status from Work in Progress to Closed Changed Fixed In from 2.4.2 to 2.5.0-beta2
  13. @tschetschpi1@unintelligible. Thanks once again for submitting logs. I've now uploaded the patched version and hope it should work without issue. Let me know how it goes.
  14. Thanks for reporting it. Could one (or both) of you DM me your /oxide/data/SmartWarnings_PlayerData.json file? I'll take a look asap and patch it thanks!
  15. This is now added in v.2.5.0! Thanks for the suggestion
  16. Hey, its working just fine. Do you have the required dependency DiscordMessages plugin set up correctly?
  17. Yes you can use the warn command from console but it may not reply back to console currently. Opacity control will be added to the next version, good input. I will research possibility to output in console for those actions.
  18. FakeNinja

    Failed to run a 3.00 timer

    Ok, thanks for confirming it still appears. So it only appears once if I understand? Does it appear only on start up? Trying to pin this bug down.
  19. This is great feedback and I'm planning to implement this permission feature in the next version. I can research the possibility to make a lightweight non-UI warning. Stay tuned
  20. FakeNinja

    Console usage

    Changed Status from Pending to Closed
  21. FakeNinja

    Console usage

    You can use the same commands from the console, however the plugin does not reply to the console in the current state.
  22. FakeNinja

    Failed to run a 3.00 timer

    Hi, thanks for sharing this info. It is recommended to wipe the warning data file for the new version. I will check these issues.
  23. FakeNinja

    Failed to run a 3.00 timer

    Changed Status from Pending to Work in Progress Changed Fixed In to 2.4.2
  24. FakeNinja

    Failed to run a 3.00 timer

    Hi, I've now released a new version that should resolve the above issue. Please try it and confirm
  25. FakeNinja

    Failed to run a 3.00 timer

    Hi, Thanks for reporting this I'm working on a fix!
1.6m

Downloads

Total number of downloads.

7.7k

Customers

Total customers served.

115.5k

Files Sold

Total number of files sold.

2.4m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.