Aphrodite and newt: I don't think you guys get the issue:
He is accessing properties of an object that exists, but has no instances at the time of the referencing.
think of it like this:
- <There are zero balls>
- Make all balls be blue
- Create a ball
- Ball unexpectedly comes out white
I don't consider this a "bug" per se, but Ashley might want to do something about this. Either make it so that you can write defaults, or make construct give an error if the object you're writing to has no instances (I think this last approach would be very hard to implement).
For a situation like this it would be nice if the debugger could provide you with a list of warnings when a situation like this arose. For example "Warning: this operation has no object instance". However as Fimbul said, I'm not sure how you'd do it.
As Ashley said, the behaviour is not surprising, but it is hard to debug when it accidently arises.
PS: didn't know about the physics object behaviour.
I don't think changing the defaults is a good idea