Releases: gimicze/firescript
FireScript v2.0.2
Changelog
- Bugfix (fixed desync/script jamming when respawning/reconnecting with active fires)
Full Changelog: v2.0.1...v2.0.2
FireScript v2.0.1
FireScript v2.0.0
Changelog
- The script now supports QB Core (for sending dispatch messages based on players' job)
- Changes to permission system to allow invoking commands from server scripts. (using ExecuteCommand native)
Full Changelog: v1.8.0...v2.0.0
config.lua
is NOT backwards compatible. Transfer your old fires.json
and whitelist.json
files, replace all other files in resource folder and adjust the new config accordingly.
FireScript v1.8.0
Changelog
- Some bug fixes and minor changes in code logic
- Added fire difficulty system (see config.lua, line 12)
- Added command
/setscenariodifficulty <scenarioId> <difficulty>
to set an exemption from the default difficulty setting - Added fire tone functionality (alarm which goes off at coordinates specified in config.lua, line 32 when fire spawns)
- Added additional sound to all fire nodes
config.lua
should be backwards compatible. If you want to use the new functions, add the config sections mentioned above.
FireScript v1.7.6
IMPORTANT NOTE: If you cannot run this version of the script due error in console regarding global ESX, try downloading the script as latest code, not here from the releases page.
Changelog
- Numerous bugfixes (mostly sync issues)
- Added support for custom dispatch messages1
1 See the wiki for more information.
FireScript v1.7.5
Changelog
- Fixed fires persisting for players outside the fire's render distance
FireScript v1.7.4
Changelog
- renamed commands (you can still use the old ones)
- added coordinates as optional parameters in /addflame and /registerscenario 1
1 See the wiki for more.
FireScript v1.7.3
Changelog
- bugfixes (fire spawner wouldn't reset upon putting out fires using /stopfire, ...)
- permissions update 1
1 added some aces support to provide better control over the script:
"firescript.start"
to allow the subject to start a fire;
"firescript.stop"
to allow the subject to put a fire out using a command;
"firescript.manage"
to allow the subject to manage the fires in general - that applies to: registering fires, adding them to the spawner, etc.
FireScript v1.7.2
Changelog
- yet another bugfixes
Sorry for the two consequent updates, you just never know when somebody discovers a bug :-)
FireScript v1.7.1
Changelog
- some bugfixes