This is bad.
If you look at the variable "Index" on the materials, you'll notice it says the number can't collide with another number.
Meaning... We're possibly limited to 256 materials, meaning any mods released with the same index go boom.
BAD.

Well, for the time being, you could use the Wiki to list when you've used an index?

Okay, I've learned it can be over 256 (phew)
Still, we can't have the same materials any more.

Just use insanely high and random numbers.

Ok?

Aaah! don't use anything over 255 or under 0... it's cause trouble. We'll figure out some way to keep mods from introducing conflicting indices of materials. Stay tuned

I R crashing =[, something about material 91?

Once again the great Data decendth apon his forums to qwell a disquieting developement amongst the mod community.

We shall drink to his good health!

Huzzah!

Alechs, i tmeans one of your mods are using a material which ends up being index 91... it gets copied to the terrain as that index and then anyhting colliding with it will freak out and give that error, since there isn't any material definied with index 91. We'll talk about this in a post soon

- D

ok... thanks... hmm can't remember using any mods though... . Maybe I did.

Data, this might be really hard to implement (or not with your greatness) but i have an idea...

When the loader goes through materials.ini, it looks for duplicate indexes, and the reassigns them to the next open slot. Possible?
Or it could just be a standalone appliacation that does the same, names: CCCC (Cortex Command Conflict Crusher)

Are these reasonable suggestions, and what confuses me is what is the advantage of using the indexing???

Data could make it so each mod can have it's own material list or array or whatever he used to store them. Or at least a way to define new sets.

Perhaps use namespacing Data?

ohh. i think i understand.