Hashtables and MUI

[Element of Water]

Fair point, deuterium. A single unit will never be able to cast 8191 spells at the same time. Not even 10, probably.

EDIT: Just saw Roflcopter's post - hashtables are slower than indexing. Indexing is more than twice as fast, from what I've heard.

 

[PurplePoot]

It's pretty easy to fill up an array with 8191 indexes with a single spell in a few minutes if you mess up.

 

[Element of Water]

Yeah, but the point is you only index it if the same unit casts the spell more than once at the same time...

 

[PurplePoot]

That post earns a "What?" for not making sense.

PS. Where are you getting your hashtable information?

 

[Deuterium]

@ Element of Water:

Well one thing: the index is shared between all units casting the same spell, and I was saying that even if all are casting once a second it never fills up until more than two hours into the game

 

[PurplePoot]

You're assuming that each cast uses only one index--bad assumption.

 

[Element of Water]

Well I was trying to create a hashtable per unit every time it casted the spell so a spell is MUI and SUI (Same Unit Instanceable).

How would you create only 1 hashtable per spell??? Explain everything!

This was the original question about this whole indexing thing. He wants one unit be able to cast the spell more than once at the same time.

And I got my hashtable information from that first news thread about it I think. I think DSG said hashtables are at least two times slower than arrays.

 

[Deuterium]

each cast uses only one index

PP what do you exactly mean by that?

 

[PurplePoot]

What do you think I mean by that? A spell could use more than one index every time it's cast. I've had ones that use hundreds.

EoW, did he actually give any evidence, or did he just say they were?

 

[Element of Water]

He means you might have an array of missiles or something you need to move in one spell.

EDIT:

@Poot
I think he said the modulo thing takes a while, I dunno. Look in the thread.

 

[PurplePoot]

What?

 

[Kwah]

Seriously, What?

 

[Element of Water]

Look in the thread.

 

[PurplePoot]

We don't know what thread, nor what modulo has to do with hashtables.

 

[Element of Water]

I said, the first thread about 1.23b and the new natives. And don't hashtables use modulo formulae to reduce the values to within a reasonable range?

 

[PurplePoot]

No, but even if they did a native mod is quite fast.

 

[Deuterium]

It's not about the modula, it's a matter of looping... ask DSG he can clear things up.

 

[Rmx]

I only know that if you Recycle the indexes it will be much better.

Recycling indexes is very good and also i am 100% sure that Paladon system Recycles those indexes, but only when there is no active instance, and it isn't Dangerous at all.

Also if you are efficiency freak, you could recycle the indexes much faster way, the usual reducing indexes until it reaches 0 and turn off, diffrent than Paladon's sys.

And if you are SO Freakich in efficiency and you have a very LARGE map, then go use hashtables or purplepoot indexing kinda spell.

 

[Deuterium]

Well, let me do us all a favor, PurplePoot said that any well-done index system would be allowed, so why don't we stop arguing and let each user pick what he likes as long as the rules allow it?

 

[PurplePoot]

If you are "SO Freakich in efficiency" then you would "not" be using "GUI".

 

[Deuterium]

PP kicks ass

 

[Rmx]

If you are "SO Freakich in efficiency" then you would "not" be using "GUI".

I am not Freakich in Efficiency, i will use GUI and don't bother me again ...

 

[Deuterium]

off-topic @ Rmx:

don't bother me again ...

Rmx, why did you get offended? We're not talking about you, we're talking about what you said...

 

[Rmx]

Sorry lol, i was just mad about something else ^^

 

[Asgard_Ragna]

If you want it to be recycled right i guess the DIR system of Kingz works pretty fine and does it's work.

The tut is well done, but I don't think that I will use them very often.

 

[-Berz-]

Awesome, now I must geek this up

 

[Squiggy]

if you want it to be recycled right i guess the dir system of kingz works pretty fine and does it's work.

The tut is well done, but i don't think that i will use them very often.

dir?

 

[Roflcoptor]

Dynamic Index Recycling

EDIT:Fixed link.

Btw EoW, how could DIR be Dynamic Values Storage?

DIR is just an expansion to it i think

 

[Element of Water]

Dynamic Index Recycling

What a dodgy broken link... http://www."http.com//www.hiveworkshop.com/forums/trigger-gui-editor-tutorials-279/dynamic-values-storage-121558/???

It should be:

http://www.hiveworkshop.com/forums/trigger-gui-editor-tutorials-279/dynamic-values-storage-121558/

 

[aaron]

Easy to understand but in big triggers and complicated ones...

Hashtable will be extremely complicated, but some easy triggering and jumps slides ext..

Hashtable is F T W ( for the win ) ^^

Rmx u kidding me its so easy

 

[PurplePoot]

Rmx u kidding me its so easy

Easy to say about things you understand. I could say that (and mean it) about things that you would have no idea how to approach, let alone carry out.

 

[OnkelManfred]

damn useful! thanks man, +rep for sure ;-)

 

