Current Project: HUD7

Issue ID# 182 Implement an alternative routine to determine the RLV-status if possible.
Status: Completed Version: 7.1.7 Priority: 3
Assigned to: Lulu Submitted by: Miriam Himanez Attached file:
Type: Bug Submitted:
04/03/2016 10:32:49 PST
Last Update:
30/06/2016 22:17:52 PDT
Description: Technically this is about a bug. I don't submit this as bug-report, because I've already found a good description:

Please view the closed issue #131 "RLV not recognized by uHUD" posted by Vanny Richez 4 months ago.

I'm not able to add much to it. I have a screenshot of the popup, Owner receives and the chat-message coming up 3 times always for sub. (Please view attached file.) Additionally I found out, that restarting the uHUD is useless but after relogging everything is ok again. Like Vanny, I'm absolutely not able to reproduce this issue; I just recognized a tendency: The longer I didn't relog, the more teleports I did within this timespan and the more lag I had around me, the higher the chance for this bug to be triggered. Sometimes 1 hour was enough, sometimes everything was still fine after more than 3 hours without a relog.
This bug doesn't come with the general tendency of sl losing information on RLV-restrictions and -locks when having been online for too long and having done too much without relogging in between; it appears significantly earlier sometimes.
Because this issue being so difficult to catch, I'm thinking of a workaround. Somehow the routine determining the RLV-status tends to loose the proper information after a while. A solution could be to implement a different routine and/or saving a backup of the RLV-status at login, which could be re-read later - just in theory of course. I'm no scripter and haven't got a clue, wether something like this could be done without exceeding a realistic amount of work.