Repository navigation
[Bug] data_file types are now case sensitive #653
Ehbw
started this conversation in
[BUG] FiveM for GTAV Enhanced
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
In Legacy, data_file's could be entered with any variation of casing (e.g. 'handling_file', 'HANDLING_FILE', 'hANDLING_fILE' etc). Now in Enhanced they are case sensitive which leads to several valid resources breaking as data_file's get skipped from being used.
Issue type
Client
Repro rate
Always
Server build version
b177
OS
Windows 11 25H2
CPU
AMD Ryzen 7 9700X
GPU
NVIDIA RTX 3060
RAM
64 GB
Storage type
SSD NVMe
Connection type
None
ISP and bandwidth
No response
DxDiag
No response
Network graph
No response
Platform
None
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
Unknown data file type carcols_file for resource <ResourceName>, skippingin console if the string is not fully uppercaseIn legacy this would have still be mounted.
Expected Behavior
The data_file should still work as it does in legacy in these scenarios.
Actual Behavior
The data_file gets skipped over and not mounted.
Evidence
No response
Additional Context
No response
All reactions