[Trigger] Question: About Loading in Hashtables

[FUJI]

Hello,

I have a question and I want to know the differences of this procedure =,= When saving a value to the hashtable.. Why other users doing like this?

Loading without Setting it

• Just Example
  • Events
    • Time - Every 0.03 seconds of game time
  • Conditions
  • Actions
    • Unit Group - Pick every unit in KU_Group and do (Actions)
      • Loop - Actions
        • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
          • If - Conditions
            • (Load 1 of KU_Key from KnockUp_Hashtable) Greater than 0.00
          • Then - Actions
          • Else - Actions

And the others are using this: Loading with Setting it

• Just Example
  • Events
    • Time - Every 0.03 seconds of game time
  • Conditions
  • Actions
    • Unit Group - Pick every unit in KU_Group and do (Actions)
      • Loop - Actions
        • Set KU_Time = (Load 1 of KU_Key from KnockUp_Hashtable)
        • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
          • If - Conditions
            • KU_Time Greater than 0.00
          • Then - Action
          • Else - Actions

I'm desperately want to know what they're differences XD... Is it brokening MUI (Multi-Unit Instanceabilty) in what procedure... Is it for faster coding???? or Is it for efficiency???? Elaborate Pls...

 

[Rheiko]

the difference is you're not using your stored variable..
and it's make your code less efficience..

 

[Ofel]

It's for faster...Loading a value saved in hashtable is slow...that's all i can tell

 

[FUJI]

the difference is you're not using your stored variable..
and it's make your code less efficience..

Usually I'm beginning with setting it the stored variables xD but I'm confused to others that they're not storing their stored variables to the trigger and they're just loading the datas to the function not to a variable.

It's for faster...Loading a value saved in hashtable is slow...that's all i can tell

So It's faster as you said but is it will affect the MUI of the Spell or the efficiency ?

Off - Topic : 100 posts (just a newbie or noob)

 

[Rheiko]

MUI, no.. efficiency, yes

Usually I'm beginning with setting it the stored variables xD but I'm confused to others that they're not storing their stored variables to the trigger and they're just loading the datas to the function not to a variable.

which one are your referring? the first trigger or the second one?

 

[FUJI]

MUI, no.. efficiency, yes



which one are your referring? the first trigger or the second one?

2nd one

 

[Rheiko]

because they're setting the variable first, it much faster than the first trigger..
it's like

1st trigger:
you have an apple in the cast trigger
then in the loop trigger, you need to search for it (because you forgot where it is) first then eat it (because you're not save that apple)

2nd trigger:
you have an apple in the cast trigger
then in the loop trigger, you save that apple (you're remember where you put the apple)
you don't need to search for it, you can just eat it.. (because you know where it is)

now, if you see from both of them which one is faster?
the 2nd one of course

 

[FUJI]

because they're setting the variable first, it much faster than the first trigger..
it's like

1st trigger:
you have an apple in the cast trigger
then in the loop trigger, you need to search for it (because you forgot where it is) first then eat it (because you're not save that apple)

2nd trigger:
you have an apple in the cast trigger
then in the loop trigger, you save that apple (you're remember where you put the apple)
you don't need to search for it, you can just eat it.. (because you know where it is)

now, if you see from both of them which one is faster?
the 2nd one of course

Nice +rep for your gift then eat it .

 

[Rheiko]

yeah, you know what..
i wanna eat an apple right now, but there is no apples at my home!
i think i'll go to buy it

 

[deathismyfriend]

the difference is you're not using your stored variable..
and it's make your code less efficience..

This is not true at all.

@TO
The reason that people store things into temp variables is because hashtable loads are very slow. If you use the hashtable loaded value twice or more it should be stored into a temp variable and the temp variable should be used in your triggers.

 

[Rheiko]

why not

 

[deathismyfriend]

Look at the trigger above he is using the stored variable. It is more efficient to store loaded hashtable values into a temp variable.

 

[Rheiko]

at the first trigger, he didn't store it to a variable

 

[deathismyfriend]

at the first trigger, he didn't store it to a variable

That is because it was only used once. Read what i said closer.

 

[Rheiko]

hm, okay..

 

[FUJI]

Anyway I did storing the loaded value in the variables and I'm doing the 2nd trigger as ALWAYS.. not the 1st trigger anyway I think I'll stick to the store loadded value in the variables as deathismyfriend said.

 

[Rheiko]

well, good then

apples :3