Skip to content

Releases: Bot-detector/bot-detector

v1.3.9.5

26 Jun 00:04
0b33949
Compare
Choose a tag to compare

In this release of the bot detector plugin, we’ve incorporated a warning message to promote respectful interactions within our community:

  • We’ve introduced a warning message to the plugin interface, visible by default to anyone using/installing the plugin after the update, below the player statistics panel.
  • This warning can be removed through the plugin's settings after reading through an acknowledgement message.
  • The warning underscores that any form of harassment towards other players based on predictions is strictly forbidden.

We've added the warning as a response to reports of legitimate players being targeted due to plugin predictions. It’s important to remember that our machine learning models are not perfect, particularly for accounts with unique builds or those that deviate from the norm. Let’s maintain a respectful attitude towards each other and steer clear of unnecessary conflicts. After all, harassing a bot doesn’t really accomplish anything.

We appreciate your understanding and cooperation! Let’s work together to keep the game fun for everyone.

Best regards,
The Bot Detector Team

v1.3.9.4

29 Jan 00:54
6867120
Compare
Choose a tag to compare
  • Separated the option for showing the right-click predict menu item into two, one for game-world players and the other for interfaces.
  • Twitter button rebranded to X.
  • FlatLaf related fix for buttons on the panel not being correctly highlighted in red/green/yellow.

v1.3.9.3

13 Jan 17:38
b526aba
Compare
Choose a tag to compare

v1.3.9.2

18 Apr 17:04
db306de
Compare
Choose a tag to compare
  • Changed a deprecated variable from Runelite's API.
  • Reverted the fix in v1.3.9.1 related to manual detections as the Bot Detector API was updated to accept the flag from the serialized data directly instead of being required through a query parameter.
  • Changed the Bot Detector API URL to point to the new subdomain (api.prd.osrsbotdetector.com).

v1.3.9.1

22 Dec 05:03
9eb6ff4
Compare
Choose a tag to compare
  • Fix for broken Manual Detect functionality: API call was missing a parameter indicating the upload was manual, so the API treated it as an automatic upload.

v1.3.9

09 Nov 16:11
5ffabc7
Compare
Choose a tag to compare
  • Patreon link updated on the README as well.
  • Slight behind the scene changes with error logging when communicating with the Bot Detector API.
  • Added hover tooltips to the Feedback and Flagging panel headers after an error occurred.
  • Added a new sister feature to the Predict coloring settings. Users may now apply the coloring to the in-game Report option as well.
    • Useful for those who hide the Predict option and make use of Predict on right-click Report instead.
    • However, may cause unforeseen issues with other plugins if they rely on the Report option's text being unchanged. This is due to the way the color is applied, which is by adding a color tag in front of the option's text. An appropriate warning should display when trying to enable this option.

v1.3.8.4

21 Oct 21:14
b932f0b
Compare
Choose a tag to compare

v1.3.8.3

19 Oct 18:51
65a1295
Compare
Choose a tag to compare
  • Fixed Stats Too Low not letting you specify a bot type in the Feedback box when the option to show the Prediction Breakdown in such cases is disabled.

v1.3.8.2

09 Sep 17:18
b5d794d
Compare
Choose a tag to compare
  • Internal changes to how resources are used by the plugin to completely eliminate potential conflict issues with other plugins.

v1.3.8.1

29 Aug 16:13
516e9fb
Compare
Choose a tag to compare
  • Added a new setting and handling for the API returning null primary confidence (e.g. Stats Too Low). Set the appropriate plugin config option to see the breakdown for these predictions. Disabled by default.
  • Added some extra handling to attempt to log and prevent issues with player sightings being saved with instanced coordinates after somehow bypassing instance checks. No guarantee this actually fixes the root cause however.
  • Some formatting on the README file to make IntelliJ happy.
  • Changed generated version.txt file name to prevent collision with other plugins.