![]() |
|
Welcome to the Vanguard Spheres forums. You are currently viewing our boards as a guest which gives you limited access to view our discussions, articles/interviews and photo galleries. By joining our community you will gain access to post your own topics, communicate privately with other members (PM), respond to polls, upload your own photos and access many other special features and tools like our upcoming Guild Management Tool (GMT). Registration is fast, simple and absolutely free so please, join our community today! As a bonus this banner will disappear once you are registered! If you have any problems with the registration process or your account login, please contact support. |
|
|||||||
![]() |
|
|
LinkBack | Thread Tools |
|
|
#1 (permalink) |
|
Member
|
Parser for Testing
This may not be the right spot, if not, please go ahead and move it.
Does anyone know of a decent parser for Vanguard that we can use when testing? It seems like right now we are having to go with "gut feeling" on a lot of stuff, and by watching the numbers that pop up over the mob's head, and by reading the combat spam as fast as we can. It would be kind of nice to be able to use a parser on the combat log to determine if things are proccing, how many times things crit, what kind of damage abilities do on average, etc.
__________________
-Razlath Kurik Malsviriejer (Dark Elf Dread Knight - Shidreth) You will know me by the scars I bear, You will know me by the hate I swear. |
|
|
|
|
|
#2 (permalink) |
|
Junior Member
|
i was doing some testing because i was thinking about making a parser, but i found that the combat window and the combat log displays the incorrect data.
i was testing with a bloodmage and the damage did not change after putting on searing pact, but the amount of hp that was removed changed. haven't done any output damage testing yet, but with the huge number that shows up in the log sometimes (not sure when) it would throw the dps way off. though you could just not include any number over a certain amount, but that would not be the correct number either. though i still may try my hand at writing one but well see ![]() |
|
|
|