Exolent[jNr]
09-23-2010, 18:14
About XVars
XVars are public variables that can be accessed across plugins.
They work and look like normal variables inside of the plugin creating them, but have to be accessed a different way in the other plugins.
Purpose:
XVars should be used instead of CVars when the variables need to be private to the plugins.
XVars cannot be changed from the server console or by any existing command unless a plugin is made for that purpose.
It basically provides security to variables.
If you have dynamic natives who's purpose is to only share a variable between plugins, XVars should be used instead.
Dynamic natives are a bit slower than using XVars (see Connor's post (https://forums.alliedmods.net/showpost.php?p=1307575&postcount=8)).
Creating:
When creating XVars, they need to be global and public.
What this means is that they should not be inside any function when created and must be prefixed with public instead of new or stock.
Example:
public ExampleXvarVariable;
public bool:ExampleXvarBoolean = true;
public Float:ExampleXvarFloat = 3.14;
Inside the plugin that created them, they work just like normal variables.
Assigning values and accessing values works just the same.
XVars only support cells (integers, floats, bools, etc.).
Arrays (including strings, since strings are arrays of characters) cannot be used with XVars.
Cross-Plugin:
When accessing XVars from another plugin, you have to use specific natives.
First, you need to get the XVar's unique identifier:
new g_pExampleXvarVariable;
new g_pExampleXvarBoolean;
new g_pExampleXvarFloat;
public plugin_init( )
{
// get the XVar's unique identifier and store for usage throughout the plugin
g_pExampleXvarVariable = get_xvar_id( "ExampleXvarVariable" );
// check if the XVar is valid
if( g_pExampleXvarVariable == -1 )
{
set_fail_state( "XVar did not exist: ExampleXvarVariable" );
}
// repeat above for other 2 XVars
}
If you are just interested in checking if the XVar is valid, you can do this:
public plugin_init( )
{
// check if the XVar is valid
if( !xvar_exists( "ExampleXvarVariable" ) )
{
set_fail_state( "XVar did not exist: ExampleXvarVariable" );
}
// repeat above for other 2 XVars
}
To access an XVar's value, you can use these two natives:
// get integer value
new iValue = get_xvar_num( g_pExampleXvarVariable );
// get boolean value
new bool:bValue = bool:get_xvar_num( g_pExampleXvarBoolean );
// get float value
new Float:flValue = get_xvar_float( g_pExampleXvarFloat );
To set an XVar's value, you can use these two natives:
// set integer value
set_xvar_num( g_pExampleXvarVariable, 10 );
// set boolean value
set_xvar_num( g_pExampelXvarBoolean, false );
// set float value
set_xvar_float( g_pExampleXvarFloat, 19.6 );
For more information on the natives, read the funcwiki (http://www.amxmodx.org/funcwiki.php?search=xvar&go=search).
Note: The plugin creating the variable does not have to be above the other plugins that are accessing the variable in the plugins.ini.
Duplication:
Plugins can have the same public variables without compilation error or runtime error.
The only effect on this is where the value is being changed/retrieved.
The first plugin that creates the public variable is the plugin that will be affected by it's value and will send the value to other plugins with get_xvar_*().
Here is an example:
// This is plugin #1 in the plugins.ini
#include < amxmodx >
public DisplayRoundMessage;
public plugin_init( )
{
register_plugin( "New Round Display", "0.0.1", "Exolent" );
register_event( "HLTV", "EventNewRound", "a", "1=0", "2=0" );
}
public EventNewRound( )
{
if( DisplayRoundMessage )
{
client_print( 0, print_chat, "A new round has started!" );
}
}
// This is plugin #2 in the plugins.ini
#include < amxmodx >
public DisplayRoundMessage;
public plugin_init( )
{
register_plugin( "New Round Display", "0.0.1", "Exolent" );
register_event( "HLTV", "EventNewRound", "a", "1=0", "2=0" );
}
public EventNewRound( )
{
if( DisplayRoundMessage )
{
client_print( 0, print_chat, "A new round has started!" );
}
}
Yes, they are the same plugin so it's a weak example, but it gets the idea across.
Okay, so these 2 plugins have the same public variable.
If we had this plugin:
#include < amxmodx >
public plugin_init( )
{
register_plugin( "New Round Display Enabler", "0.0.1", "Exolent" );
new pDisplayRoundMessage = get_xvar_id( "DisplayRoundMessage" );
if( pDisplayRoundMessage != -1 )
{
set_xvar_num( pDisplayRoundMessage, 1 );
}
}
This would only affect the first plugin's variable and the second plugin would still not show the message.
Extra Notes:
My test files can be used if you need any more understanding of how they work.
xvar_holder.sma is above xvar_finder.sma in the plugins.ini.
The commands that mimic natives require the same arguments, just in command format.
Example: get_xvar_id1 "SomeXvarVariable"
All feedback and suggestions are welcome.
XVars are public variables that can be accessed across plugins.
They work and look like normal variables inside of the plugin creating them, but have to be accessed a different way in the other plugins.
Purpose:
XVars should be used instead of CVars when the variables need to be private to the plugins.
XVars cannot be changed from the server console or by any existing command unless a plugin is made for that purpose.
It basically provides security to variables.
If you have dynamic natives who's purpose is to only share a variable between plugins, XVars should be used instead.
Dynamic natives are a bit slower than using XVars (see Connor's post (https://forums.alliedmods.net/showpost.php?p=1307575&postcount=8)).
Creating:
When creating XVars, they need to be global and public.
What this means is that they should not be inside any function when created and must be prefixed with public instead of new or stock.
Example:
public ExampleXvarVariable;
public bool:ExampleXvarBoolean = true;
public Float:ExampleXvarFloat = 3.14;
Inside the plugin that created them, they work just like normal variables.
Assigning values and accessing values works just the same.
XVars only support cells (integers, floats, bools, etc.).
Arrays (including strings, since strings are arrays of characters) cannot be used with XVars.
Cross-Plugin:
When accessing XVars from another plugin, you have to use specific natives.
First, you need to get the XVar's unique identifier:
new g_pExampleXvarVariable;
new g_pExampleXvarBoolean;
new g_pExampleXvarFloat;
public plugin_init( )
{
// get the XVar's unique identifier and store for usage throughout the plugin
g_pExampleXvarVariable = get_xvar_id( "ExampleXvarVariable" );
// check if the XVar is valid
if( g_pExampleXvarVariable == -1 )
{
set_fail_state( "XVar did not exist: ExampleXvarVariable" );
}
// repeat above for other 2 XVars
}
If you are just interested in checking if the XVar is valid, you can do this:
public plugin_init( )
{
// check if the XVar is valid
if( !xvar_exists( "ExampleXvarVariable" ) )
{
set_fail_state( "XVar did not exist: ExampleXvarVariable" );
}
// repeat above for other 2 XVars
}
To access an XVar's value, you can use these two natives:
// get integer value
new iValue = get_xvar_num( g_pExampleXvarVariable );
// get boolean value
new bool:bValue = bool:get_xvar_num( g_pExampleXvarBoolean );
// get float value
new Float:flValue = get_xvar_float( g_pExampleXvarFloat );
To set an XVar's value, you can use these two natives:
// set integer value
set_xvar_num( g_pExampleXvarVariable, 10 );
// set boolean value
set_xvar_num( g_pExampelXvarBoolean, false );
// set float value
set_xvar_float( g_pExampleXvarFloat, 19.6 );
For more information on the natives, read the funcwiki (http://www.amxmodx.org/funcwiki.php?search=xvar&go=search).
Note: The plugin creating the variable does not have to be above the other plugins that are accessing the variable in the plugins.ini.
Duplication:
Plugins can have the same public variables without compilation error or runtime error.
The only effect on this is where the value is being changed/retrieved.
The first plugin that creates the public variable is the plugin that will be affected by it's value and will send the value to other plugins with get_xvar_*().
Here is an example:
// This is plugin #1 in the plugins.ini
#include < amxmodx >
public DisplayRoundMessage;
public plugin_init( )
{
register_plugin( "New Round Display", "0.0.1", "Exolent" );
register_event( "HLTV", "EventNewRound", "a", "1=0", "2=0" );
}
public EventNewRound( )
{
if( DisplayRoundMessage )
{
client_print( 0, print_chat, "A new round has started!" );
}
}
// This is plugin #2 in the plugins.ini
#include < amxmodx >
public DisplayRoundMessage;
public plugin_init( )
{
register_plugin( "New Round Display", "0.0.1", "Exolent" );
register_event( "HLTV", "EventNewRound", "a", "1=0", "2=0" );
}
public EventNewRound( )
{
if( DisplayRoundMessage )
{
client_print( 0, print_chat, "A new round has started!" );
}
}
Yes, they are the same plugin so it's a weak example, but it gets the idea across.
Okay, so these 2 plugins have the same public variable.
If we had this plugin:
#include < amxmodx >
public plugin_init( )
{
register_plugin( "New Round Display Enabler", "0.0.1", "Exolent" );
new pDisplayRoundMessage = get_xvar_id( "DisplayRoundMessage" );
if( pDisplayRoundMessage != -1 )
{
set_xvar_num( pDisplayRoundMessage, 1 );
}
}
This would only affect the first plugin's variable and the second plugin would still not show the message.
Extra Notes:
My test files can be used if you need any more understanding of how they work.
xvar_holder.sma is above xvar_finder.sma in the plugins.ini.
The commands that mimic natives require the same arguments, just in command format.
Example: get_xvar_id1 "SomeXvarVariable"
All feedback and suggestions are welcome.