[Trigger] Checking inventory for multiple items at once

[Ardenian]

Hello,

I would like to receive an answer to the following question, please:

1. How can I define a general index, checking every index ?
Example:

• (Item-type of (Item carried by GDD_DamageSource in slot TempInteger[0])) Equal Orb[1]

(Item-type of (Item carried by GDD_DamageSource in slot TempInteger[0])) Equal Orb[1]

With a loop I can check every item slot, but how can I check it for every indexed item Orb[EVERY] ?

One workaround would be to create a 'Any'-Condition and add every indexed item and add a variable that is set to the index of the item that is actually hold, but how do I get the index ?

Would this work if the GDD_DamageSource has multiple Orb[INDEX] ?
So the trigger runs for every item hold of type Orb[INDEX] ?

 

[Flux]

You can use Hashtable saving the index of the array with key being the item-type or handle id of the orb item instead of loopingthrough each index thus, time complexity is O(1)

 

[Ardenian]

Is there a way to avoid hash tables ? Never bothered to learn how to use them, believe me, I tried, but there were always easier ways.

Could you show me the trigger, I guess it is a very simple one, please ?

 

[Flux]

Ok but can you re-phrase your problem, I did not fully understand it but from what I understand, you want to detect if certain item is stored in the Orb[] array.

 

[Ardenian]

Yes, I have 6 different items, stored in Orb[]. Now, I have a trigger checking whether a unit holds an item of type Orb[].

The problem is, I can only check for Orb[1] or for Orb[2] and so on, so I have 6 triggers for every indexed item.

 

[IcemanBo]

Loop for int I from 1-6
---- Loop for int K from 1-6
---- If Unit has item of type Orb[K] in Slot then
-------- Do Actions --------

Something like this, if I understood correctly?

 

[Ardenian]

Oh, yes, that's it, thank you. I am ashamed I myself didn't think of a double loop..

Is it recommended to use this method or hashtables ?

 

[Flux]

Iceman's suggestion is correct, it will allow you to get the index of the array and the slot number
Use that instead of hash (since it is easier) because you only have 6 index in the orb array but if the index of the orb array can increase a lot, a hashtable is recommended.

 

[Ardenian]

Alright, thank you!

 

[IcemanBo]

Oh cool, you're welcome!

 

[Maker]

You should really learn how to use hashtables. With arrays, the number of loops (and thus function calls) increases linearly with the amount of different types of orbs. With hashtables, the amount of function calls is constant and always less than by using arrays.

 

[Flux]

^ I was expecting that