You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sounds from the custom alarm will not abide by the range set in the block.
Also it seems as though when unloading the alarm's chunk and then reloading it and coming back to the range it supposed to play at will cause it to play quieter. Unsure if that is a feature or not.
The text was updated successfully, but these errors were encountered:
Priority-6
changed the title
[1.16.5] [Version 1.16.5-0.2.6a] Sound Range Bug from Howler Alarm
[1.16.5] [Java Version 1.16.5-0.2.6a] Sound Range Bug from Howler Alarm
Aug 1, 2022
Sounds from the custom alarm will not abide by the range set in the block.
Also it seems as though when unloading the alarm's chunk and then reloading it and coming back to the range it supposed to play at will cause it to play quieter. Unsure if that is a feature or not.
Here is my config for the mod:
#General settings
[General]
#Allowed Alarms
allowedAlarms = "default,sci-fi,siren,boom,001,ambience_001"
#Default Thermal Monitor Refresh Period
#Range: > 1
thermalMonitorRefreshPeriod = 20
#Load Custom Sounds
useCustomSounds = true
#Web Socket Host
wsHost = ""
#Alarm Pause in Ticks
#Range: 10 ~ 2000
alarmPause = 10
#Max Possible Howler Alarm Range
#Range: > 0
maxAlarmRange = 128
#Web Socket Token
wsToken = "78c2b80a-1203-43fd-a9af-75cec29f5acf"
#Default Panel Refresh Period
#Range: > 1
infoPanelRefreshPeriod = 20
#Web Socket Refresh Rate
#Range: 10 ~ 20000
wsRefreshRate = 100
#Default Howler Alarm Range
#Range: > 0
howlerAlarmRange = 64
#Web Socket Server ID
wsServerID = "408eb5fb-6e35-47a0-85ae-1ebbbec9907f"
#Web Socket Port
#Range: 1 ~ 99999
wsPort = 1
#Default Range Trigger Refresh Period
#Range: > 1
rangeTriggerRefreshPeriod = 20
#Web Socket Enabled
wsEnabled = false
#Disable Range Check
disableRangeCheck = false
Here is a link to a video showcasing the bug:
https://youtu.be/BTprXpgNSAM
The text was updated successfully, but these errors were encountered: