I really like the filters on the log, and the clear markings on the popouts for resizing. Very nice work, look forward to trying this out in raid. Anyway, just an idea, keep up the good work. There is an app for custom timers on my razer keyboard but something reading your combat logs would be much better not only because it could work for boss health-tied mechanics but also would know when to start and stop timers automatically. I think you get what I'm saying, same thing for mechanics tied to boss health, it would show dmg till mechanic or something like that. Also going a step further you could even create a timer profile for mechanics that occour with time or boss health so that for DG fight for example the overlay would say something like "Heirad lightning field in 3:00" and then keep counting till it reaches zero, and then the timer starts for the next one till heirad dies and then it becomes a timer for doom, and then mark for death from kelsara and force-leech. Really well done, I like your parse and the combat log function is really nice, didn't test it with raids though, will do it later.īut pretty much it's what I've been missing from parsers ever since MoniTOR was discontinued is a full log for all your group members instead of just you, don't know if your parser offers this but if it doesnt you should think about adding this, it really helps troubleshooting in raids for example if a tank dies you can then look at the logs and see if he didn't take any heals or if he was actually one-shoted, you check if someone forgot to cleanse a dot that they should, if a dps neglected a mechanic and took unnecessary damage and that kind of stuff.Īlso one thing that I always wanted on parsers was a pop-out that would detect from the log which boss you are fighting and what difficulty (even if you have to input this) and then as soon as you start the battle if would show you how long till enrage (again, even if you have to input the enrage timer). I may include some sort of raid user list in the future. I realize this does not entirely meet the need you expressed but its close. Also, once combat begins you can see a list of users in combat on the raid tab. Note that if the Raid Light is green and the buttons says "Raiding" then you are connected. I have noted your feedback on the request for a successfully joined message and for the list of people raiding. This allows you to "admin" a group from any machine. If you have a problem member you can simply delete the group and create a new one.Īs for "Admin" of a group from another machine, any admin activity for a group that does not have an Admin Password saved will prompt you for the admin password. Kicking someone out would require a more robust account setup and storage which I am staying away from. A group does not consist of a defined set of members, instead it is just a group of connected raiders. It is true that Admin Groups is not a robust member-group solution. I also did not see a way for an admin to log in on another instance of the program (for example if you got a new computer) With the admin being able to kick from group On top of that, it would be nice if everyone could a list of who is in the group. There should probably be a confirmation like successfully joining or something. When you join a group, it is not very clear that you successfully joined. We used this tonight and only a bit of a complaint regarding raid: Please keep an eye on this and if it continues to occur feel free to submit a bug report online or shoot the support email address (found in the help window of the app) a message with your log attached! Were you dropping out of combat using a stealth ability or something? This would cause a combat end event and a combat start event in the log, resulting in a new "fight". This does not occur for anyone in our raid groups. for example, if our merc dps CC'd an ad, the ad is healed for 4.3k every few seconds and it counts as heals on the parse though, he never healed anyone in the raid. Heals are counted on CCs that are active out of combat i.e concussion missle, whirlwind, etc. Parser starts over after the dread guard ads die before the kell dragon on styrak Parser starts over after Olok The Shadow disappears the first time There were just a few things we noticed as far as bugs: I ran this tonight in our progression HM SNV raid and we are very thrilled with the intricacies that you threw into the parser.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |