I suspected that might be the caseThat's really not a suitable solution, then, since this module would need to run regardless of what scenario was being loaded...
---------- Post added at 15:59 ---------- Previous post was at 15:24 ----------
I just thought of a workaround, but I have to warn you it is quite ugly...
In InitModule, you could "poison" all scenario files with BEGIN_PluginModuleName/END pairs. This ensures your module gets the opcLoadState callback. In ExitModule, you could then "unpoison" the scenario files again - bearing in mind that ExitModule doesn't get called if you CTD.
Don't say I didn't warn you :lol: