They may not be the props used, but not having them in the template doesn't really rule out the posibility. Here's how I think its working...
Client reads the template and creates an instance of the window in its workspace (_HUD) at the default "Location" established by the template. It then checks if the window is set to UserMovable. If true, it checks the character.ini for a saved PackLocProp and moves the window. If false, it recalculates the PackLocProp.
Once in game, the client's OnMove handler sets Location and recalcs the PackLocProp. OnSave it again checks for UserMoveable. If true it saves the PackLocProp. Notice how this doesn't depend on the template having a PackLocProp.
If my guess is correct, the problem stems from not recalcing the PackLocProp from script. Even if the window is set to userMoveable, the last drag location is saved and not a subsiquent script move. Easy enough to test this using a text field populated with the PackLocProp value of a window with some buttons to move the window via script. If the Prop changes with a script move, these aren't the properties being saved. If it doesn't change, there's a good chance they are what's dumped to character.ini.
|