Report #3660
Excessive battery drain after idling in estate-level script disabled region
| source | toothless.draegonne |
|---|---|
| version | 0.5.5 |
| status | NEW |
| priority | TRI |
| target fix | |
| report date | 2025-08-28 16:29:33 |
| report | When you are in an estate-llevel script-disabled region, obviously ARES will be in a paused state. The issue is that this includes whatever your current drain is (for instance, the high value of a previous teleport). Thus, after a time spent idling in such a region, a subsequent teleport to a region with scripts enabled will cause ARES to do what appears to be a simple usage*time calculation, which can cause you to lose a significant amount, or all of your available battery level immediately. To test this, you can try teleporting to a script-enabled region and then, while power drain has not yet settled, teleport to Linden Estate Services 2 or another estate-scripts-disabled region. Spend some time idle there, then teleport back to a scripted region such as Eisa. As a workaround, I would suggest including a time value to store when the last drain-tick happened. If it is greater than some sensible value (maybe 30 or 60 seconds), we can assume that all is not right with the world, and it may be a good idea to not apply the next power drain calculation. |