What does the hashtables do?

[TKF]

The hashtables was added in the 1.24 patch. It's a new thing for me and I don't know what it really does.


But what does it do and what is it good for? In which situation is it useful to use?




Rep+ for the best explanation and answers.

 

[Azul]

I think its like a saving and loading trigger as what ive seen since most of it says that

 

[Tau Empire]

The best way to describe Harshtables?

Glue, that's it. You place 2 interger or whatever at start so when it's loaded, you load the harshtable, say I need a 3rd ressource by mining oil or whatever, you create 1 harshtable for the ability and the other for the region it enters. You stick both of them together to make 1 trigger work.

 

[TKF]

I read that useing Hashtables removes backward compatibility. What does that mean?

Are there disadvantages of using hashtables?

 

[Cheezeman]

They save anything under 2 integers. Like, if you save Footman under 1 and 2, you can load it by typing Load Unit 1 and 2 or whatever the GUI command is.
It's like a two dimensional array.

If you're a GUI user I'd say that you should use them. Sure, everything has disadvantages but comparing hashtable's to the disadvantages of other GUI things, they're nothing.
(Short said no, there are none)

 

[TKF]

Sry I'm not skilled using triggers. I don't know what I'm need them for?.... I don't get a grasp of it's usufulness...


I kinda using integers and reals covering mostly everything....

 

[Dr Super Good]

Hashtables store values and act like a 2D array as far as you interface with them. Further more their indexes have no bounds and can take any integer (32 bit two's compliment). As far as you the user goes, this is all you need to know.

They actually work by what their name says, they use hash related systems. This however is purly for explaining how they store data so efficently so really is not needed to use them.

 

[takakenji]

hashtables allow you to save/load

 

[DoOs_101]

Sry I'm not skilled using triggers. I don't know what I'm need them for?.... I don't get a grasp of it's usufulness...


I kinda using integers and reals covering mostly everything....

What you need it for?

Instead of creating variables to store what unit a Footman is attacking, hashtable allows you to store that attacked unit to a table that you initialized and created beforehand.

Lets say Bob attacks Ralle.

I want Bob to have an integer ID of lets say 1.

I also want any attacked unit to be represented as 2.

So I save Ralle to a table with a parent key 1 and a child key 2.

Now, I wan't to refer to Ralle because I wan't him to be turned into a sheep everytime bob attacks. So instead of creating a global variable for Ralle, all I have to do is simply Load a unit from the table with parent key 1 and 2.

Walah!

To be more efficient, use

GetHandleId() to take the integer representation of any Object instead of assigning them random integers...

Also use StringHash if you want to convert a string to an integer. This helps to identify the child key using a string instead of an integer. Lets say instead of putting 2 for child key, you put "attacked unit" and converted it to an integer using StringHash.

 

[Dr Super Good]

hashtables allow you to save/load

Um, too vague and interpreted to be an incorrect explinantion.

Hahstables can store and retreve values like a limatless 2D array, once the games ends their contence is lost permantly.

 

[f0rsAk3n]

Read This mate. Gives you a complete understanding of hashtables and its functions within WE.

 

[DoOs_101]

Um, too vague and interpreted to be an incorrect explinantion.

Hahstables can store and retreve values like a limatless 2D array, once the games ends their contence is lost permantly.

What I don't get is this...

All handle types share the same key namespace. For instance, if you call SavePlayerHandle followed by SaveUnitHandle, with the same keys, then the unit handle will overwrite the player handle. Even though the handle functions share the same key space, The SaveXHandle and LoadXHandle functions are type safe. For instance, calling SavePlayerHandle followed by local unit u = LoadUnitHandle will result with u initialized to null.

Source:http://forums.battle.net/thread.html?topicId=17730193178

Can you explain?

 

[aznricepuff]

If you use the same hashtable:

function foo takes unit u, player p returns nothing
    local hashtable t = InitHashtable()
    local unit u
    local player p
    call SaveUnitHandle(t, 1, 1, u)
    call SavePlayerHandle(t, 1, 1, p) // using the same keys (1, 1) here overwrites the saved unit from the previous line even though we are now saving a player instead of another unit. This will also be true for ALL handle types, so if I used the same keys and saved a special effect, the unit still gets overwritten.
    set u = LoadUnitHandle(t, 1, 1) // u is set to null because the saved unit was overwritten
    set p = LoadPlayerHandle(t, 1, 1) // works correctly
endfunction

 

[DoOs_101]

If you use the same hashtable:

function foo takes unit u, player p returns nothing
    local hashtable t = InitHashtable()
    local unit u
    local player p
    call SaveUnitHandle(t, 1, 1, u)
    call SavePlayerHandle(t, 1, 1, p) // using the same keys (1, 1) here overwrites the saved unit from the previous line even though we are now saving a player instead of another unit. This will also be true for ALL handle types, so if I used the same keys and saved a special effect, the unit still gets overwritten.
    set u = LoadUnitHandle(t, 1, 1) // u is set to null because the saved unit was overwritten
    set p = LoadPlayerHandle(t, 1, 1) // works correctly
endfunction

Ic, thanks!

 

[TKF]

Well, thanks for providing so much angles. I think I understand know....