Update on a mysterious bug that happened with our server

[gdbaldude]

2 Months ago i opened up an issue about a weird warning pop-up that happened to some players on our server, We initially changed server version and that mitigated it for a while before it came back to handful of players after a few weeks.

This was originally closed, however thought id reopen it with a bit of extra info and a fix we have found.

Steps to reproduce the behavior:

1. Load in to server, and it occasionally happens.

Expected behavior
Load in to server with no warning.

Screenshots

• vMenu Version (check the about menu): 3.7.0 Release
• Do you have access to the files? Yes
• FXServer artifacts version: b17715

Additional context
Add any other context about the problem here.
Such as:

• We have no experimental features turned on, Base vMenu 3.7.0. We only have 1 add-on that enabled that would add chameleon colors as an option in vMenu. Nothing else that is supposed to mess with vMenu.

• Managed to locate the function that causes this warning in the first place, Storage.html. I have since deleted the bit of code responsible for displaying this message. It did not seem to be responsible for anything but displaying this warning pop-up.

• Still unsure why this popped up in the first place and only for our server, It seemed to have no consistent way to reproduce it, just happened randomly when logging in to a few players.

• There is also no way to click the check box to make it go away either, Once it is there it is there for the entire time.

[rco-titus]

Had this problem before, i thought for us it was with our phone resource, that got an update and no one saw that message again.

Also I think we were able to hit the box with F8 console

[gdbaldude]

Had this problem before, i thought for us it was with our phone resource, that got an update and no one saw that message again.

Also I think we were able to hit the box with F8 console

I also thought it was due to one of our resources, but we have too many that do different things unrelated to vMenu, This issue isn't reproducible consistently either, its not easy to single out the resource that would cause this. Clearing that bit of code did solve it for us though.