error

Hello. When I logged into my server, I noticed the status indicated that a purge was still active, even though it wasn't; I had to use a command to end the purge so the status would disappear. Then I came across this in the console. Can you help me?

Everything was running as it should before the updates; I don't understand it.

I tested this pretty extensively on the latest SimpleStatus build and I haven’t been able to reproduce the stuck purge status.

The console message you posted is expected and is only informing you that PurgeFX is using a Rust asset icon, so SimpleStatus falls back to Legacy CUI for that status. It is not an error.

I tested:

• adding/removing the purge status while online
• removing it while the player is offline
• timed status expiry while offline
• reconnecting after the status expired
• reloading SimpleStatus during the purge
• reloading the plugin controlling the purge during the purge
• restoring the status after reload and then clearing it while the player was offline

In all of those cases the status was removed correctly and did not reappear after reconnecting.

At this point I can’t reproduce an issue in SimpleStatus itself, so this may be related to how PurgeFX is restoring or clearing its purge state in your specific case.

The problem probably is not SimpleStatus itself, and may be related to how PurgeFX is restoring or clearing its purge state in your specific case.

Can you tell me exactly what happened before the status got stuck? For example, whether the server restarted, PurgeFX/SimpleStatus was reloaded, the purge ended automatically or by command, and which versions of PurgeFX and SimpleStatus you are using. If you have any console logs from around the time the purge ended, send those too

13 hours ago, dFxPhoeniX said:

I tested this pretty extensively on the latest SimpleStatus build and I haven’t been able to reproduce the stuck purge status.

The console message you posted is expected and is only informing you that PurgeFX is using a Rust asset icon, so SimpleStatus falls back to Legacy CUI for that status. It is not an error.

I tested:

• adding/removing the purge status while online
• removing it while the player is offline
• timed status expiry while offline
• reconnecting after the status expired
• reloading SimpleStatus during the purge
• reloading the plugin controlling the purge during the purge
• restoring the status after reload and then clearing it while the player was offline

In all of those cases the status was removed correctly and did not reappear after reconnecting.

At this point I can’t reproduce an issue in SimpleStatus itself, so this may be related to how PurgeFX is restoring or clearing its purge state in your specific case.

The problem probably is not SimpleStatus itself, and may be related to how PurgeFX is restoring or clearing its purge state in your specific case.

Can you tell me exactly what happened before the status got stuck? For example, whether the server restarted, PurgeFX/SimpleStatus was reloaded, the purge ended automatically or by command, and which versions of PurgeFX and SimpleStatus you are using. If you have any console logs from around the time the purge ended, send those too

Thanks for the detailed message.

I deliberately scheduled the restarts so they wouldn't happen during a Purge. My Purge was active when I logged off; it was set to end at 6:00 PM, and when I logged back in at 6:30 PM, the Purge had ended, but the status indicator was still there.

I have to ask: do you have "UseCustomVitals" set to on or off?

I turned it off after I noticed the issue—it used to be set to "true"—but unfortunately, I haven't tested it yet.

Yes, I have UseCustomVitals set to true.

However, for this particular PurgeFX status it should not make much difference, because PurgeFX is using assets/icons/warning.png. SimpleStatus detects that the asset icon is not supported by Custom Vitals and automatically switches the affected player to the Legacy CUI fallback.

All the tests I mentioned were actually done with UseCustomVitals = true and with that Legacy fallback active

I also tested almost the exact scenario you described: the purge status was active, I disconnected, the purge ended while I was offline, the external plugin called SetStatus(.s 0) while I was offline, and when I reconnected the status was gone. I also tested it across SimpleStatus and external-plugin reloads

So changing UseCustomVitals to false may change the renderer being used, but I don't think it is the root cause here

If it happens again, could you check the console (if the purge plugin have logs) around the exact time the purge ends? The most useful thing would be to know whether PurgeFX is actually clearing the SimpleStatus status when the purge ends while the player is offline. SimpleStatus handles that case correctly when it receives the removal call

Here’s a quick video. I specifically set the duration to one minute; the Purge starts automatically as usual and stops after a minute. While it’s active, I leave the server, wait for it to finish, and then rejoin—and lo and behold, the status is still there even though the Purge has ended.

I should add that I haven't changed anything; it was working the whole time, and then suddenly, out of nowhere, I have this problem.

That’s useful to know. Even if you didn’t change anything manually, it could still be a timing/state issue that only shows up when the purge ends while the player is offline.

From the video, the important part is that the status is being restored after you reconnect even though the purge has already ended.

I tested that exact SimpleStatus scenario separately: the purge-style status is active, the player disconnects, the event ends while the player is offline, the external plugin clears the status with SetStatus(s 0), and after reconnecting the status does not come back. I also tested this with the Legacy CUI fallback active and across plugin reloads.

So this still points more toward PurgeFX not clearing the saved SimpleStatus status for an offline player when the purge ends, or restoring/reapplying it from its own state when the player reconnects.

Since the UI is destroyed when the player disconnects, the bar you see after reconnecting is not simply an old UI element left on screen, the status is being restored from stored state.

If it happens again, please check the console around the exact moment the purge ends. That would help confirm whether PurgeFX is actually sending the status removal while you’re offline

If you want, you can add me on Discord and send me the plugin that’s causing the issue. I can check the SimpleStatus integration directly and see whether something changed there

Based on the tests I’ve done, I’m fairly confident the problem is coming from that plugin rather than SimpleStatus itself. I’m not sure what changed in the compatibility if you say it used to work before, but having the actual plugin would make it much easier to confirm exactly where the status is being left behind or restored incorrectl

The plugin is a paid product, so I don't think I can send it to you. Technically, it doesn't even belong to me—I only bought it for personal use—and I wouldn't want us to run into any trouble.

However, the support for Purge is pretty poor; it has actually been removed from sale because the developer unfortunately doesn't respond. I also think the issue lies with the Purge plugin.

and unfortunately, I don't have Discord.

I didn't find anything unusual in the console, except perhaps this.

24.9. 12:04:40 [Info] Command 'callcrash' not found

24.9. 12:12:49 [Info] ArgumentNullException: Value cannot be null.

It definitely has to be due to Purge, because the status disappears as soon as I reload the plugin. It definitely has to be due to Purge, because the status disappears as soon as I reload the plugin. But you can't get any help with it anymore; unfortunately, the plugin owner doesn't reply.

If PurgeFX is a paid plugin, then honestly this should be handled by its developer. I’ve already tested the SimpleStatus side extensively and the issue does not reproduce there

I’m not going to purchase paid plugins just to debug or potentially fix someone else’s compatibility issue. I’ve tried to help as much as I reasonably can from my side, but without the PurgeFX source or proper logs, the next step is with the PurgeFX developer

If the PurgeFX developer is no longer providing support, then unfortunately there isn’t much more I can do without access to the plugin code or useful debug information showing exactly what PurgeFX does when the purge ends

Changed Status from Pending to Can't Reproduce

2 minutes ago, dFxPhoeniX said:

If PurgeFX is a paid plugin, then honestly this should be handled by its developer. I’ve already tested the SimpleStatus side extensively and the issue does not reproduce there

I’m not going to purchase paid plugins just to debug or potentially fix someone else’s compatibility issue. I’ve tried to help as much as I reasonably can from my side, but without the PurgeFX source or proper logs, the next step is with the PurgeFX developer

If the PurgeFX developer is no longer providing support, then unfortunately there isn’t much more I can do without access to the plugin code or useful debug information showing what PurgeFX does when the purge ends

Okay, understood. Thank you very much for your time and effort. Have a nice day.