v1.39.1

Quieter, and the console reader stops gluing entries together. A run of the same error is one row instead of one a second: over three days of a real log, 885 error rows became 218, and the alerts did not change. The reader now asks the console how wide it is on every look, because reading a row of a buffer that has narrowed runs on into the row below it, which is what put two log entries on one line and a page of log into one Discord field. That field is capped at 240 characters now and says when it cut. A crash is one row: the exception under the line that reported it belongs to that line.

v1.39.0

Reads the words a client stops with. A script that gives up, a client that cannot log back in after a break, and a client stuck at the login screen are now alerts, and a stop reaches Discord whatever the script notifications are set to. One spell of not earning is one alert: a client that says it stopped in four lines, or retries the login screen a hundred times, no longer sends one for each. What re-arms it is evidence the bot worked, not the client's own claim that it is in the game. A Java crash is one row instead of four: the exception under the line that reported it belongs to that line.

v1.38.8

Every em dash is gone from the text the app shows: the help page, the settings notes, toasts, diagnostics, Discord messages and the alert titles. The only ones left are the dashes that stand for a value there is none of yet, in table cells.

v1.38.7

Console readers: the logs a run leaves behind are cleared when the app opens, so a client stops turning up twice after a restart and a name an early reader invented cannot come back. Only files a reader wrote, and only ones nothing is still writing. A row with no client behind it can now be dismissed from the session card. Fixes a reader deleting a log another reader was still writing, and a --report run clearing the logs it was describing.

v1.38.6

Session summary: an account with no client behind it and nothing finished to its name no longer gets a row. A single started task, which is all a briefly misnamed client leaves behind, used to be enough to keep one there for hours.

v1.38.5

Fixed

• Accounts that no longer exist stayed on the session card reading "Unknown" with nothing in any column. A row is kept when a client is behind it or when something was recorded against it, and a name with neither was never a bot.

v1.38.4

Fixed

• Clients attached to before anybody was playing on them were named after the client version, so four bots turned up called V12408-STABL. A character is only taken from a window title that names one, and it is looked for as the client logs in rather than once when the reader attaches.

v1.38.3

Fixed

• Errors carrying a Java stack trace filled the card with machinery. The exception is kept and the frames are counted instead: "... Index 0 out of bounds for length 0 [and 9 stack frames]". The raw line is untouched, so "show the log around this" still has all of it.
• Runtime was measured from the log file rather than the client. A client running for 44 minutes read as two if its reader had just started. It now uses the client's own start time.

v1.38.2

Fixed

• The switch for reading clients that write no log file was invisible. It was added with the wrong class names and rendered as a bare checkbox, so it could not be found and was never turned on. It is in Settings under Log source, below Poll interval.

v1.38.1

Fixed

• Clients whose window title carries a name this app had not heard of were invisible, so only some of them were watched. BotClient is recognised now, and so is any window your own client title pattern matches.
• Asking for a diagnostics report no longer starts a second console reader per client.