This is a question regarding the efficiency/memory usage of a quest that I use merely to contain a script with a function which can be called from other scripts.

In this quest script I have created a custom function Function CallMenu(int iMenu) which contains all the structure for navigating some deep configuration menus, and all of their associated options. This same script of course also contains Property references to all of the various items called by these menus.

This function only gets called when a configuration spell is cast.

My question is, would their be any difference in overhead to leave this quest stopped until I needed it, start it and call the function, and stop it within the menu navigation, compared with simply leaving it on all the time?