Simple Item Table System v1.00

[Moderator]

Approved

Suggested changes:

• Add drop chance
• Add support for more than one drop on death
• You don't need to set itemcount in setup, loop until array index == null
  Then store the last index that wasn't null
• No need to load all item types into an array in the death trigger. Use random(1, ItemCount) as a key

 

[defskull]

Reserved~

 

[gorillabull]

ok using a hashtable to store the different item drops is good but you dont need to save the dropping unit into an array, you can use some underused stat like food prodused to represent that unit, for example set footman's food produced to 1, peasant to 2 etc store the items in a hashtable then when a unit dies this will either create an item or be null depending on weather the food produced value of the unit is linked to items or not

 

[defskull]

for example set footman's food produced to 1, peasant to 2 etc

This may disturb the Object Editor's value, no ?
What if the map developer doesn't want Footman to produce any Food ?
I'm still doesn't understand your statement.

 

[Adiktuz]

I suggest not using food related things as most maps seem to use food in some way or another... And anyway, he already uses UnitTypeID which is unique for each unit type so why bother using other things that can potentially cause conflicts?

Also I don't see a part that saves a unit into an array... maybe you mistook the part that saves the Unit Type (GUI) into a temporary variable as saving units into an array?

As for the system, well its pretty nice and simple... not as much functions as my system but hey this is GUI... though like Maggy said, being able to process more than one drop per unit is a really good (and maybe needed) addition to this...