Context:
I've recently encountered some weird behavior with script-created Zeus modules while locally testing rc compatibility of the Admin/Development-Tool I'm writing at the moment. From what I've searched online / on the feedback tracker I couldn't find anything about this, although I might have filtered incorrectly (apologies if so).
Explanation:
In SP / local MP environment script-created Zeus modules are incapable of remote controlling AI units and can't open the "edit window" when double clicking units. Although Editor placed Zeus modules work as expected in these environments.
Further unexpected/unintended behavior comes along when having RCd a unit using an editor placed module previously. Subsequently using RC, with a script-created module, will default to the last RCd unit (if null / dead it displays the appropriate error message in the zeus menu - regardless of which unit you try to RC and their current status).
However: This is not the case in a dedicated MP environment. Script-created modules work perfectly fine and can use RC to control units just fine. This only happens in SP/local MP.
I've made a quick video trying to showcase this (I recommend watching at 1.5x speed). First part is showing it working perfectly fine on dedi, second part is showing the behavior in sp/local mp. (Video: https://www.youtube.com/watch?v=ubV4AvNd9Tg) (used my Tools mod to simplify showcasing in the video, the behavior isn't affected by this however).