well this is tough. im assuming you're making a game.
what you can do is attempt to recall a variable at the beginning of the program and match it's value to what the program assigned it
Using A as our variable and the number 5 as our checking value:
(beginning of code)
If A=5
Then
(your code for it has been used)
else
(first time running the program)
end
since these variables are constantly changing, it would be safer to use less used variables such as GDB and Matrices and such. But since calling a GDB or a Matrix (im not so sure about the matrix) that isnt defined would produce an error, use a list. the command SetUpEditor, when given an argument, recalls a list if it exists and unarchives, or if it doesnt exist, it will create it with a size of zero. so we use a custom list that we know will be used later in the game, such as ∟SAVE.
SetUpEditor SAVE
if Not(Dim(∟SAVE
then
(the program has not been used before)
else
(the program has been used before)
