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
a) Currently, in content where there is more than 1 enemy (anything other than guardian raids), the name of an encounter is usually chosen as the first (or last - not sure) mob that took damage in that log session (screenshot below). This makes it a bit difficult to understand which encounter in that list was the session you're actually interested in. Also, adding a duration of each encounter instead of only timestamp, might help the user decide which is the encounter they're looking for a bit easier, even when the name is confusing.
b) From version v.0.0.3.8 and onwards (not entirely sure if this happened in previous versions too), encounters with no name but only timestamp are added to the list of encounters (no screenshot). These are times when im afk in a non combat zone like north vern. No encounter entry should be created if there were 0 dmg packets in it.
Examples
a) Boss rush. There are 20+ bosses in it. Most people don't know/remember each boss's name, so when they see a weird name in the encounter list like "Trumpeter Clown" they won't know what it is. Potential workaround: An if statement where if X number of mobs with more than X million hp appear in 1 session, to automatically name that session "Boss Rush" - instead of just picking 1 boss name and naming the entire session after it.
b) Abyss Dungeon. Didn't actually run one to see if it's the same case with boss rush, but an even simpler fix for this is to have an if statement where if a boss with X name (where X is a lookup against a dictionary of all bosses of each abyss dungeon) is detected, and in that session there was less than let's say 4 mobs with more than X million hp (this is needed to avoid incorrectly naming a boss rush session where a Seto was detected as Aira's Oculus) , then name that session after the name of the dungeon that the detected boss belongs to. Then if you click on that session/encounter, you get to another screen where you see a breakdown of the 2-3 bosses you faced in that dungeon.
c) Open world. If for some reason you have your logger on while questing, and for some reason you wanna know which session that is, you could have a statement like "if X mobs detected with less than X hundred thousand hp, then name the session after the zone you were in". Not sure if you can see the zone in the packets. But this use-case is not really useful.
The text was updated successfully, but these errors were encountered:
a) Currently, in content where there is more than 1 enemy (anything other than guardian raids), the name of an encounter is usually chosen as the first (or last - not sure) mob that took damage in that log session (screenshot below). This makes it a bit difficult to understand which encounter in that list was the session you're actually interested in. Also, adding a duration of each encounter instead of only timestamp, might help the user decide which is the encounter they're looking for a bit easier, even when the name is confusing.
b) From version v.0.0.3.8 and onwards (not entirely sure if this happened in previous versions too), encounters with no name but only timestamp are added to the list of encounters (no screenshot). These are times when im afk in a non combat zone like north vern. No encounter entry should be created if there were 0 dmg packets in it.
Examples
a) Boss rush. There are 20+ bosses in it. Most people don't know/remember each boss's name, so when they see a weird name in the encounter list like "Trumpeter Clown" they won't know what it is. Potential workaround: An if statement where if X number of mobs with more than X million hp appear in 1 session, to automatically name that session "Boss Rush" - instead of just picking 1 boss name and naming the entire session after it.
b) Abyss Dungeon. Didn't actually run one to see if it's the same case with boss rush, but an even simpler fix for this is to have an if statement where if a boss with X name (where X is a lookup against a dictionary of all bosses of each abyss dungeon) is detected, and in that session there was less than let's say 4 mobs with more than X million hp (this is needed to avoid incorrectly naming a boss rush session where a Seto was detected as Aira's Oculus) , then name that session after the name of the dungeon that the detected boss belongs to. Then if you click on that session/encounter, you get to another screen where you see a breakdown of the 2-3 bosses you faced in that dungeon.
c) Open world. If for some reason you have your logger on while questing, and for some reason you wanna know which session that is, you could have a statement like "if X mobs detected with less than X hundred thousand hp, then name the session after the zone you were in". Not sure if you can see the zone in the packets. But this use-case is not really useful.
The text was updated successfully, but these errors were encountered: