I was trying to convert my hashtables into table

[Pinzu]

            set ta[unitTypeId].boolean[0] = true        
            set ta[unitTypeId].integer[1] = this
            call SaveBoolean(udg_hash, unitTypeId, 0, true)
            call SaveInteger(udg_hash, unitTypeId, 1, this)

But unitTypeId is > 8112

 

[PurgeandFire]

I don't understand the question.

The [] operators are overwritten, so it isn't actually using an array. So it doesn't matter if the index is > 8191.

 

[Pinzu]

I don't understand the question.

The [] operators are overwritten, so it isn't actually using an array. So it doesn't matter if the index is > 8191.

I got some error messages complaining about the array size in game. "IndexError: Tried to get key 17016700775 from outside TableArray bounds: 8192"

 

[PurgeandFire]

Oh yeah. It isn't a 1:1 correspondence with the hashtable function. The whole philosophy of Table revolves mostly around the idea of using a struct as the storage for a multitude of data.

Naïve hashtable usage involves long lists of data being stored:

call SaveBoolean(hash, id, 0, true)
call SaveUnit(hash, id, 1, caster)
call SaveUnit(hash, id, 2, target)

Table usage revolves around storing the struct and letting that do everything for you:

struct Data
    static Table storage = 0

    unit caster
    unit target
    boolean something
    
    private static method onInit takes nothing returns nothing
        set storage = Table.create()
    endmethod
endstruct

// ... some code
local Data d = Data.create()
set storage[id] = d

That is just a random example. The main concern is the line: set storage[id] = d. Rather than storing all data individually in the hashtable, you simply store the struct. Later on, you can load the struct from the same ID and then grab whatever data you want. In a sense, you can picture structs as "packing" the data into a box.