ScopeAlways objects are created in reverse order on the client?

As a relatively new Torque-r, I'm kind of excited to reach the point where I'm writing some NetObject-derived classes of my own in C++. (pauses to feel the power rush...)

I'm seeing something strange though. Objects marked 'ScopeAlways' are getting created in reverse order on the client, as they are on the server. I'm seeing this happen for both my classes, and for Torque's own ScopeAlways classes, like TerrainBlock & WaterBlock. (just by watching in the debugger)

I would think that ScopeAlways objects should be created in the same order on the client as on the server. Otherwise, if your objects have order dependencies (as mine do), you're in trouble.

I found this related thread where Mark Frohnmayer said ScopeAlways objects are created in the same order both places, so it sounds like that's the way it should be, but that's not what I'm seeing in Torque 1.3.

Can anyone shed light on this? Is reverse-order creation an oversight, or by design? I'd like to try to modify Torque to do normal-order creation.

thanks

edit: typo