[ravery12]

Hashtables can have an infinite number of indices, however, which is more than you can say for vJass 2D arrays.

the hashtable has 2 indices, parent value and child value, so is a 2d array

unlimited yes but still a 2d array

There are some things which are quite hard to do with just structs, for example if you need a separate timer for each instance of the spell. These things are much easier to do with hashtables.

since strict is really a sophisticated indexing system.
you can put the timer in the struct and have a timer for each instance of the spell


the biggest advantage I see to hashtables is that you can use the unit handle as your index, thus eliminating the need to somehow keep track of your index

 

[Element of Water]

the hashtable has 2 indices, parent value and child value, so is a 2d array

unlimited yes but still a 2d array

I didn't say "a hashtable can have an unlimited number of dimensions", I said "a hashtable can have an unlimited amount of indices". Get your English right.

since strict is really a sophisticated indexing system.
you can put the timer in the struct and have a timer for each instance of the spell


the biggest advantage I see to hashtables is that you can use the unit handle as your index, thus eliminating the need to somehow keep track of your index

No, the struct is not a really sophisticated indexing system, and what I meant by what I said, is that you can easily use hashtables to attach structs to units, timers, etc.

 

[ravery12]

No, the struct is not a really sophisticated indexing system, and what I meant by what I said, is that you can easily use hashtables to attach structs to units, timers, etc.

It is an indexing system, make a struct in NewGen, then export the script to see what it is translated to.
you will see it is just an indexing system.

 

[Element of Water]

Yes, I know it's an indexing system. What I'm saying is, it's not a really sophisticated indexing system.

 

[l0git3c]

Wow, nice tutorial.

I learn something epic!

 

[Jirinal]

Awesome, i just created withih 5 minutes an "system" with that i can set the duration of a buff and call it whenever i want.
Now i can set the duration of a buff and even stack buffs and other awesome things, without even breaking a sweat. More awesome spells here i come.

 

[Diehard@Azeroth]

Hmm, interesting; though a personal question, even though i dont use UMSWE and such improved WE´s, i want to ask just what exactly are all the advantages does this have over UnitIds (GetUnitID etc)? Since you can store variables by attaching ids and recycling them by removing them and or replace them.

Thanks for your time.

 

[Dragonson]

So... if this does what i think it does... it can be used as a save system for orpg maps? O.ô

 

[ravery12]

Hmm, interesting; though a personal question, even though i dont use UMSWE and such improved WE´s, i want to ask just what exactly are all the advantages does this have over UnitIds (GetUnitID etc)? Since you can store variables by attaching ids and recycling them by removing them and or replace them.

Thanks for your time.

The major advantages of the hashtables are:

1) no limit on the index, arrays are limited to a max of 8190.

2) it's two dimensional

3) you can get the handle Id of most any object.

 

[Diehard@Azeroth]

Interesting, thank u very much, but does it really have no limit? because that may be the motive for me to use hashtables and dl umswe!

Thanks for ur time once again t.t

 

[ravery12]

Interesting, thank u very much, but does it really have no limit? because that may be the motive for me to use hashtables and dl umswe!

Thanks for ur time once again t.t

yes, the index is unlimited, so you can directly use a handle ID as your index.

HashTables functions are native code and included in the GUI .......... USMWE isn't required, nor NewGen

Just log in to B.net to get the autopatch to 1.24

 

[Diehard@Azeroth]

heh thanks bro.

 

[emilaxel]

Great tutorital I got all about hashtables now. It´s very usefull indeed.

I am going to use hashtables in my maps from now on.

 

[Dinah]

Great Tut but there is a memory leak in the sixth trigger:

• Unit - Move (Picked unit) instantly to ((Position of (Picked unit)) offset by KnockbackDistance towards KnockbackAngle degrees)

Should be:

• Set temp_point = (Position of (Picked unit)
• Unit - Move (Picked unit) instantly to temp_point offset by KnockbackDistance towards KnockbackAngle degrees)
• Custom script: call RemoveLocation (udg_temp_point)

 

[dansaDisco]

Yeah.. and he also wrote this under it:

As a final note, these triggers are merely examples. As you may or may have not noticed, the knockback trigger would require memory leak fixing since it leaks 25 locations each second for every unit that is being knocked backward. I intentionally left the triggers how they are so they would be easier to understand. Those who wish to use these kinds of triggers in their maps should make sure to fix any memory leaks that were not cleaned up in the examples.

 

[prophetboy]

all i can say is WOW this was easy with your tut!!! I played with it and I was able to create Healing and Damaging using 2 different hashtables.
please consider doing a whole series of tut using the hashtables for us beginners/learners

thanks

 

[Noobsmoke]

good work ... and thx for help

 

[Billy the Cat]

Warning: First off, in order for the code in this tutorial to work you must be using the beta 1.24 patch available on the Westfall server. This tutorial covers a new type introduced in the upcoming patch that is not currently available in the current patch (1.23).

You might want to adjust this now since it's old news