Instructions for collecting data: Very rough version. I will keep updating it based on questions or any problems.
Introduction
I think it would be nice to have more enemy data on gw2dungeons. It’s pretty simple to check these things but takes some time. If someone has too much time to waste then I would happily accept any help.
Most importantly you should check gw2dungeons.net and see what is actually missing. Then collect data and report to me either here, pm or email (wethospu@gmail.com).
First of all, download example spreadsheet from http://gw2dungeons.net/DL/Example.zip
Enemy health
This is easiest and fastest to check but requires using an external tool (dps utility by frifox, link in the spreadsheet). There is always a risk of getting banned but I’m still here even after using it publicly.
All you have to do is target the enemy and you will see its health. A list to fill is provided on the spreadsheet.
Attack damage
Also easy and fast to check. Just get hit by the enemy. If possible, get hit multiple times and use the highest non-critting value.
However, I need normalized values for gw2dungeons so just fill in your stats to the spreadsheet to scale them properly. A list to fill is provided on the spreadsheet.
Enemy type
Easy to test. See https://forum-en.gw2archive.eu/forum/game/dungeons/gw2dungeons-Help-verifying-enemy-types/first for more info.
Enemy armor
Takes some spreadsheet magic and multiple attacks to get decent estimates. However, because weapon strenth downscaling is unknown this doesn’t work on under level 80 enemies. You can still collect data as it can be corrected later.
Two scenarios:
1) You know armor of a nearby enemy (faster):
Minimize any variables like vulnerability, runes or randoms traits. Pull enemies together. Use any cleave or aoe attack and hit both known and unknown enemy. Damage difference can be used to scale known armor value to unknown armor value.
For this there is a cleave test in the spreadsheet. There are 4 different hit cells. Hit 1 is meant for known enemy and hit 2 for the other one. If attack was a critical you should use “crit” one instead.
You only need to fill Critical Damage value if one hit was critical while the other was NOT (check attributes, use downscaled value). End result is 4 possible armor values depending which values you filled. If you don’t know what is the right one put 0 to unused hit cells. Keep in mind that because of in-game rounding, end result is not 100% accurate.
2)No known armor values (longer):
Minimize any variables like vulnerability, runes or random traits to keep your hits steady. Use the other armor test in the spreadsheet. Fill in your values. Use only one attack (get coefficient from wiki) and keep updating minimum and maximum hit. Hit until sufficient damage is reached or you can guess correct armor value.
Note: Remember to copy-paste new test scenario in both cases. Starting values might be needed to correct stuff later.
Attack animation
Pretty hard to test. You need a video recording tool and some software which allows you to check it “frame-by-frame”. I use one purchased video editing software so no idea about free alternatives.
So record a short video of the attack and then analyze when it starts and when it hits. Also try to describe enemy behavior. Check gw2dungeons for examples. A list to fill is provided on the spreadsheet.
Attack cooldown
Same as above but doesn’t need accuracy. You can also use a timer (clock or your own skill cooldowns).
Record video of the fight (or take time between attacks) and see often the attack is used. Try to get multiple skill usages and report the minimum. Keep in mind in any special requirements like range.
Attack effects
Check duration of any effects like boons and conditions. Record a short video of the attack (or use timer).
(edited by Wethospu.6437)