Skip to main content

Changelog

This page documents the changes made to FAR.

v1.4.*​

v1.4.4 - 03/22/2025​

Changed:

  • Minor refactor to FAR Tool's demo prop creation logic.

Fixed:

  • Typo in internal event handling Alarm System updating between client and server.
    • The typo existed both in the event handler and the trigger, so it still functions in prior versions.
  • Hidden Metadata not being removed from memory after FAR Tool was closed.
  • Preview prop in FAR Tool appearing above the player's head momentarily when first spawned.
  • Draft Alarm System data being stored in server memory when it didn't need to be.
  • Issue with the Detector Testing where a server error would be thrown.
  • Typo in an uncommon error relating to draft alarm systems not being loaded properly.
  • An empty error message appearing in the server console when a Draft Alarm system with a syntax error was loaded.
    • Now the error indicates the syntax error is from a "draft alarm system", instead of an empty error message.

v1.4.3 - 02/24/2025​

Added:

  • Detector Tester Spray Can, see here for details.
  • disableInteractions client export, see here for details.
    • The editable/client/targeting.lua file has been updated to include canInteract entries for both OxTarget and QBTarget, if you use these resources you might want to update this file.
    • If you use your own targeting/third-eye resource, consider making use of the canInteract() export, see the examples inside the editable/client/targeting.lua file.

Changed:

  • Some interactions now take priority over others.
    • Interacting with a Control Panel or Pull Station will take priority over Spraying the Detector Spray Can, for example.

v1.4.2 - 01/20/2025​

Added:

  • Ability to shoot Sprinklers
    • When shot, a Sprinkler will show water.
    • If the Alarm System is not yet in Alarm, it will go into Alarm.

Changed:

  • HTTP API request logs such that they only log when Debug Mode is enabled.

v1.4.1 - 01/16/2025​

Fixed:

  • Issue where if two or more Alarm Systems were within 100 units of each other, and one or more Alarm Systems had its props spawned (entering spawn radius), despawned (leaving spawn radius), and then spawned again (reentering spawn radius), the Alarm System's props would not respawn and instead "No Interactable Prop" errors would appear.

v1.4.0 - 01/13/2025​

Added:

Changed:

  • Optimized syncing of Alarm Systems between Server and Clients.

Fixed:

  • Some console log messages being malformed.
  • Sonoran CAD export in Server Editables missing Alarm System name.

v1.3.*​

v1.3.9 - 01/06/2025​

Added:

Fixed:

  • Error relating to base-game explosions.
  • Typo in config.cfg for ic_far_defaultSprinklerValveModel
    • Existing server owners/developers should search for sert and replace with setr.

v1.3.8 - 01/02/2025​

danger

Major breaking changes to editables and OxTarget were made in this version, do not blindly update.
Reach out in Discord if you need help updating.
Always make a back-up before updating!

Added:

  • Support for multiple target/third-eye resources, see below.

Changed:

  • Multiple Detectors can now activate for a single fire/smoke event, instead of just the closest.
  • Moved all targeting logic into a new client editables folder
    • Allows support for OxTarget & QBTarget out-of-the-box.
    • Owners/developers who previously used ic_far_oxTargetSupport will need to enable ic_far_manualInteractions and edit their editable/client/targeting.lua to re-enable support.
      • Reach out in Discord if you need help with this.
  • Moved server editable files from editables/ to editables/server/.
    • Existing users will need to manually move their existing editables files to the new directory.
      • Reach out in Discord if you need help with this.

Fixed:

  • OxTarget zones being removed twice, resulting in a harmless error.
  • SmartFires' smoke would not activate detectors.
  • Unhandled error and getting stuck in an animation when trying to access a Control Panel another player is using, instead of displaying the friendly pop-up.
  • Custom props not being used in the FAR Tool.
    • note

      This fix makes several small changes to the config.cfg file, existing users may need to update this themselves.
      To apply the change, replace set with setr for the following entries:

      • ic_far_defaultControlPanelModels

      • ic_far_defaultPullStationModels

      • ic_far_defaultDetectorModels

      • ic_far_defaultSprinklerModels

      • ic_far_defaultSounderModel

      • ic_far_defaultStrobeModel

      • ic_far_defaultSprinklerValveModel

      danger

      Do not replace all instances of set inside config.cfg, only change the entries listed above, otherwise secret values such as the HTTP Access Token can be exposed.

v1.3.7 - 12/23/2024​

Added:

Fixed:

  • Being unable to open/close Sprinkler Valves properly with OxTarget.
  • Detectors not fully resetting when an Alarm System is reset.

