Bad, put a constant for it and say do not modify unless you know what you are doing.
Some people might want to change it, for example I reserve Player(15) for hero selection system.
And using constant collision size kind of makes this whole lot less useful.
Very strange thing, it really is an PUI error.
It was introduced with 5.2, version 5.1 works fine.
I have reattached 5.1 to first post, use that until I release 5.3
Thanks for finding this Joker(Div)
EDIT:
fixed, version 5.3 is out.
In case someone cares the problem was that I forgot...
Tell me how am I goint to reproduce your error from that script?
Please make me a demo map that demonstrates the bug.
Are you using UnitUserData directly somewhere?
Ye you are talking about imaginary world in your head.
Because what you say must be true and the fact that me and Builder Bob have tested PUI extensively and that PUI had been used in all kinds of maps for almost 4 years without any errors/performance issues does not really matter.
It also...
It frees indexes after 5-10 seconds, big deal.
PUI was the first indexing system out there, and by my logic it was and still is the best indexing system ever made.
A lot of really good map makers seems to agree with me on that one too.
I really don't care about your test maps because I have...
No, and I don't plan to.
I believe in "don't fix if it is not broken" phylosophy.
PUI works as it should and it works well, I have no intention of wasting my time on maybe-improvements.
2-3 hours of my life are simply more expensive than 2-3 nanoseconds of PUI efficiency.
Go read that...
You are welcome.
(not being malicious)
Maybe you need to actually test the things you write?
Compiling the code in your head does not work sometimes. :)
Oh sorry did not look past your first code post because it was silly. (IMHO)
To reply to the second one:
You did not do any optimization there.
Optimization is by definition improving of some aspect of a system without modifying the algorithm.
You changed the algorithm so you would "save...
That is because you want to reinvent the wheel.
Yes, yes(the point of using systems), yes.
Maybe I just like the warm and couzy feeling inside I get from knowing at exactly what time the unit index started decaying.
Do yourself (and myself) a favor and read this.
Especially the part...
Bonus_life is not really an array, it is a unit property.
(units are used as indexes directly, there are no integers)
You don't need to understand jass to use this.
Just read the comments is the triggers carefully, they explain it all.