Pulling this back from beyond the valley of 2014...
I finally got into this, and more or less did exactly the "light switch" tutorial, except that I made a FormID List of the NPCs I wanted to disable, fed that into the quest, and am looping over the list to disable/enable NPCs. But it doesn't do anything in-game, and I'm sure it's because I did something wrong at the basic level with the quest setup or something. No Papyrus errors, just doesn't appear to work. I'll be adding log debug script to see if things are firing.
Despite working with quests for the last mod I just released, I still don't get some of the fundamental aspects, and tutorials are really geared around making literal quests with a giver, stages, dialogue etc. and don't seem to get into the finer points of using them as mechanisms to simply control things. I know this understanding will come in time.
My question is, if I wanted this "always running" quest just to execute a script that switches things off/on, do I NEED to have an alias, and should that alias be the player? Or can a quest just "run in the background" without needing to have an alias filled? MCM menus and the quest I put together to control my zoom hotkey mod have a forced reference on the player, which sort of makes sense since both of those only effect the player and nothing else, but this effects placed NPCs.
The second question is whether or not you can call ENABLE/DISABLE on ACHR placed NPC records the same way you can on a direct NPC reference. These NPCs are actually leveled NPC lists placed in the world, so they vary.
I can go into more detail and post code, but some basics on how to set up the quest for an "always-on" script that modifies things in the world would be the best starting point. I tend to skip ahead sometimes.