actually, it wasn't 1+2+4
it was
[Class Flag #]-[Highest Class flag # that can be taken out of it]-[Next Highest Class Flag #, etc]
as that would be the most efficient way of coding it minus having all the #s as a seperate entity. (like having each class be a number, and then class combinations be others, but that would be more than a few objects to make)
The binary idea could only have 1 flaw when you have like 12 classes, and if your binary conversion drops leading zeros. e.g. 0000000111 becoming 111 instead (as it wouldn't negate the leading classes, and to do otherwise would be more coding).
I dunno, I just think it might be easier to code it the way I was mentioning, since that could easily cover any more added classes they might want to throw into in the future (ala the Froglock/Vah Shir races for ecample since this could apply tho races as well with a slight modification of just labells and db calls)(just add a new first number to subtract with a class flag). Though I see no plans for such in the future, it could be easier in the long run.
__________________
The downside of being better than everyone else, is that people have a tendancy to think you're pretentious.
|
Threaded Mode
