AlertText: function, the string to show as alert text.AlarmText: function, the string to show as alarm text.TextAlert: boolean, turn on or off on screen text SoundAlert: boolean, turn on or off sounds.SpeechAlert: boolean, turn on or off tts texts.GroupSpeechAlert: boolean, turn on or off group tts texts.The fields that are valid on PerTriggerOptions are the following: The size and color of info text alerts can also be changed by #popup-text-container and #timeline-container which can be changed via user/raidboss.css See the ui//.css to find the names of things you can modify.įor example in ui/raidboss/raidboss.css, you see the The user/.css file can change positions, sizes, colors, etc. cactbot/user/ relative to the CactbotOverlay.dll. If that doesn’tĮxist, it will then look for. Lets you specify where your cactbot/user directory. The OverlayPlugin config panel has a text field for “Custom User Config Directory”, which If you want to do it yourself, then create a user/.css or a user/.jsįile, where is the name of the UI module, such as raidboss orĪfter making any changes to these files, pressing the “Reload overlay” button for theĪppropriate cactbot in ACT’s OverlayPlugin settings will apply the changes. The user/ĭirectory already includes some example configuration files, which you can rename and use.įor example the user/raidboss-example.js can be renamed to user/raidboss.jsĪnd edited to change the behaviour of the raidboss module. Will prevent your changes from being clobbered during future cactbot updates.Īll cactbot UI modules can load user settings from the user/ directory.
The ui directory, and any user configuration should go in files in the user directory. The general philosophy of cactbot is that future updates of cactbot will update files inside
0 kommentar(er)
