from a student a request for guidance ..

from various scifi novels ops has aggregated a science fiction future to model as a game or 'simulation'.

in this alternate faster than light transits are a little less convenient than ones normal star wars, star trek or battlestar galactica variants.

In our present design every stellar system keeps a record of all insystem assets. to 'move' from a to b involves removing assets from a stellar systems records and adding them to the destinations systems records in some future turn.

while a spine or complex is subject to the 'rules' of FTL interstellar transit that asset is effectively 'frozen' and can neithr react to real space demands nor engage in normal activity. Think the sleepers in 2001 or aliens.

So it would seem to our poor addld wits that while asleep in transit these concrete instantiations cannot allow anything to call their methods ? How does one put an object to sleep ? Ops is toying with doing an 'intransit' exception ?

Comments and/or suggestions ?

 Or stick the reference into an 'inTransit' object that has a record of where the asset has come from, where its going, and what time its going to get there at, and stick the 'insTransit' object into a 'TransitBuffer' thats polled once a turn to see if you have to pop anything out and place the contained reference into the destiniation system assetlist. I reckon thats probably the -simplest- way to do it ...

D.