[General] One event to many different results

[sethmachine]

Hi,

Suppose I have a trigger that checks when a unit picks up an item, as I need to make sure I can allow that unit to hold said item.

But say also picking up some items can start a quest for a player.

These are two entirely different results from the same event. Do I just make one set of if statements that iterate over all such possibilities? I suppose I can be clever and assign certain point values to items that start quests, but it still has to look like this:

Player picks up some item

If item is an equippable item
  If player is strong enough to use item
    do nothing
  else unequip item, display message "Not ready to use item"
elseif item is a quest starting item
  if item is == QuestItemA
    start QuestA
  if item is == QuestItemB
    start QuestB
...

 

[deathismyfriend]

if statements are the easiest way to go. You can use a hashtable for this also but that requires storing everything in the hashtable at map init. There are other ways but it would be hard on what to suggest without more of an explanation on what you are trying to do / not do.

 

[sethmachine]

Well I need to control which units pick up what items.

But picking up items is also a way to start a quest, or perhaps advance one. E.g. a character comes across a dusty old tome (think Skyrim where you read a book you start a quest). Or character finds the item their quest needs.

These are all the same event, but different outcomes. It's a bit annoying to have to put it all into a single giant set of conditions...

 

[deathismyfriend]

I would think that the best way is an ITE.

 

[Maker]

You could use a hashtable to initialize data.

For examle

set ht = InitHashtable()
call SaveBoolean(ht, 'Hpal', 0, true) // Hpal = paladin

Unit acquires an item
if LoadBoolean(ht, GetUnitTypeId(GetTriggerUnit()), 0) then
--can equip
else
--can not equip
endif

Likewise, you can initialize if an item is a quest item or not.