Fix negative playtime stat breaking /baltop

[JRoy]

Unclear how this happens, possibly a division error?

Fixes #6043

PR Overview

This PR addresses a bug where negative playtime statistics can break the /baltop command by ensuring that playtime values are non-negative before further processing.

• Clamps playtime seconds to zero using Math.max to avoid negative values.
• Adjusts the playtime threshold check from > to >= to include borderline cases.

Reviewed Changes

File	Description
Essentials/src/main/java/com/earth2me/essentials/commands/Commandbalancetop.java	Updates to prevent negative playtime values and adjust the minimum playtime check for /baltop

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (2)

Essentials/src/main/java/com/earth2me/essentials/commands/Commandbalancetop.java:131

• Ensure that clamping the playtime to 0 in case of negative values is fully compatible with downstream logic. Consider adding an inline comment explaining why negative playtime values are clamped to improve code clarity.

final long playTimeSecs = Math.max(playtime / 20, 0);

Essentials/src/main/java/com/earth2me/essentials/commands/Commandbalancetop.java:136

• [nitpick] Verify that changing the comparison operator from '>' to '>=' for the minimum playtime check is intentional, as it now includes users whose playtime exactly matches the minimum requirement.

playTimeSecs >= ess.getSettings().getBaltopMinPlaytime()) {