On Wed, 04 Jun 2008, Dustin White wrote: > I've been poking around with how ships and fleets are implemented in > different rulesets (on tpserver-cpp) and I just wanted to make sure I'm > understanding all of it correctly... > > A "ship" is essentially just a collection of components each of which is a > collection of properties, correct?
In Minisec (and rfts too, iirc) a fleet is composed of a number of ships of a given design. The design is the collection of components and properties. The fleet has some additional properties. > Orders are always given to a fleet not a single ship, correct? No necessarily. > Would the best way to have a single ship execute an order be to have it in > a fleet by itself? > > Thanks! > -Dustin (nuleren) Just to clear things up. The current clients expect the objects to have a particular format in the TP03 Object Frame on the network, basically from Minisec: Universe, Galaxy, Star System, Planet and Fleet. When everything supports TP04, there is no reason not to have different object types, such as constellation, star, ship, etc. Or vary the properties. If you want to give orders to individual ships, I suggest you make a Ship object type, but in the TP03 compatibility code, make it look like a fleet with only one ship. Hope this helps Later Lee Begg
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
