Repository navigation
[Bug] Ensuring resource starts a different resource whose name shares a prefix #509
Closed
xXJamieXx
started this conversation in
[BUG] FiveM for GTAV Enhanced
Replies: 2 comments 1 reply
|
Hello, |
0 replies
|
Not the original reporter, but I can confirm the fix on b161-ea (Windows). Resources:
|
1 reply
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
When I run
ensure Vehiclefor example (either from the server console or in server.cfg), FiveM starts the resourceVehicle_publicinstead ofVehicle. I have two separate resources,VehicleandVehicle_public, and only the one with the extra suffix gets started, even though I explicitly named the other one.Issue type
Server
Repro rate
Always
Server build version
b139
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
Windows 11 Pro
CPU
AMD Ryzen 7 2700 Eight-Core Processor 3.20 GHz
RAM
32GB DDR4
Using txAdmin?
Yes
Hosting provider
Self-hosted
Machine type
Dedicated
/perf endpoint output
No response
DDoS protection
No
ulimit -n value (Linux only)
No response
Docker Compose file (Docker only)
No response
Steps to Reproduce
ensure Vehicleto server.cfg (or type it directly into the live console).Expected Behavior
Typing
ensure Vehiclein the server console, or havingensure Vehiclein server.cfg, should start/restart the resource named exactlyVehicle.Actual Behavior
The server instead starts/restarts
Vehicle_public.Vehicleitself does not start.Evidence
Additional Context
No response
All reactions