Random ideas
Here's a bunch of things I have written down about my game with Stickies (they're floating on my desktop)
Warning, very "raw" text :]
Should units contain a function which generates a data-list of the unit? Or should there be a pre-set class which displays a unit data sheet and it would just be passed a unit as a reference? Probably the latter is better
Units could kind of have some interfaces like IArtillery/IRanged, ITransport and INaval or something? Maybe not Naval...do it with movementpenalties instead.
note: MovementPenalties is a bunch of values in the game used to determine whether unit can move over a certain terrain and if it costs more than normal
Anyway, interfaces would allow some kind of implementation
Another way would be to implement this all into the unit class itself, which would allow for a versatile XML-definition for them. To allow versatile definition but separate functionality, separate classes would be needed instead of Interfaces, eg. ArtilleryUnit, TransportUnit
With interfaces, however, you could have a transport unit which would also be artillery... =)
Optimizing idea for Tile-rendering
- Use one tile for a certain type of tile
- Move the single tile around with matrices
- eg mountain tile, grass tile and blah blah... then it gets moved around
Currently every tile is different - 14x14 map -> 196 tiles... and there are like 4 or so different kinds. I could just store a List
1 Comments:
Really amazing! Useful information. All the best.
»
By Anonymous, at 5:09 AM
Post a Comment
<< Home