Quantcast
Download
(34 Kb)
Download
Updated: 09/02/19 12:08 AM
Pictures
File Info
Compatibility:
Scalebreaker (5.1.5)
Updated:09/02/19 12:08 AM
Created:08/26/18 09:28 PM
Monthly downloads:878
Total downloads:52,877
Favorites:29
MD5:
Asylum Tracker  Popular! (More than 5000 hits)
Version: 2.0.5
by: init3 [More]


This addon was created to provide preemptive warnings for many of the mechanics in vAS +2

Dependencies:

Currently the addon includes user-provided translations in German, French, and Japanese for both the notifications and for the settings configuration menu. The language will be selected based on your in-game client language.

thanks cricket

Notifications include:
  • Olms' HP: Displays on screen within 5% of the jump phase
  • Storm the Heavens: ~5s preemptive countdown before the kite phase starts
  • Llothis' Defiling Blast: ~5s preemptive countdown before blast starts.
  • Protectors: Displays when the protectors start to shield Olms
  • Felms' Teleport Strike: ~5s preemptive countdown before jump starts
  • Llothis' Oppressive Bolts: ~13 countdown before he needs to be interrupted (Timer doesn't apply to the first cast)
  • Olms' Steam Breath: ~5s warning before his steam breath attack. (Timer doesn't apply to the first cast)
  • Trial by Fire: Not preemptive, just displays when it starts being cast.
  • Maim: Displays a countdown for the duration of Felms' maim while it is on you.

/astracker - Opens the settings menu
/astrackertoggle - Locks/Unlocks the notifications (can also be done within the settings menu)

Each Notification is resizable, movable, and the color can be changed. (OlmsHP, Storm and Sphere notifications alternate between 2 different colors, which is why it displays 2 colors in the picture)

Displays a notification when Llothis/Felms comes up/goes down and provides 10s and 5s notifications before they come back up

Here's a video of a friend of mine using the original release of the addon in a +2 run:
https://www.youtube.com/watch?v=AXAuoY0rNXw

Note: The "Toxic" notification when Llothis is interrupted can be changed in the settings to whatever you want.
Version 2.0.5:
+ Added potential fix for mechanics saying they are targeting the wrong person

Version 2.0.4:
+ Fixed bug with Center Screen Announce and re-enabled Llothis and Felms Notifications

Version 2.0.3:
+ Commented out the entire function referencing CenterScreenAnnounce.

