Quote:
Originally Posted by CreativeTR
In some cases due to differences in definition tags, becomes an unreadable command array (It's always like this)
|
What?
Both the return value of cs_get_user_team() and CS_TEAM_T constant are tagged with CsTeams:, a tag override is redundant.
Quote:
of course, it makes sense for pawn just like c++
if you don't pay attention to the case, it will cause "Tag mismatch warming". You can try this
PHP Code:
MessageBox::Show("message","title, ..."
diffrence (it will cause fatal fault)
PHP Code:
messageBox::Show("message","title, ..."
|
Floating point values are implicitly tagged with Float: in Pawn, there's no need to override the tag. Again, redundant.
Quote:
if plugin send this command to client all time, it will cause SZ_getSpace overflow without FSB_ALLOW OVERFLOW
The fact that this change in client isn't healthy will lead to mistakes.
For this reason, these are done with "cfg" before the game.
|
What command? Getting a cvar value is never sent to clients and you can do it as many times as you want in a single frame. As Hamlet said, use pcvars. In 1.8.3, use cvar binding.
Quote:
Amxmodx (1.8.3-dev) after updating "MAX_PLAYERS 32 and [MAX_PLAYERS+1]" is changed.
if you do this, you will encounter a lot of errors
new functuality from AMXX amxconst.inc
MAX_PLAYERS 33 and and without + 1 ([MAX_PLAYERS])
|
In 1.8.3 there's
Code:
/**
* The maximum buffer size required to store a clients name.
*/
#define MAX_NAME_LENGTH 32
use that size for clients' names.