[Release] Fire Script [OneSync]

FiveM Resource Development & Modding Releases
, ,
163

Hi,

Please let me know about the result! Everything runs fine on my machine. Which version did you update from? There were a few patches which required a new config.

What do you mean by this? 10 actual fires (spawner in-game) or 10 scenarios? There is a hardware limitation set by the game which causes particles to disappear or appear improperly when around too many particle sources (flames). If the “scenarios” (as I call them in the docs) are what you mean (and you’re unable to create more than 10 scenarios), I’ll need to have a look at it.

This is intentional, as the tools contained with the /firedispatch command were intended to only be used by administrators. I didn’t think of this problem when implementing custom dispatch messages… As of now you can overcome this issue by allowing command.firedispatch permission to the desired player(s).

164

Apologies for not being more descriptive, it seems to be 10 individual fires. When spawning a second fire either by scenario or second start fire command it equals out the total number of fires to 10. This does not appear to affect the “spread” numbers so anything over 10 will cause the standard effect of “respawning” fires that have gone out.

The script was updated from 1.4.5 to 1.4.7 (correction; 1.7.4 to 1.7.6) without a config change but everything else was altered so this could be the cause for the lack of random fires.

I’ll update this post when I do the reinstall to see if that corrects the issue, but as of now I’m highly confident it’s going to be an issue with the config.

Edit - Had to fix those version numbers, not sure where the heck I obtained the originals. A full wipe of the script and then server cache in that order prior to a fresh 1.7.6 being put onto the server with the original fires.json seems to have been the fix.

Oh interesting, as of right now we’re using the dispatch ace perm for all of our main FD as I haven’t gone about making something for them to add and remove themselves from dispatch freely just in case they wish to do other non-fire related things without adding ESX onto the server.

165

But where do I put that line? (I don’t know how to use ace perms stuff)

166

Howdy. Great resource. One question, random fire spawner doesn’t exactly spawn fires randomly. It’ll spawn fire #1, then after the prescribed time it’ll spawn fire #2 and so on. Is there a way that it will randomly pick one of my 50 saved scenarios?

167

I put it in my sever.cfg

168

Hey! That definitely shouldn’t happen. I’ll do some testing tomorrow and will get back to you with further information.

2 Likes
169

Thanks GIMIcz, user error. Fantastic script, highly recommend!

1 Like
170

Hey Gimi! How can i see the scenario ID?

171

Hi! Unfortunately, as of now the ID gets displayed only upon creating the scenario. I will add a few commands which will help with finding it in the future - don’t have the time for that nowadays though.

There are going to be ways to obtain all existing scenario IDs, to teleport to scenarios and possibly see the spawn points through 3D text of some sort. Stay tuned, I may have a look at it in the following weeks :slight_smile:

172

How am I bypassing the whitelist it would be great for an explanation cause I put the ace permission into my server.cfg and it didn’t do shit.

173

Hello,

Im not being able to find Fires.json or whitelist.json, im trying everything but got no luck.

Any ideas? Thanks a lot in advance.

174

Hi, heres an Auto Reply for everyone!, i had to restart my TxtAdmin server.

I mean all my machine not just from TxtAdmin and now its working!.

Heads up!

1 Like
175

where do I put the firescript.all at?

176

Hey are there some special things that i need to take care for if i like to add a firestart on a vehicle explotion or are such functions supportet by defalt by teh script?

177

Not yet, unfortunately. Taking into account the lack of time I have at the moment, I cannot tell you whether or when I would have a look at this specific functionality.

178

Excellent script, fun. I was able to register a new fire, add it to random fires, used addflame to set its properties. It’s spawning perfectly, randomly, spreads, and a firetruck works great to put it out. I can and want to repeat that multiple times to add a bunch more new fires.

The real problem for us is that these commands are required on every join, it’s difficult for my users to grasp:

/randomfires add 1
/randomfires add 2
/randomfires add 3
/randomfires add …
/randomfires enable
/firedispatch add (player id) FIRE

I can take care of registering new fires, but this script takes multiple commands and an ID lookup on each session to get started. If I add more fires, a new command will be needed to add each new fire to random, on each session join.

I’m looking for a way to add all random fires from fires.json on startup, start the random fires right away, and add all players to the dispatch, all on script start. A lot to ask I know, I’m looking into workarounds.

Thanks, very cool.

179

In server/main the checks can be removed for permissions on each command, comment out lines similar to this, a bit risky to open this up I suppose:

	--if not Whitelist:isWhitelisted(source, "firescript.(command)") then
		--sendMessage(source, "Insufficient permissions.")
		--return
	--end
180

Hello and thank you for the kind words! :pray:

The script definitely shouldn’t behave this way. I will have a look at what might be the problem later in the afternoon. Sit tight, will get back to you :slightly_smiling_face:

Edit: Meanwhile, could you please provide your current fires.json file in a PM? Also, please have a look in the console for any errors… Thanks!

1 Like
181

Super sick script, really god job man

1 Like
182

Anyone able to help me set this up for permissions, id like to remove the whitelist so anyone can start a fire