[Shadows In Rain]

Originally Posted by ConnorMcLeod What is the advantage of making APIs if you use prethink to do that kind of stuff ???

What kind of logic you use? Different events, different responses.

[Arkshine]

You are not authorized to provide *.amxx unless you ask someone from the staff to do it for you.

[ConnorMcLeod]

Originally Posted by Shadows In Rain What kind of logic you use? Different events, different responses.

PreThink is not the right place at all to give weapons, even without a main api.

[Shadows In Rain]

Originally Posted by Arkshine You are not authorized to provide *.amxx unless you ask someone from the staff.

Ok, amxx's removed, archive updated.
Can you authorise me?

[Shadows In Rain]

Originally Posted by ConnorMcLeod PreThink is not the right place at all to give weapons, even without a main api.

Originally Posted by Shadows In Rain ... Roadmap / TODO: ... Perfomance optimisation. ...

Right?

[ConnorMcLeod]

As long as the plugin stays in submission queue, yes.

Makes your api say something as "give user ability", then the ability plugin catch this, if player is alive, give item now, else, wait to player spawn.
PreThink should disappear from sub-plugins unless it is really needed for special ability.

[Shadows In Rain]

Originally Posted by ConnorMcLeod As long as the plugin stays in submission queue, yes.

Even 100 single true/false checks per second does not any perfomance trouble.

[Arkshine]

Attachment updated with the compiled plugin.

By the way, fastly look at your code, you overuse "static" when that's not needed at all.

[Shadows In Rain]

I will take into accoun your notes and try to fix.
It's easy to fix, but usually i have no time.
I follow the rule "first write, then optimise".

[ConnorMcLeod]

Originally Posted by Shadows In Rain Even 100 single true/false checks per second does not any perfomance trouble.

Obviously, but that's not a reason to show bad code examples, also i don't think you gonna have any problem to find a good way to replace that.