Hello,
So I'm in the process of implementing order entry for galaxie[1]. One
thing I noticed for object selection is that is currently all or
nothing. That is an object parameter is currently all objects are
'valid' with no filter.
The problem is that too often the list of valid objects is a small
subset of this. Merge with fleet is obviously can only be merged with
other fleets. Similarly colonise can be only be on planets. Obviously
there is a second level of validity here.. but you really can't colonise
a star.
Work arounds are to use a list of valid objects, but then there is no
way for a client to know what it is[2], and if the list is all
objects... well that could be a long list (especially since it would be
sending the objects by name). A reference list could also be sent.. but
then again that would be a long list as well.
Hence I'd like to propose either a new order argument or a modification
to the current object argument to include:
* a list of
<Uint32> Valid Object Types
If the list is empty, any object can be selected.
This should be fairly short for most games. (ie Planets for a colonise
order), although an game that distinguishes between types of planets or
a race that can colonise suns may get two or thee).
Other solutions would be a bit field for object types, but that only
works for objects up to #32, which is a bit of a limitation.
Thoughts?
Regards,
nash
[1] Yes finally[3]
[2] So it can't easily allow you to select by clicking on a map for
instance.
[3] And, yes I'm close to finished.
_______________________________________________
tp-devel mailing list
[email protected]
http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