v1.3.6 - 12/16/2024​

Added:

Changed:

  • Increased maximum prop spawning distance from 75 meters to 100 meters, and maximum FAR Tool prop placement from 35 meters to 75 meters.
    • The aim of this change is to allow for physically larger Alarm Systems to be created.
  • Editable events such that they cannot be triggered from the client.

Removed:

  • Logic that checked if an interior had loaded before spawning FAR Props.
    • Caused issues with add-on MLOs located in the same position as base-game MLOs.

Fixed:

  • Announcements not working correctly from the Control Panel.
  • Passcode error pop-up when creating a new Alarm Location with the FAR Tool.
  • Erroneous file name being shown when saving an existing draft with the FAR Tool.
  • Being able to load empty .lua files as valid drafts for FAR Tool.

v1.3.5 - 12/09/2024​

Added:

  • Alarm System Monitoring
    • Adds a monitoring parameter to the AlarmSystem object.
    • Designed to represent if an Alarm System is being monitored by an Alarm Monitoring Company, such as Gruppe Sechs.
    • Can be used when handling activation events to determine if the alarm activation should result in an automatic page/call/etc. to Emergency Services, for example: 
      • RegisterServerEvent("Inferno-Collection:Server:FireAlarmReborn:Editable:AlarmActivation")
            AddEventHandler("Inferno-Collection:Server:FireAlarmReborn:Editable:AlarmActivation", function(alarmSystem)
          	
            -- Monitoring is not enabled, so we will not page the Fire Dept.
            if not alarmSystem.monitoring then
                return
            end
          	
            Pager:NewPage("Fire Alarm - " .. alarmSystem.name .. " - " .. alarmSystem.location)
        end)
    • Value is true by default, and can be changed in one of two ways:
      1. In-game, by using the Control Panel and locating the Disable Monitoring option in the Main Menu.
      2. Out-of-game, by adding monitoringDisabled = "true" to Alarm System entries.
    • MonitoringDisabled event.

Changed:

  • Logic that checked if interiors were full loaded before spawning FAR props.
    • Previously, if an interior was reporting as "not ready", FAR would not spawn props at all.
    • Now, FAR will load props after 15 seconds regardless.
      • This resolves an issue with FAR props not loading at locations where addon MLOs intersected with base-game MLOs.
  • Multiple players can now use the FAR Tool at the same time.

Fixed:

  • "Press E to ..." prompts appearing even when ic_far_oxTargetSupport was set to true.
  • OxTarget Sprinkler Valve interactions duplicating.
  • Random Alarms being triggered even when there were no players in server.
  • Bug that prevented the loading of draft Alarm Systems that shared locations with a live Alarm Systems already loaded.

Removed:

  • Per-Control Panel passcodes.
    • Passcodes are now per-Alarm System.
    • Existing Alarm Systems can be updated by moving passcode = "..." from the Control Panel entry into the Alarm System entry.
      • Reach out in Discord if you need help converting old systems.

v1.3.4 - 12/04/2024​

Fixed:

  • Hidden Props reappearing momentarily ('flickering') when an Alarm System changed status, such as from standby into alarm.

v1.3.3 - 12/01/2024​

danger

Breaking changes to the Exports were made in this version, do not blindly update.

Added:

Changed:

  • Multiple Sprinklers can now activate for the same fire.
    • Previously, only the closest Sprinkler within X distance of a fire would activate, now all Sprinklers with X distance will activate.
    • The distance ('X') from the fire to the Sprinkler has been reduced slightly to avoid "too many" Sprinklers activating.
  • Pre-activated Sprinklers now extinguish new fires.
    • note

      This only applies to z_Fires and SmartFires.

    • Previously, once a Sprinkler was activated, any new fires in the same location while the Sprinkler was still active would not be extinguished; this is no longer the case.
  • triggerPullStationAtPosition export now activates the closet Pull Station to the provided position, not a random Pull Station.

Fixed:

  • Issue where randomly generated z_Fires smoke was causing server errors and Sprinklers not to activate.

v1.3.2 - 11/27/2024​

Fixed:

  • All fires created by z_Fires were put out after a few seconds, regardless of Sprinklers.
  • AlarmActivation event being fired multiple times.
  • Typo in ic_far_defaultSprinklerValveDistanceCheck config option.
  • ALARM and BUZZER Control Panel LEDs still blinking after being muted.

v1.3.1 - 11/25/2024​

