[Bug/Regression] Change of behaviour with GetResourceState

[ChatDisabled]

Summary

GetResourceState used to return "stopped" when a resource failed loading or never got loaded in the first place. On FiveM for enhanced however it now returns "loaded" even though this is not a valid option (according to the yet to be updated documentation). If it fails loading however it returns "uninitialized". This regression is especially apparent when trying to control your resources through txAdmin since it still expects the previous values.

Issue type

Server

Repro rate

Always

Server build version

FXServer-early-access b90 win32

OS

No response

CPU

No response

GPU

No response

RAM

No response

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

Windows

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

None

Hosting provider

None

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Have a valid resource with a proper manifest but never start it through a cfg
2. Use GetResourceState or check inside of txAdmin with that resource name
3. Get "loaded" as a result

---

1. Have a valid resource but with a dependency in the manifest that doesn't exist
2. Use GetResourceState or check inside of txAdmin with that resource name
3. Get "uninitialized" as a result

Expected Behavior

Return "stopped" since the resource never got loaded and to match behavior with legacy

Actual Behavior

Returns "loaded" if outright not starting it or "uninitialized" if it fails to load

Evidence

No response

Additional Context

No response

[tabarra]

Thanks for the report. Issue confirmed, will fix it asap.

[tabarra]

To be included in next hotfix: citizenfx/txAdmin@1076eb2