This is the mail archive of the xconq7@sources.redhat.com mailing list for the Xconq project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Just a caution: This is a game. It's supposed to be fun. Before adding any new complication, I think it's important to ask "Will this make the game more fun?" There isn't only one right answer, since the answer depends on who's answering, and on the context of the particular game in which the feature will be used. But I think the question should be asked.
That's one reason I said in one of my other messages that I think the GIS/XConq translation process will need a lot of customization per map; really, what it needs is customization *per game*. Some games will want some of the data to be really detailed; others will want less of the data and less detail in it. I think that in all cases the game's needs have to come first, and they'll shape how the data is treated.
I have similar reservations about Cooper's plan to make every hex its own
unique terrain type. I can see doing that as a work-around in order to
give every hex its own unique picture, but even that seems like a lot of
work and I think it would be a very special game that actually needed it. It would be nice to instead do something like the recent "specify a
picture for an individual unit" patch to allow specification of a picture
for an individual hex, while leaving the hexes grouped into just a few
terrain types.
Clouds and unit altitudes sure
seem to be so cumbersome in the current interfaces as to be almost
unusable (if, in fact, they are implemented at all).
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |