Originally Posted by
Styrmir
@MrDDT
I am unable to recreate any of the errors you get. As far as my testing and running of my games, things work as intended.
1) Tested melee and ranged attack on NPC and player on top of dead foe. Worked.
2) Tested melee and ranged attack on NPC and player on top of blood left by moved dead foe. Worked.
3) Tested melee and ranged attack on NPC and player on top of blood left by removed dead foe. Worked.
4) Tested melee and ranged attack on killed and brought back player. Worked.
5) Tested melee and ranged attack on killed and brought back on top of blood pool. Worked.
6) Tested melee and ranged attack on changed altitude of player. Worked.
7) Tested melee and ranged attack on changed altitude of player, killed and brought back. Worked.
8) Tested melee and ranged attack on changed altitude of player, killed and brought back on blood pool. Worked.
9) Created new encounter, added to map, npc's show up hidden on map and combat tracker. Worked.
ps. The onZoom script warning can be ignored. It is due to the way the layers code works and it's not something that can be changed and it has no effect on the running of the game.
This alone has probably taken a good 30 minutes so far of getting things up and running, testing the various scenarios and replying with the results. Trying to test and recreate errors takes time and effort before I can even start figuring out what might be going wrong in the code, which is the bulk of the work.
This is why it's important to be as detailed as possible, like Trenloe said before the error is the first thing that's needed (you did have the error output in the image so that's fine), exactly what were you doing when the error occurred, how were you doing it, does it always happen, any specific tokens, module used if any, npc's at play (from what module if any?), what weapon/s is/are used, any altitudes at play, map used (module if any), etc.
As you see I tried all sorts of variations of what you did to try to recreate the error, but on my end everything works without fault.
This become even more important now that most bugs have been cleared up, so it's really mostly rare outlier cases of very specific circumstances that there is no way for me to foresee, that errors show themselves.
So in general I'll ask of you all to please, try to do as much testing and scrutinizing yourselves as you are able to before you report a bug, and report in as much detail as possible. Make sure you can recreate the error by a set number of steps and/or situations, that you can then report with your bug report. So I can actually make good use of my time, of which is limited.