"Game events", [
[
1, "Score", 0, 0],
[
1, "Rockets", 0, 3],
[
0, [true, "Player and general"],
[
?[-1, cr.system_object.prototype.cnds.IsGroupActive,
?null, false, false, false, false, [
[
1, [
2, "Player and general"]]
?]]
],
[],
[
?[
?0, null, [
[-1, cr.system_object.prototype.cnds.OnLayoutStart,
null, true, false, false, false]
?],
[
[
11, cr.plugins_.Sprite.prototype.acts.Destroy, null],
[
31, cr.plugins_.Audio.prototype.acts.Play, null, [
??[
??2, ["squaremotif1", false]],
??[
??1, [
??2, ""]]
]],
[-1, cr.system_object.prototype.acts.Wait, null, [
??[
??0, [
??1, 1]]
]],
[
31, cr.plugins_.Audio.prototype.acts.Play, null, [
??[
??2, ["mattoglseby - 3", true]],
??[
??1, [
??2, "music"]]
]]
So I'm not sure you really want to do anything with that. From there C2 does call actual javascript functions which each plugin defines (@rexrainbow was describing this) but those are the code "inside" each condition and action and expression. If you like you can use Chrome's debugger and set breakpoints in these functions, but I still don't think there's much to gain from it - it tells you more about how each function works than what your events are doing overall.