• Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
  • The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!
  • ✅ The POLL for Hive's Texturing Contest #34 is OPEN! Vote for the TOP 3 SKINS! 🔗Click here to cast your vote!
  • ✅ The POLL for Hive's Techtree Contest #20 is OPEN! Vote for the TOP 3 FACTIONS! 🔗Click here to cast your vote!

Hashtable vs Hashtables

Status
Not open for further replies.
Maybe around 200-500 handles, only then we need a new Hashtable (this is just a rough estimation tho).

That is very few, I think. A hashtable can store that without any problems.

I have around 5 or 6 hashtables in my map, though I think there is still at least 1 that can be removed in favour of an array using unit indexes.
 
Hashtables are fine to use only one for everything in your map or have 255 that all work cooperatively to store all the data you need.

I presonally think you shouldnt care that much.
But as long as you do not need a hashtable, you should use normal arrays.

There are a total of more than one trillion slots in hashtables so you can store more data than even your Hard Drive supports.
I am talking about 16 Zebibytes of data... (16,384 Exabytes or 16,777,216 Petabytes or 17,179,869,184 Terabytes)
That not even using handles but only primitive types.

If you only need one row of a hashtable, you can use Table instead.
But if you only need one row, you can probably do it without a hashtable.
 
Last edited:
Status
Not open for further replies.
Back
Top