When using playTriggerEffect on an assetBundle, at first I didn't know why it was not working. I could have done some testing to look up my trigger effects, but instead I had a hunch that the indexes might start at 0 instead of 1. Sure enough, that fixed my issue. This was confusing to me because when you click on the item and go to the trigger effect, the trigger is labeled at 1 by default.

Now I'm not sure if this could be considered a bug, really. But there are a few instances where indexes start at 0 when almost every other index, including lua loops, all start with 1. Notably, buttons and notepad tabs. Perhaps drawing attention to it in the Knowledge Base article would help?

Anyway, thank you for the great update! =)