CRL Question on Fumble Listener

Trying to get this to function but it does not seem to recognize when a fumble happens, the sister script for Criticals works great! !crl \\create,name=Critical,text=##,roll=critical \\!critical \\!roll20AM --play|Critical ^^^^ This works fine !crl \\create,name=Fumble,text=##,roll=fumble \\!fumble \\!roll20AM --play|Fumble ^^^^This does not

How is it not working? What happens if you replace the API commands with basic text to test? What happens if you try to edit via the !crl \\config command? Im short, I need more info to troubleshoot. There are a ton of things that can happen that could be described as not working.

Sorry, it does Not seem to recognize when a fumble is being rolled for instance when someone rolls for 20 the script activates and rolls on the critical chart when someone rolls a one it does not activate the fumble chart.

Tried typing fumble in manually didn’t seem to change let me try typing the other parts manually.

Yea I tried using \\TEST instead of the commands and can't get that to run on a fumble either.

" > CRL ERROR ||| Ability: Fumble was not parseable. You may want to remove/update this ability via the config menu." This Error seems to be coming up in the API

Does the Fumble roll result work for anyone else?

No it doesn't work for me either. I digged a wee bit into the source and can maybe give some hints for Scott where to look. Minimal Testcase: The minimal testcase I came up with that yields the error in the log and shows the same behaviour as experienced by Anthony is this: !crl \\create,name=f,text=##,roll=fumble \\fumble That creates the error in the log mentioned by Anthony above "Ability: f was not parseable...". I believe this is because the else if statement in line 412 fails because c.results.v is undefined, at least that's what I got by adding some logging to the catch block and removing every instance of `v` one by one. Hope this helps.

Florian B. said: No it doesn't work for me either. I digged a wee bit into the source and can maybe give some hints for Scott where to look. Minimal Testcase: The minimal testcase I came up with that yields the error in the log and shows the same behaviour as experienced by Anthony is this: !crl \\create,name=f,text=##,roll=fumble \\fumble That creates the error in the log mentioned by Anthony above "Ability: f was not parseable...". I believe this is because the else if statement in line 412 fails because c.results.v is undefined, at least that's what I got by adding some logging to the catch block and removing every instance of `v` one by one. Hope this helps. Appreciate you posting and doing that for me! Hope something comes of it!