Some issues with the way Adrift currently handles properties. In some cases Adrift seems to evaluate functions too late, resulting in the following scenarios, and possibly others:
- If you use an '%object%' reference in the 'PropertyValue' function and then store the result in a property. When you refer to the property later, It fails to output anything with a cannot find '%object1%' error.
- I set up a task that refers to an array index using a variable and stores the result in a property. It then modifies said variable and reuses it to refer to the same array and store the result in a second property. However, the result of the second reference appears in both properties.
Bugs with properties