Fixed:

  • Resets being soft locked if first reset attempt failed.
  • FIRE LED state not updating until FIRES button was pressed.
  • Sprinklers reactivating for a few seconds if the Sprinkler Valve is Closed, and a new component is activated.
  • Edge case where the distance check for the nearest interactable component would fail.
  • ic_far_disablePasscodes config option being ignored.
  • TEST button saying a passcode is required, when ic_far_disablePasscodes is true.
  • ALARM and BUZZER LEDs being stuck in the ON condition after being tested.
  • SILENCE ALARM button not working if an Alarm System was silence, but a second component was then activated.

v1.3 - 11/19/2024​

Added:

  • Sprinkler Valves
    • Sprinkler Valves are optional, any systems without a Sprinkler Valve will behave as it did prior to v1.3.
    • Only one Sprinkler Valve can be placed per Alarm System.
    • Sprinkler Valves have two positions:
      • Open
        • Water can flow.
        • Sprinklers will activate.
        • Sprinkler Bell will sound.
      • Closed
        • Water cannot flow.
        • Sprinklers will not activate, and pre-activated Sprinklers will stop showing water.
          • If the Sprinkler Valve is Opened again after being Closed, but before a system reset, pre-activated Sprinklers will show water again.
        • Sprinkler Bell will not sound.
    • If an Alarm System is in Alarm, and there is a triggered Sprinkler, the Sprinkler Valve must be placed in the Closed position before the system can reset.
      • tip

        Be sure to place it back in the Open position afterward though, or else Sprinklers will not activate when there's a fire!

    • Sprinkler Valves have their own Ace Permission.
    • SprinklerValveChanged event.

Changed:

  • If an Alarm System contains a Sprinkler Valve, the Sprinkler Bell sound effect will come from the position of the Sprinkler Valve instead of the center of the Alarm System.
    • tip

      Not sure where the Sprinkler Valve is located in an Alarm System? Follow the sound of the bell!

Removed:

  • Server console warning about permissions not being correctly set-up.

v1.2.*​

v1.2.2 - 11/18/2024​

danger

Major breaking changes to the Events were made in this version, do not blindly update.

Added:

Changed:

Removed:

  • getAlarmSystem export.
    • If you know the ID of the Alarm System, you likely already have access to an AlarmSystem object.
    • If you want to get all of an Alarm System's Control Panels, Pull Stations, etc., use the new getAlarmSystemComponents export.
  • Components from the AlarmSystem data type.
  • alarmSystemId from all components (Pull Stations, Sounders, etc.).
    • If you know the ID of the Alarm System, you likely already have access to an AlarmSystem object.

v1.2.1 - 11/17/2024​

Added:

  • Example in editable/pager.lua for changing tones paged based on which Alarm System is activated.

Fixed:

  • Issue where not passing enough arguments to Exports would throw a confusing error.
  • PullStationTriggered event example code referencing a non-existed variable.
  • alarmSystemId parameter on data returned by Exports incorrectly being passed as alarmSystem.

v1.2 - 11/16/2024​

Added:

  • Check to prevent multiple of the same Alarm System being loaded.
  • Error message when a file listed as an fire_alarms file could not be found.

Changed:

  • Warning and Error messages when ingesting Alarms System files to match the style of others from the resource, as well as to include both the file and resource name when referring to Alarm Systems.
    • Example: INFO: Ingested 15 Alarm Systems from **food_stores.lua** (**inferno-alarms**), 48 total.

Fixed:

  • Errors appearing in the client console complaining about config values not being set, when really they had.
  • The error message that appeared when you had no set default model values, showing the default values as Dictionary<bool,sting> etc instead of their actual JSON values.
  • Multiple people being able to interact with an Alarm System Control Panel at once.
    • Even if there are multiple Control Panels for one Alarm System, only one can be used at once.
  • SystemDisabled event not being fired.

v1.1.*​

v1.1 - 11/11/2024​

Added:

  • IgnoreProximity flag for Alarm Systems which removes the warning in the server console when one or more systems are within 30 units of each other.
warning

We suggest only using this if you're confident you've set up your alarm systems far enough away from each other not to overlap.

  • Error message to the server console that appears when the config.cfg file has not been executed.
  • triggerPullStationAtPosition Export which allows for the activation of a random Pull Station of a system within 50 units of the provided position.
  • getAlarmSystemPasscode Export which returns just an Alarm System's passcode.

Fixed:

  • Space Bar missing from the Tool controls helper.
  • Typos 😔
  • Outdated docs link.
  • Bug that prevent all but the first Alarm System's Control Panel from opening.
  • Postal codes not being loaded from Alarm System files.
  • Missing sounders in some of the stock resources.

v1 - 11/11/2024​

Initial resource release.