Version 2.0.2:
+ Removed calls to CenterScreenAnnounce (This disables the notifications for when Llothis and Felms change from a dormant state. I removed this because I believe there may be some conflicts with some other addons using CenterScreenAnnounce, but I can't personally reproduce any errors for it.

Version 2.0:
+ Added the ability to change the color of the countdown timer in the settings
+ Added ability to track exhaustive charges
+ Added option to adjust Olms' timers to account for another mechanic happening first. (Disabled by default)
* For example, if Steam is happening in 20s and Storm the Heavens is happening in 23s then the Storm the Heavens timer will be changed so it hits 0s as steam ends.
* If two timers are too close to each other, they will not be adjusted because it's uncertain which will occur first.
+ Added option to adjust oppressive bolts timer based on if defiling blast is supposed to happen first. (Disabled by default)
+ Changed all timers to say soon instead of sitting at 0 for consistency
+ Revamped /astracker slash command
+ Toggling UI will now place a backdrop behind the notifications to show where they can be grabbed at. The dimensions of the control for the notifications will also now correctly adjust when changing the size of the notifications.
+ The Fire notification now provides a timer
+ The addon will now attempt to provide a more accurate timer for Llothis' and Felms' first cone/bolts/jump.
+ Fixed Maim Tracking
+ Restructed addon across multiple lua files for readability
+ Added checks for Russian names for Felms/фелмс and Llothis/ллотис to provide better support for players using ruESO [https://www.esoui.com/downloads/info1347-RuESO.html]
+ General code optimization
+ Rewrote the comments for the addon for better readability
+ Added ability to override in-game language and use whatever (supported) language you desire within AsylumTracker

Version 1.8:
+ Removed LibStub
+ Removed LibUnits
+ Removed bundled version of LibAddonMenu. LibAddonMenu must now be installed separately.

Version 1.7.2:
+ Added ability to change the volume and sound effects for Defiling Blast and Storm the Heavens

Version 1.7.1:
+ Decreased Initial Defiling Blast timer by 6s
+ Decreased Initial Teleport Strike timer by 3s

Version 1.7:
+ Added Ability to change the opacity of notifications.
+ Attempted to provide notifications for the first cast of Defiling Blast, Oppressive Bolts, and Teleport Strike.
+ Adjusted Storm and Steam timers to account for the other happening first
+ Changed the refresh rate for timers from 1s to 500ms
+ Updated to API version 100028 (Scalebreaker)

Version 1.6.1:
+ Updated to API Version 100027 (Elsweyr)

Version 1.5.1:
+ Added ability to set custom text for the protector notification from in-game without editing lua files

Version 1.5:
+ Updated to API Version 100026 (Wrathstone)
+ Adjusted timer for Felms' Teleport Strike so that the countdown would correctly provide a 5s warning

Version 1.4.4:
+ Added French translations (Thanks, Floliroy)

Version 1.4.3:
+ Fixed German Fire notification
+ Added Japanese translations (Thanks, Sestoral)

Version 1.4.2:
+ Changed the method of determining if you're fighting Olms
+ Added German translations for the settings menu and in-game notifications. (Thanks, Cricket)

Version 1.4.1:
+ Changed "Heilinger to Heiliger in the German locale file

Version 1.4:
+ Fixed bug where the addon would not completely load if you were not using the English client. (Thanks for the help, Crondira)
+ The addon will now load for the English, German, and French language clients (the in-game notifications are still hardcoded in English. If you would like to help add additional support for your language, feel free to message me)

Version 1.3:
+ Update to API Version 100025

Version 1.2:
+ Added Priorities for notifications so time sensitive notifications would hopefully not be delayed as much (Vitality Decreased notifications has had the biggest effect on the delay).
+ Redesigned the timers so they would be more consistent and not accidently skip an entire second in rare cases
+ Added Debugging function to prevent chat spam by accidently leaving in debug lines
+ The on-screen notifications will now (dis)appear instantly when you toggle the setting in the settings menu
+ Added the ability to toggle Llothis/Felms Notifications

Version 1.1:
+ Added a notification to track Felms' maim
+ Added the ability to scale up/down notifications in addition to the font-size for people who want really small or really big notifications
+ Adjusted the Felms/Llothis up/down notifications

Version 1.0.7:
+ Changed the slash commands from /ast and /asttoggle to /astracker and /astrackertoggle to avoid conflicts with AIM's Synergy Tracker

Version 1.0.6:
+ Fixed a bug where the sphere and kite notifications would sometimes not alternate in color if using non-default colors

Version 1.0.5:
- Removed a debug line that I accidentally left in which would spam the chatbox throughout the entire Olms fight.

Version 1.0.4:
- Removed the HIDE notification before Olms' jump in favor of just showing his % health. (His health no longer shows decimals and now just truncates/floors the value. The reason for this is because Olms doesn't jump exactly at 90/75/50/25% and it could be confusing when he jumps at 90.6)

Version 1.0.3:
+ Changed the "BLOCK" message when defiling blast is about to be cast from "BLOCK" to "BLAST: SOON"

Version 1.0.2:
+ Olms' storm the heavens mechanic seems to be delayed ~5s after ZoS fixed Olms not flying during kite, so I've adjusted the timer accordingly.

Version 1.0.1:
+ Added a 5s warning for Llothis and Felms respawn
+ Fixed an issue with mislabeled dependencies

Version 1.0:
+ Initial Upload
Optional Files (0)


Archived Files (27)
File Name
Version
Size
Uploader
Date
2.0.4
34kB
init3
08/29/19 06:20 PM
2.0.3
34kB
init3
08/26/19 08:23 PM
2.0.2
34kB
init3
08/26/19 06:22 PM
2.0
35kB
init3
08/25/19 07:02 PM
1.8
26kB
init3
07/25/19 03:03 PM
1.7.2
67kB
init3
07/21/19 06:36 PM
1.7.1
67kB
init3
07/21/19 04:54 PM
1.7.1
67kB
init3
07/21/19 03:14 PM
1.6.1b
73kB
init3
06/10/19 10:52 AM
1.6.1
73kB
init3
04/21/19 10:57 PM
1.5.1
73kB
init3
03/06/19 09:17 PM
1.5
73kB
init3
03/06/19 05:31 PM
1.4.4
73kB
init3
11/29/18 11:59 PM
1.4.3
71kB
init3
11/25/18 09:24 PM
1.4.2
65kB
init3
11/20/18 10:05 PM
1.4.1
62kB
init3
11/18/18 01:14 PM
1.4
61kB
init3
10/23/18 10:26 PM
1.2
61kB
init3
09/02/18 09:21 PM
1.1
61kB
init3
08/28/18 10:34 PM
1.0.7
60kB
init3
08/28/18 11:24 AM
1.0.6
60kB
init3
08/27/18 11:41 PM
1.0.5
60kB
init3
08/27/18 10:30 PM
1.0.4
60kB
init3
08/27/18 10:24 PM
1.0.3
60kB
init3
08/27/18 08:52 PM
1.0.2
60kB
init3
08/27/18 03:08 PM
1.0.1
60kB
init3
08/27/18 12:47 PM
1.0
60kB
init3
08/26/18 10:18 PM


Post A Reply Comment Options
Unread 08/27/19, 04:41 PM  
init3
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 35
Uploads: 9
CSA Errors

Okay, I managed to consistently reproduce the CSA errors so I readded the code for it and added some checks to prevent it in the future. I'm going to hold off on releasing it yet on Minion though because I want to try and be sure that there are no more issues with addon.

The version that is on Minion should have no errors due to the CSA code being completely commented out; however, a side affect of that is the Llothis and Felms notifications (The ones about when they are changing to/from a dormant state) will not work in the version that is on Minion.
Report comment to moderator  
Reply With Quote
Unread 08/27/19, 12:58 PM  
init3
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 35
Uploads: 9
Re: Re: Re: Re: Errors

I haven't noticed or heard of any performance issues besides the one caused by these errors, I'll keep an eye out though.

Originally Posted by iiJonno
i have checked the bug catcher log theres nothing from the time of our raid
Report comment to moderator  
Reply With Quote
Unread 08/27/19, 10:58 AM  
iiJonno
 
iiJonno's Avatar

Forum posts: 3
File comments: 12
Uploads: 0
Re: Re: Re: Errors

i have checked the bug catcher log theres nothing from the time of our raid
Originally Posted by init3
I'm pretty sure the most recent update should fix it. I saw a stream last night where people were getting spammed by CenterScreenAnnounce errors that were causing people's FPS to tank. I'm still looking into it though. Thanks for providing your addon list. I suspect you were getting these errors but your bugcatcher addon is why you didn't see them


Originally Posted by iiJonno
diddnt have any error popups just the fps tanking have updated but wont be able to test until thursday

addon list if it helps
Code:
ADR, addon selector, advanced filters,  asylum sanctorum status pannel, azurah, bugcatcher,codes combat alerts combat metrics, dressing room,  harvens improved skills window, hodor reflexes improved deathrecap iifa itemization browser, kyoma's repair 'n recharge, light attack helper, raidificator, raid notifier(asylum options all off), s'rendarr, wykkyd toolbar, zolan's slash commands
Originally Posted by init3
Originally Posted by iiJonno
was all default
Okay, I just pushed an update that removed the code that mentions when Llothis and Felms change from their dormant states (The Felms/Llothis in 10/5 etc notifications). I believe there may be some conflicts for people running AsylumTracker alongside some other addon that is creating errors, but I can't personally reproduce these errors.

I ran a vAS +2 last night (EST Timezone) before pushing the update with every notification setting enabled, and did not receive any errors.

I also just finished 2 nAS +2 runs where every person in the runs was using the updated version (version 2.0) of the addon. In the first run I had default settings and in the second run I had everything enabled. In both cases nobody received any errors and nobody's FPS tanked in execute or at any other point in the runs. Again, this may be because nobody has the conflicting addons related to the code I removed in the update I just pushed, but beyond that I can't reproduce any issues with the addon.

If you can manage to get a screenshot of the errors that are popping up on your screen in the trial, that would be the best way to help me find the cause of the issues, but for now I can't reproduce any problems.

I just commented out any other references to CenterScreenAnnounce in 2.0.3. If anybody running this version of the addon is still receiving errors related to CenterScreenAnnounce then they aren't receiving the errors from AsylumTracker
Report comment to moderator  
Reply With Quote
Unread 08/27/19, 10:50 AM  
init3
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 35
Uploads: 9
Re: Re: Errors

I'm pretty sure the most recent update should fix it. I saw a stream last night where people were getting spammed by CenterScreenAnnounce errors that were causing people's FPS to tank. I'm still looking into it though. Thanks for providing your addon list. I suspect you were getting these errors but your bugcatcher addon is why you didn't see them


Originally Posted by iiJonno
diddnt have any error popups just the fps tanking have updated but wont be able to test until thursday

addon list if it helps
Code:
ADR, addon selector, advanced filters,  asylum sanctorum status pannel, azurah, bugcatcher,codes combat alerts combat metrics, dressing room,  harvens improved skills window, hodor reflexes improved deathrecap iifa itemization browser, kyoma's repair 'n recharge, light attack helper, raidificator, raid notifier(asylum options all off), s'rendarr, wykkyd toolbar, zolan's slash commands
Originally Posted by init3
Originally Posted by iiJonno
was all default
Okay, I just pushed an update that removed the code that mentions when Llothis and Felms change from their dormant states (The Felms/Llothis in 10/5 etc notifications). I believe there may be some conflicts for people running AsylumTracker alongside some other addon that is creating errors, but I can't personally reproduce these errors.

I ran a vAS +2 last night (EST Timezone) before pushing the update with every notification setting enabled, and did not receive any errors.

I also just finished 2 nAS +2 runs where every person in the runs was using the updated version (version 2.0) of the addon. In the first run I had default settings and in the second run I had everything enabled. In both cases nobody received any errors and nobody's FPS tanked in execute or at any other point in the runs. Again, this may be because nobody has the conflicting addons related to the code I removed in the update I just pushed, but beyond that I can't reproduce any issues with the addon.

If you can manage to get a screenshot of the errors that are popping up on your screen in the trial, that would be the best way to help me find the cause of the issues, but for now I can't reproduce any problems.

I just commented out any other references to CenterScreenAnnounce in 2.0.3. If anybody running this version of the addon is still receiving errors related to CenterScreenAnnounce then they aren't receiving the errors from AsylumTracker
Last edited by init3 : 08/27/19 at 10:52 AM.
Report comment to moderator  
Reply With Quote
Unread 08/27/19, 10:23 AM  
iiJonno
 
iiJonno's Avatar

Forum posts: 3
File comments: 12
Uploads: 0
Re: Errors

diddnt have any error popups just the fps tanking have updated but wont be able to test until thursday

addon list if it helps
Code:
ADR, addon selector, advanced filters,  asylum sanctorum status pannel, azurah, bugcatcher,codes combat alerts combat metrics, dressing room,  harvens improved skills window, hodor reflexes improved deathrecap iifa itemization browser, kyoma's repair 'n recharge, light attack helper, raidificator, raid notifier(asylum options all off), s'rendarr, wykkyd toolbar, zolan's slash commands
Originally Posted by init3
Originally Posted by iiJonno
was all default
Okay, I just pushed an update that removed the code that mentions when Llothis and Felms change from their dormant states (The Felms/Llothis in 10/5 etc notifications). I believe there may be some conflicts for people running AsylumTracker alongside some other addon that is creating errors, but I can't personally reproduce these errors.

I ran a vAS +2 last night (EST Timezone) before pushing the update with every notification setting enabled, and did not receive any errors.

I also just finished 2 nAS +2 runs where every person in the runs was using the updated version (version 2.0) of the addon. In the first run I had default settings and in the second run I had everything enabled. In both cases nobody received any errors and nobody's FPS tanked in execute or at any other point in the runs. Again, this may be because nobody has the conflicting addons related to the code I removed in the update I just pushed, but beyond that I can't reproduce any issues with the addon.

If you can manage to get a screenshot of the errors that are popping up on your screen in the trial, that would be the best way to help me find the cause of the issues, but for now I can't reproduce any problems.

I just commented out any other references to CenterScreenAnnounce in 2.0.3. If anybody running this version of the addon is still receiving errors related to CenterScreenAnnounce then they aren't receiving the errors from AsylumTracker
Report comment to moderator  
Reply With Quote
Unread 08/26/19, 06:30 PM  
init3
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 35
Uploads: 9
Errors

Originally Posted by iiJonno
was all default
Okay, I just pushed an update that removed the code that mentions when Llothis and Felms change from their dormant states (The Felms/Llothis in 10/5 etc notifications). I believe there may be some conflicts for people running AsylumTracker alongside some other addon that is creating errors, but I can't personally reproduce these errors.

I ran a vAS +2 last night (EST Timezone) before pushing the update with every notification setting enabled, and did not receive any errors.

I also just finished 2 nAS +2 runs where every person in the runs was using the updated version (version 2.0) of the addon. In the first run I had default settings and in the second run I had everything enabled. In both cases nobody received any errors and nobody's FPS tanked in execute or at any other point in the runs. Again, this may be because nobody has the conflicting addons related to the code I removed in the update I just pushed, but beyond that I can't reproduce any issues with the addon.

If you can manage to get a screenshot of the errors that are popping up on your screen in the trial, that would be the best way to help me find the cause of the issues, but for now I can't reproduce any problems.

I just commented out any other references to CenterScreenAnnounce in 2.0.3. If anybody running this version of the addon is still receiving errors related to CenterScreenAnnounce then they aren't receiving the errors from AsylumTracker
Last edited by init3 : 08/26/19 at 08:27 PM.
Report comment to moderator  
Reply With Quote
Unread 08/26/19, 02:54 PM  
iiJonno
 
iiJonno's Avatar

Forum posts: 3
File comments: 12
Uploads: 0
was all default
Report comment to moderator  
Reply With Quote
Unread 08/26/19, 02:22 PM  
init3
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 35
Uploads: 9
FPS tanking

Sorry to hear that. I'll look into it, thanks for the report.

If you could tell me what settings you had enabled/disabled in settings that would be helpful

Originally Posted by iiJonno
something with the new update is causing extreme FPS issues my entire raid group on 10-15 fps where usually about 50+ we all had to revert to previous version to fix for time being. the issues start at about 25% boss health on +2 veteran for us if that helps you
Last edited by init3 : 08/26/19 at 02:44 PM.
Report comment to moderator  
Reply With Quote
Unread 08/26/19, 01:50 PM  
iiJonno
 
iiJonno's Avatar

Forum posts: 3
File comments: 12
Uploads: 0
something with the new update is causing extreme FPS issues my entire raid group on 10-15 fps where usually about 50+ we all had to revert to previous version to fix for time being. the issues start at about 25% boss health on +2 veteran for us if that helps you
Last edited by iiJonno : 08/26/19 at 01:52 PM.
Report comment to moderator  
Reply With Quote
Unread 06/10/19, 11:41 PM  
init3
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 35
Uploads: 9
Re: Hmmmmm

Originally Posted by Kyzeragon
*Wonders who Gary is...*
Code:
if HashString(AsylumTracker.displayName) == 1325046754 then targetName = "Gary" end
He's Gary, obviously.
Report comment to moderator  
Reply With Quote
Unread 06/10/19, 10:40 PM  
Kyzeragon
 
Kyzeragon's Avatar
AddOn Author - Click to view AddOns

Forum posts: 0
File comments: 18
Uploads: 2
Hmmmmm

*Wonders who Gary is...*
Code:
if HashString(AsylumTracker.displayName) == 1325046754 then targetName = "Gary" end
Report comment to moderator  
Reply With Quote
Unread 11/27/18, 08:11 AM  
Siegtime

Forum posts: 15
File comments: 76
Uploads: 0
Re: Re: Re: I would like to ask Japanese translation.

Originally Posted by Siegtime
Originally Posted by init3
Originally Posted by Siegtime
If you can translate Japanese, certainly, please.
I have a friend working with me on that currently
That is dependable. I expect it.
Thank you for JP Translation
Report comment to moderator  
Reply With Quote
Unread 11/22/18, 05:38 AM  
Siegtime

Forum posts: 15
File comments: 76
Uploads: 0
Smile Re: Re: I would like to ask Japanese translation.

Originally Posted by init3
Originally Posted by Siegtime
If you can translate Japanese, certainly, please.
I have a friend working with me on that currently
That is dependable. I expect it.
Report comment to moderator  
Reply With Quote
Unread 11/20/18, 04:01 AM  
init3
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 35
Uploads: 9
Re: I would like to ask Japanese translation.

Originally Posted by Siegtime
If you can translate Japanese, certainly, please.
I have a friend working with me on that currently
Report comment to moderator  
Reply With Quote
Unread 11/20/18, 12:28 AM  
Siegtime

Forum posts: 15
File comments: 76
Uploads: 0
Wink I would like to ask Japanese translation.

If you can translate Japanese, certainly, please.
Report comment to moderator  
Reply With Quote
Post A Reply



Category Jump: