I have a script that I had planned on using over and over and setting different properties in each of the various instances I'm using it, exactly like using a default vanilla script and changing the properties for your specific use of it. However, it just occurred to me that it wont work that may for me because I will be setting different quest stages at different times when I use the script. Here's the code:

Scriptname BalokDefaultTimerAliasSCRIPT extends ReferenceAlias  Location Property HelgenLocation AutoQuest Property BalokQuestToStop  AutoQuest Property BalokHelgen01  AutoEvent OnLocationChange(Location akOldLoc, Location akNewLoc)		if akNewLoc != HelgenLocation				BalokHelgen01.SetCurrentStageID(86)				Debug.Notification("Stage XX has been set")				BalokQuestToStop.Stop()			   Debug.Notification("Timer Quest Has Stopped")		endIfendEvent

What would be awesome would be if I could set some sort of property for the setCurrentStage line that I could define differently each time I use this script. If not, I'll have to just use different scripts and change the quest stage in each of the scripts as I need them. But if I could use this one script and change it on each instance it would be great. There's probably something obvious I missed, so sorry if this is a noobish question.

You can define your properties to be generic names
This is just a quick example
you can see its identical to your script except for the names and the addition of Int Property.

Now, you can set the properties and stage to whatever you need it to be. Having said that you could set the properties in your original script to whatever you wanted anyway.

Those are a mix of generic and specific. The location is an actual location that won't change. The BalokHelgen01 is the name of my main quest. I used it so it would auto fill. The quest to stop is one that will change, so yeah, I know about the names. However, the Int property is what I was missing. Thank you! I knew it was something simple i was missing, lol.