So far what i understand a little more from more testing.
I have a lot of actions (about 150). From the previous for-in loop i found that there was a chunk of maybe about 30+ actions that come up sequentially in the runtime.js file of my plugin but are missing from the prototype in export. there are actions which aren't missing which come before and after this chunk. My theory is that the 'compiler' - parser- whatever you might call it, which runs during export, is clipping out a big chunk of code from the runtime for some strange reason which i'm not sure of.
I added alerts throughout my code so that i have my runtime.js file set up something like this:
.................... above this point there are lots of actions that weren't missing around where actions started to go missing from acts.proto on export i added alerts.
alert('start')
Acts.prototype.function001 = function(p1,p2,p3){
//code
};
alert('1');
Acts.prototype.function001 = function(p1,p2,p3){
//code
};
alert('2');
Acts.prototype.function002 = function(p1,p2,p3){
//code
};
alert('3');
Acts.prototype.function003 = function(p1,p2,p3){
//code
};
alert('end')
.................. more actions which didn't go missing.
running the project, in preview all the alerts fire as you would expect, but on export only those which come after a certain point, and those which come before a certain point, are firing. theres a block of script which just disappears for no good reason. I've poured over the code and there doesn't "seem" to be anything suspicious which should cause this, but it's happening anyway.