Item restrictions (only 1 charged, 1 permanent, etc)

[NET-RUN]

EDIT: SOLVED (now if i can find that button to make it show as solved...)





I've searched the web and havent come to a conclusion yet about how to do this. Exactly what im trying to do is impliment a trigger that will restrict heros from having more than one permanent item, more than one charged item ect. I would rather have help from one more skilled than me help me on this issue instead of me spending days looking at the trigger list.

(Listing the triggers would help.)

 

[x3m]

Give the item's custom values..then just check whenever a hero gets a new one, if there is 2 then drop the last recived or something.

 

[NET-RUN]

This would help only if the involved items are precreated. The system I'm trying to get working is that if a hero picks up two permanent items it's drops the last gained. Your suggestion doesnt help.

Edit: Yes I tried your suggestion it didnt work.

 

[QueloR]

I don't get it, you wan't every hero to be able to only have one of a permanent item, one of a charged item and so on? If so x3m's idea should work just fine, just set all permanent abilitys to the same value and then check through triggers

 

[Equal]

I would say u could use JASS.
In addition i would use 'Kattanas Handle Vars'
The trick would be to create X vaules, where X is the number
of the different types of items u have. Lets say u have 10 diff types.
now u make whenever the item is given, no matter how, to a hero
and it is a PERMANENT;
Check if there is a vaule called PERMANENT and if NOT then
creating a vaule PERMANENT (as integer) and set it to 1.
Else, drop the item that was get last.
Additionaly u will need a trigger to check whenever u drop a Item
checking if its PERMANENT and if true then reducing the vaule to 0
or removing it.

But u said u are less known with triggers, so this is mb a to advanced
solution. MB ask someone to create such a system or wait until
somone that is better in GUI then me answers.

greets equal

 

[NET-RUN]

Equal throught that explination this might get solved, thanks.

EDIT: No need for any of the above I sorted out a system with an
'Item Class Comparrison' Condition. But everyone thx for the help, have some rep.