Open dmanbob opened 5 years ago
@dmanbob possibly a conflicting resource? Are you able to try with all other scripts disabled?
I will disable other resources and test and let you know.
@dmanbob any update?
sorry busy weekend I will try tonight and let you know. I'm sure like you say it's some mod.
updated to your latest release will test tonight
Still does it with latest version. Without ESX it works so probably something in the ESX Framework causing a conflict.
@Albo1125 A server I am a part of has had the same issue as #3. We restarted the server with only the fire script running, and it still only came up with the 'starting fire' print. No fire was started. Standby for graphics settings.
@dmanbob possible that the ESX framework intercepts the command somehow? I don't use it so wouldn't know unfortunately.
If no further reply will close.
was this ever fixed?
i am having the same problem the print pops up and says "fire started" but then theres no fire
I was able to start a fire no issues at all I made a small one flames 3 radius 3. The stopfire and stopallfires commands did not work. I tried to use the fire truck for 20 minutes still did not put out the fire. Restarted resource and server same issue. Looks Like others are posting same issue. I use ESX framework as well.