• 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.

[Trigger] Hashtable Handle Question

Status
Not open for further replies.
Level 37
Joined
Mar 6, 2006
Messages
9,243
the only problem I see is the HT has an instance limit of 255, now if that 30 spells will be casted by 85 heroes at the same time(which is rare), then it will not work...

Uh...any source to this information? Doesn't sound right to me.

Triggers run one after the other, spells won't run at the same time. So how could there be a danger of exceeding this instance limit.

You can "only" have 255 hastables in a map, did you mean that?
 
Uh...any source to this information? Doesn't sound right to me.

Triggers run one after the other, spells won't run at the same time. So how could there be a danger of exceeding this instance limit.

You can "only" have 255 hastables in a map, did you mean that?

I said that coz I've encountered a problem with HT long ago, its not functioning correctly, I run multiple carrion swarns at 0.1 with a display timer then it didnt run anymore, IDK maybe I did something wrong or what...
 
You can have a maximum of 256 hashtables. (or 255, that's besides the point)

It is likely that you either:
- Ran into the limit of hashtables because you were creating one each time. (maybe by mistake)
- If not, you probably ran into the op limit.

In terms of storage per individual hashtable, it is enough to suit most people's needs. (one hashtable can easily be used for one map) You probably won't reach the limit unless you are doing something very wrong. ;)
 

Dr Super Good

Spell Reviewer
Level 64
Joined
Jan 18, 2005
Messages
27,259
Hashtables are meant to be shared between multiple systems. A map should have atmost 10, as some systems are most effective if left their own private hashtable (to avoid handling extra collisions).

The only reason hashtables are slower than variables is evaluating the parameters. Due to the interpreted nature of JASS the irony is that variables are a form of hashed structure as it is.
 
Status
Not open for further replies.
Top