Homing Missle v1.1

[Moderator]

12:17, 29th Dec 2009
TriggerHappy:

The coding was fine and all, but in the demo map triggers why did you convert them to Jass without making any modifications?

 

[Deuterium]

Seems well done! Nice idea and creative...
Use comments in the triggers so that you can read it easier when you try to update, and so that we users dont have to fully read it to understand what's going on, but go through the comments. At least use the as dividers.
(look at the spell in my signature and you'll understand what I mean).

 

[HaniBon]

This is really good +rep

 

[kroasana]

its hard to read :S but i like the spell keep it up

 

[Deuterium]

As I said, he just needs some Comments...

 

[Septimus]

I don't understand why people still continue to make GUI spells despite the new patch.

 

[Rmx]

I don't understand why people still continue to make GUI spells despite the new patch.

Hashtable have the same importance as indexing they are some how EQUAL ..

If indexing gets recycled it's even better and = hashtable ..

So it doesn't matter if they did indexing or hashtable

 

[Deuterium]

+ Indexing is faster than hashtables in a way and it's not wrong to use indexing... and for those who know indexing it's way too easy.

 

[Rmx]

+ Indexing is faster than hashtables in a way and it's not wrong to use indexing... and for those who know indexing it's way too easy.

Truth is spoken +Rep ^^

Edit : Damn must spread some

 

[Kingz]

Hashtables won't use arrays like indexes and therefore there won't be a possibility to go exceed the max array number.
At that point and the fact it will drasticaly change the look of GUI spells you should know that it is much better than indexing.

 

[Rmx]

Hashtables won't use arrays like indexes and therefore there won't be a possibility to go exceed the max array number.
At that point and the fact it will drasticaly change the look of GUI spells you should know that it is much better than indexing.

And recycling the indexes won't have a chance to exceed the max array number either :O

 

[Deuterium]

off-topic @ Kingz:
No one here is saying that hashTables shouldn't be used. But I mean, if I don't need the arrays to loop through them, using Indexing is as fine as using hashTables.
What's more, Indexing is slightly faster - so I've heard - but who cares about some picoseconds?
And we know how to Index, so it only takes us a minute.
For those who don't, well hashTables are more convenient.

 

[baassee]

wrong topic to argue about hashtables and indexings ... still I have to join this fight for sure!

indexings = faster

dunno if this is true but ive heard that hashtables takes less space then arrays ... thought its like a few bytes

 

[hell gate]

Seems well done! Nice idea and creative...
Use comments in the triggers so that you can read it easier when you try to update, and so that we users dont have to fully read it to understand what's going on, but go through the comments. At least use the as dividers.
(look at the spell in my signature and you'll understand what I mean).

ooop. now i know what i forgott

will add it soon

 

[kms333]

ummmm isent there an option to add homing to a missle?

 

[Kingz]

Hmm how to put this...

Arrays won't be used anymore cause arrays are generaly slower than Hashtables.

Still indexing is fine if it contains index recycling

 

[S.W.I.N.E]

triggers please =/

 

[Itachi009]

my benchmark tests showed that using indexing is 2x faster than hashtables, but hashtables are 2x better because:
1) you cant reach the max index
2) hundreds of globals will take A LOT of memory and you simply cant remove them, just recycle

 

[baassee]

1. Why should you reach max index.
2. Why should you remove them when you can reuse them (recycle).

 

[Thepriest1750]

thanks alot 5/5!

 

[DEE-BOO]

This isn't 100%

I find that when I launch multiple missiles, some of them will not detect and/or follow a target, instead they will just keep travelling forward, ignoring any enemies in range. I think it has something to do with the indexing.

I should mention that I modified it so that:

• the missiles are slower and have increases turning rate.
• the missiles won't expire when reaching max range. (temporary testing)
• decreased impact range.
• the missiles will forget and try to look for a new target, only if the first target was too fast and escapes the pinning range.

I might have modified something to cause this issue, but I doubt it.
I added control over a footman for testing purposes. It will follow the steam tank's right click and will teleport when the steam tank issues a move order.

EDIT: I found the problem.

• Set HM_TempGroup = (Units within HM_PinningDistance[HM_LoopIndex[3]] of HM_LeakPoint[1] matching ((((Matching unit) is A flying unit) Equal to False) and ((((Matching unit) is Mechanical) Equal to False) and (((((Matching unit) is alive) Equal to True) and (((Matching unit) is

It's suppose to be HM_LeakPoint[0] not [1].