Jesus4Lyf

I'm making an item drop system similiar to Diablo 2's body loot. When a hero is knocked out in my rpg and his/her spirit is rejoined by a medium their body comes to them, so their items are left behind. In order to stop abuse by other players picking up, I have to register the owner.

Cool. You'll have to let me know how you go with that or something. Not sure exactly what you're trying to achieve, but it'll be interesting to see.

The right tool for the right job... We'll see if AIDS is it! Heh.

They are, I've already started coding a system using AIDS to document an item's owner.

Hey, no worries. Hope they're useful. I'd use the AIDS/KT2 one.

Thanks for the tips Jesus.

Yessir.

At least for a while.

Change that custom title to Creating more tavern. :O

Party, party!

Whee I finished my death system, and my party system.

As said previously, yes I'm a Christian. I don't have a Garena account (or rather at very least -never- ever use it if I do have one). Why wouldn't I have this name?

*Shrugs* All benchmarks are already in the KT2 thread. KT1 is a textmacro of struct/stack (global timer). KT2 is faster for one instance. That's all. And in knockbacks, usually you only have one instance. The speed advantage otherwise is like... 25% of nothing.

I forget the exact numbers. They're all in the KT2 thread. It's the most thoroughly benchmarked system I know of.

The real issue is what's nicer to code with and what improves readability and such.

And get Vex to unmute me on WC3C if you want it there.

Benchmark it and tell me how efficient can it be and I will use it.

Also it must go into wc3c library or the resource wouldn't get approved meaning you have to create another new account.

KT2 or a global timer is appropriate for a knockback. TimerUtils is not. It doesn't handle it correctly.

In some circumstances (imo most circumstances) KT2 will be more efficient than a global timer for a knockback system.

It doesn't seem appropriate.

One global timer for a knockback system is more efficient, tried to use TimerUtils but got rejected.

Perhaps not, sorry. It seemed appropriate.

Umm. If you have two knockbacks, they should be attached to KT2 not PUI.
In general you don't need to attach two instances of the same thing to one unit. They can be merged into one.

If you need more than one, it shouldn't be attached to the unit, probably.

I often find myself attaching multiple struct to things so even with that item stuff, it might break my item library.

Dude. That's genius. Lol.

You realise there's heaps of ways to store booleans like that? XD
But yea, all redundant now. Go back 6 years and tell everyone and make an alternate WC3 mapping reality. XD

The natives TriggerWaitOnSleeps and IsTriggerWaitOnSleeps. Use typecasted booleans, and they carry data happily. I won't use it, though.

Should share... lol

I found a rather interesting way to attach to a trigger with 100% stability with no O(n), or H2I. It still uses the return bug, though, so you wouldn't like it. That and Blizzard is fixing it.