[HamletEagle]

Originally Posted by Hedgehog95 HamletEagle, It saves more than 100 lines of code and you don't need to allocate memory for EngFunc_AllocString everytime.

Really ? I need an API for not allocating each time ? I can simply save it in plugin_init, that's all:

PHP Code:

new SomethingHere

public plugin_init()
{
    SomethingHere = engfunc(EngFunc_AllocString, "abracadabra")
} 


Originally Posted by Hedgehog95 fysiks, This is enough. You don't need remove entity, make basic checks, make/remove HamHook.

This are very simple operations that can be done easily without any API. Using an API here is improper and I would say it's a bad habit, let people learn how to deal with basic entity stuff.

[Hedgehog Fog]

Originally Posted by HamletEagle Really ? I need an API for not allocating each time ? I can simply save it in plugin_init, that's all:

I means allocate memory for each new item.

Originally Posted by HamletEagle This are very simple operations that can be done easily without any API. Using an API here is improper and I would say it's a bad habit, let people learn how to deal with basic entity stuff.

Change player model and team are very simple operations too, but we have API for this has been approved Approved, I have nothing against that.
API is made to simplify the process of creating something.
I don't force you to approve this plugin, I just don't understand your position.
This plugin can be ignored and continue "live" in "New Plugin Submissions".

[HamletEagle]

Originally Posted by Hedgehog95 I means allocate memory for each new item. Change player model and team are very simple operations too, but we have API for this has been approved Approved, I have nothing against that. API is made to simplify the process of creating something. I don't force you to approve this plugin, I just don't understand your position. This plugin can be ignored and continue "live" in "New Plugin Submissions".

New plugin is just a waiting room, we have to filter all the plugins. That's what I'm trying to do.
Not really simple operations, the player model API was made to avoid overflow which happens when you switch the team(so a model change occur) on too many players.

Think again on what your API gives and think how easy it is to do this directly. Don't tell me someone may not know, then it's time for him to learn to do basic entity manipulation.