[joaquimandrade]

Originally Posted by Nextra You can also prove that by simple example codes. For example, this will make the compiler throw warnings but on runtime you won't see a difference compared to correct tagging: PHP Code: #include <amxmodx> public plugin_init( ) {     register_plugin( "Tagmix", "1337", "Nextra" );     new bool:bTest;     for( new i = 0; i < 3; i++ )     {         bTest = random_float( 0.0, 3.0 );         log_amx( "%f", bTest );     } }  Output: L 04/18/2009 - 21:25:44: [tags.amxx] 1.831825 L 04/18/2009 - 21:25:44: [tags.amxx] 2.950227 L 04/18/2009 - 21:25:44: [tags.amxx] 0.513996

Yes.

[Empowers]

is it possible to make somethink like this?

PHP Code:

new is_pev_valid[1366] 


So we can use it like pev_valid(ent) native

[Arkshine]

Not worth to do that because an entity can be not valid at any time because of plugins and others. So you will have to update constantly the entity state. No, really not safe and it will not be an optimization.

[xPaw]

Originally Posted by arkshine Not worth to do that because an entity can be not valid at any time because of plugins and others. So you will have to update constantly the entity state. No, really not safe and it will not be an optimization.

This is same as using

PHP Code:

new g_isAlive[33];

// ..... 


[Empowers]

Originally Posted by xPaw This is same as using PHP Code: new g_isAlive[33];

why? g_isAlive is a good optimization & it's pretty save:

PHP Code:

//code by MeRcyLeZZ
public fw_PlayerSpawn( id )
{
    if ( !is_user_alive( id ) || !cs_get_user_team( id ) )
        return;
    
    g_isAlive[id] = true
}

public fw_PlayerKilled( id )
{
    g_isAlive[id] = false
} 


[Arkshine]

@ xPaw : Not really. You don't have a forward which says you this entity is valid or not. Plus the number of max entity can be changed and is different whereas the max slots of server, it's not a good idea to harcode a value.

[Empowers]

Originally Posted by arkshine the number of max entity can be changed and is different whereas the max slots of server, it's not a good idea to harcode a value.

When there a 32 slots on the server.. MAX_ENTs = 1365

[Arkshine]

But it can be changed using the -num_edicts switch and for people which don't have a 32 slots, you will harcode such value it will be a waste of memory.

[Empowers]

Originally Posted by arkshine But it can be changed using the -num_edicts switch and for people which don't have a 32 slots, you will harcode such value it will be a waste of memory.

So we can use bitsum for that

PHP Code:

new bitsum_pev_valid 


[Emp`]

Originally Posted by Empowers So we can use bitsum for that PHP Code: new bitsum_pev_valid

No because a bitsum can only go to (1<<31)

Originally Posted by arkshine You don't have a forward which [tells] you this entity is valid or not.

That is the main reason why you cannot do it with entites at all.