sprites: request to devs

[paradoxharbinger]

all im suggesting is that taking this sort of approach might save alot of space in a database, and since space = $ on the internets...

it probably would not be too difficult to extract the data we'd need to do it.

by all means, go ahead and talk to your friend, any extra incite in how we should proceed with this would be welcome

[paradoxharbinger]

well this went dead....

so i went ahead and started to design the dom unit db, i'll have some more on it in a bit

[Gandalf Parker]

Ummm I ended up with a file of them. Unfortunately now I dont remember how I got it and what the stipulations were. Let me bounce a note off of Kristoffer

[paradoxharbinger]

well, here's how i would lay out the db. common stats, those that all units, armor or weapons have in common, would be in thier respective tables (tbUnit, tbArmor, tbWeapon) though uncommon abilities, such as flaming or poison, would be in tbAbility and linked to through the various ability bridge tables. ultimately, each unit is linked to weapons, armor, sprites and miscellaneous abilities through various bridges so that units which have similar abilities need not have duplicate records of that ability, thus saving a lot of space.

i think i may work on incorporating this into the unit maker, but i haven't quite figured out how the databases work in c# yet.