Hm, that is possible - collision events are a bit of an outlier in the way they work.
A workaround would be to temporarily put the event's content into a script, but I'll take a look.
Hi!
I bumped into the same problem. Also using the workaround.
Did you have chance to fix this?
Thx!
I've not released an update yet but hoping to address this in the upcoming build - basically collision events use IDs instead of object names, which breaks with the current detection scheme.
