Scott C. said: Hmm, ok, based on that error, and what you've shown (thanks for the detail btw), I think we're running into a race condition. Part of the problem here is that your critHit listener will actually trigger on any critical roll, regardless of if it is in the attack1 field or not. So, when you then get a crit in attack2, it is trying to trigger both listeners instead of just one. I'd recommend changing critHit's text to be attack1=## instead of just ## I changed the listener to attack=## instead of just ## as suggested and CritHit listener still works that way. The numbering system for attacks in the pathfinder community sheet is attack, attack2, attack3, ect. I double checked it to make sure that the first attack is just attack and not attack1. CritHit 2 listener, attack2=##, still doesn't work though. I still get the same API Output Console error for CritHit even with the updated listener. I did some additional testing and with the listener set to just ## as it was originally and found that it works for only the first attack and not any additional attacks. Setting the listeners to attack=##, attack2=##, ect. seems like the way to go with multiple listeners watching for crits, but I wanted to let you know that if ## should work for any attack that is doesn't appear to be behaving properly. - Meldogs