ConVars (SourceMod Scripting)/ru - Revision history

Kailo at 16:06, 22 June 2019

2019-06-22T16:06:39Z

Kailo: Kailo moved page Ru:ConVars (SourceMod Scripting) to ConVars (SourceMod Scripting)/ru: Wrong non-english page name

2015-03-08T15:42:35Z

Kailo moved page Ru:ConVars (SourceMod Scripting) to ConVars (SourceMod Scripting)/ru: Wrong non-english page name

R1KO at 20:50, 6 January 2014

2014-01-06T20:50:54Z

R1KO at 20:44, 6 January 2014

2014-01-06T20:44:03Z

R1KO at 20:38, 6 January 2014

2014-01-06T20:38:23Z

Frenzzy at 10:34, 24 December 2008

2008-12-24T10:34:44Z

Frenzzy: New page: ConVars are ''con''sole ''var''iables. They store string, float, or numerical values. These values can be changed via the console or .cfg files, and sometimes even persist across server ...

2008-12-23T16:21:01Z

New page: ConVars are ''con''sole ''var''iables. They store string, float, or numerical values. These values can be changed via the console or .cfg files, and sometimes even persist across server ...

New page

ConVars are ''con''sole ''var''iables. They store string, float, or numerical values. These values can be changed via the console or .cfg files, and sometimes even persist across server sessions.

=Introduction=
ConVars are accessed through Handles. There are two ways to obtain a ConVar Handle. You can either create a new ConVar, or find an existing one. If you create a ConVar that already exists, it will automatically re-use the old one.

''Note: ConVar Handles are unique to the ConVar, and do not need to be freed or "uncreated." They exist until SourceMod is unloaded.''

==Finding ConVars==
Finding ConVars is very simple. For example, let's say you want to use <tt>mp_startmoney</tt> from Counter-Strike:Source:

<pawn>new g_hStartMoney

public OnPluginStart()
{
g_hStartMoney = FindConVar("mp_startmoney")
}</pawn>

''Note: FindConVar() will return ''<tt>INVALID_HANDLE</tt>'' if the ConVar is not found. Keep this in mind if you are trying to read ConVars from other plugins.''

==Creating ConVars==
A simple ConVar only requires two parameters, a name and a default value. However, it's a good idea to include a description:

<pawn>new Handle:g_hEnabled

public OnPluginStart()
{
g_hEnabled = CreateConVar("myplugin_enabled", "1", "Sets whether my plugin is enabled")
}</pawn>

You can also specify value constraints. For example, let's create a cvar called <tt>myplugin_ratio</tt> which cannot go above 1.0 or below 0.1.
<pawn>new Handle:g_hEnabled

public OnPluginStart()
{
g_hEnabled = CreateConVar("myplugin_ratio",
"0.6",
"Sets a vote ratio",
_, /* Flags will be discussed later */
true, /* Has a minimum */
0.1,
true, /* Has a maximum */
1.0)
}</pawn>

The default value can be any type of data, and it does not restrict future data types that can be used. However, the minimum and maximum constraints always interpret the value as a float.

If you create a ConVar that already exists, you will receive a Handle to that ConVar. Furthermore, the Handle itself will be identical, as neither plugin will own the Handle. The description, default value, or constraints will not be changed.

=Using/Changing Values=
Managing ConVars is very simple. For example, let's say we want to change <tt>mp_startmoney</tt>, but save the old value and restore it later. Re-using our <tt>mp_startmoney</tt> code from <tt>FindConVar</tt>:

<pawn>new g_oldmoney

SetStartMoney(newmoney)
{
g_oldmoney = GetConVarInt(g_hStartMoney)
SetConVarInt(g_hStartMoney, newmoney)
}

RestoreStartMoney()
{
SetConVarInt(g_hStartMoney, g_oldmoney)
}</pawn>

Although there are different functions for value types (float, string, et cetera), the internal data is always stored the same way. For example, this code will work:

<pawn>public GetStartMoney()
{
decl String:buffer[128]

GetConVarString(g_hStartMoney, buffer, sizeof(buffer))

return StringToInt(buffer)
}</pawn>

Even though <tt>mp_startmoney</tt> is an integer, it can still be retrieved as a string.

=Flags=
ConVars can have a number of flags to change their behaviour. A few of the important flags are:
*<tt>FCVAR_PROTECTED</tt> - Sensitive information (should not be exposed to clients or logs).
*<tt>FCVAR_NOTIFY</tt> - Clients are notified of changes.
*<tt>FCVAR_CHEAT</tt> - Can only be use if <tt>sv_cheats</tt> is 1.
*<tt>FCVAR_REPLICATED</tt> - Setting is forced to clients.

Let's say we wanted to toggle whether a cvar had FCVAR_CHEAT. The following two functions could be used:
<pawn>UnsetCheatVar(Handle:hndl)
{
new flags = GetConVarFlags(hndl)
flags &= ~FCVAR_CHEAT
SetConVarFlags(hndl, flags)
}

SetCheatVar(Handle:hndl)
{
new flags = GetConVarFlags(hndl)
flags |= FCVAR_CHEAT
SetConVarFlags(hndl, flags)
}</pawn>

=Change Callbacks=
As of Half-Life 2, it is possible to know when ConVars change. While this is a very powerful feature, you must be careful not to set a ConVar inside a ConVar change hook such that it re-invokes he same callback. This results in ''infinite recursion''.

For example, let's say you want to detect when <tt>bot_quota</tt> changes and to prevent it from going below 2:

<pawn>new Handle:g_hBotQuota

public OnPluginStart()
{
g_hBotQuota = FindConVar("bot_quota")
if (g_hBotQuota != INVALID_HANDLE)
{
HookConVarChange(g_hBotQuota, OnBotQuotaChange)
}
}

public OnBotQuotaChange(Handle:cvar, const String:oldVal[], const String:newVal[])
{
if (StringToInt(newVal) < 2)
{
SetConVarInt(cvar, 2)
}
}</pawn>

'''Note 1:''' You do not need to explicitly unhook ConVarChange functions on shutdown. These hooks are removed when your plugin unloads.

'''Note 2:''' You cannot prevent cvar changes from happening; you can only change the value again. If the engine or game mod already have a change function installed for a ConVar, that function will always be called first.

[[Category:SourceMod Scripting]]
[[Category:Russian]]

← Older revision		Revision as of 16:06, 22 June 2019
Line 1:		Line 1:
		+	{{Languages\|ConVars_(SourceMod_Scripting)}}
	Квары - ''это консольные переменные.'' Они могут иметь числовое или строчное значение. Их значения могут быть изменены через консоль или с помощью .cfg файлов, а иногда сохраняются для всех сеансов сервера.		Квары - ''это консольные переменные.'' Они могут иметь числовое или строчное значение. Их значения могут быть изменены через консоль или с помощью .cfg файлов, а иногда сохраняются для всех сеансов сервера.

@@ Line 77: / Line 77: @@
 =Флаги=
-ConVars can have a number of flags to change their behaviour.  A few of the important flags are:
+Квары могут иметь ряд флагов, в зависимости от которых могут менять свое поведение. Основные флаги:
-*<tt>FCVAR_PROTECTED</tt> - Sensitive information (should not be exposed to clients or logs).
+*<tt>FCVAR_PROTECTED</tt> - Секретная информация (не должны подвергаться воздействию клиентов или логов).
-*<tt>FCVAR_NOTIFY</tt> - Clients are notified of changes.
+*<tt>FCVAR_NOTIFY</tt> - Уведомление клиентов об изменении.
-*<tt>FCVAR_CHEAT</tt> - Can only be use if <tt>sv_cheats</tt> is 1.
+*<tt>FCVAR_CHEAT</tt> - Могут использоваться только в случае если <tt>sv_cheats</tt> равно 1.
-*<tt>FCVAR_REPLICATED</tt> - Setting is forced to clients.
+*<tt>FCVAR_REPLICATED</tt> - Принудительная установка значения квара на клиенте.
-Let's say we wanted to toggle whether a cvar had FCVAR_CHEAT.  The following two functions could be used:
+Например,  мы хотим изменить значение квара с флагом FCVAR_CHEAT.  The following two functions could be used:
 <pawn>UnsetCheatVar(Handle:hndl)
+{

← Older revision		Revision as of 10:34, 24 December 2008
Line 126:		Line 126:
	'''Note 2:''' You cannot prevent cvar changes from happening; you can only change the value again. If the engine or game mod already have a change function installed for a ConVar, that function will always be called first.		'''Note 2:''' You cannot prevent cvar changes from happening; you can only change the value again. If the engine or game mod already have a change function installed for a ConVar, that function will always be called first.

−	[[Category:SourceMod Scripting]]	+	[[Category:Ru:SourceMod Scripting]]
−	~~[[Category:Russian~~]]

← Older revision	Revision as of 15:42, 8 March 2015
(No difference)

@@ Line 63: / Line 63: @@
 }</pawn>
-Although there are different functions for value types (float, string, et cetera), the internal data is always stored the same way.  For example, this code will work:
+Хотя существуют различные функции для типов значений (с плавающей точкой, строки, и так далее), внутренние данные всегда сохраняются так же. Например, этот код будет работать:
 <pawn>public GetStartMoney()
@@ Line 74: / Line 74: @@
 }</pawn>
-Even though <tt>mp_startmoney</tt> is an integer, it can still be retrieved as a string.
+Несмотря на то, что <tt>mp_startmoney</tt> целое число, он может использоваться как строка.
-=Flags=
+=Флаги=
 ConVars can have a number of flags to change their behaviour.  A few of the important flags are:
 *<tt>FCVAR_PROTECTED</tt> - Sensitive information (should not be exposed to clients or logs).

@@ Line 1: / Line 1: @@
-ConVars are ''con''sole ''var''iables.  They store string, float, or numerical values.  These values can be changed via the console or .cfg files, and sometimes even persist across server sessions.
+Квары - ''это консольные переменные.'' Они могут иметь числовое или строчное значение. Их значения могут быть изменены через консоль или с помощью .cfg файлов, а иногда сохраняются для всех сеансов сервера.
-=Introduction=
+=Введение=
-ConVars are accessed through Handles.  There are two ways to obtain a ConVar Handle.  You can either create a new ConVar, or find an existing one.  If you create a ConVar that already exists, it will automatically re-use the old one.
+Квары доступны через Handle`s. Есть 2 способа получить Handle квара. Создать новый квар или найти существующий. Если вы создадите уже существующий квар, автоматически будет использоваться старый.
-''Note: ConVar Handles are unique to the ConVar, and do not need to be freed or "uncreated."  They exist until SourceMod is unloaded.''
+''Примечание: Handle`s для кваров являются уникальными, их не нужно закрывать или присваивать INVALID_HANDLE. Они должны существовать пока SourceMod запущен.''
-==Finding ConVars==
+==Поиск кваров==
-Finding ConVars is very simple.  For example, let's say you want to use <tt>mp_startmoney</tt> from Counter-Strike:Source:
+Искать квары очень просто. Например, вы хотите найти <tt>mp_startmoney</tt> из Counter-Strike:Source:
 <pawn>new g_hStartMoney
@@ Line 16: / Line 16: @@
 }</pawn>
-''Note: FindConVar() will return ''<tt>INVALID_HANDLE</tt>'' if the ConVar is not found.  Keep this in mind if you are trying to read ConVars from other plugins.''
+''Примечание: FindConVar() вернет ''<tt>INVALID_HANDLE</tt>'' если квар не найден.  Keep this in mind if you are trying to read ConVars from other plugins.''
-==Creating ConVars==
+==Создание кваров==
-A simple ConVar only requires two parameters, a name and a default value.  However, it's a good idea to include a description:
+Простейший квар требует всего 2 значения: имя и значение по умолчанию. Тем не менее, он может содержать описание:
 <pawn>new Handle:g_hEnabled
@@ Line 25: / Line 25: @@
 public OnPluginStart()
+{
-	g_hEnabled = CreateConVar("myplugin_enabled", "1", "Sets whether my plugin is enabled")
+	g_hEnabled = CreateConVar("myplugin_enabled", "1", "Включение/Выключение плагина.")
 }</pawn>
-You can also specify value constraints.  For example, let's create a cvar called <tt>myplugin_ratio</tt> which cannot go above 1.0 or below 0.1.
+Вы так же имеете возможностю ограничить значение. Например, давайте создадим квар названием <tt>myplugin_ratio</tt>, который не может быть выше 1,0 и ниже 0,1.
 <pawn>new Handle:g_hEnabled
@@ Line 36: / Line 36: @@
 			"0.6",
 			"Sets a vote ratio",
-			_,	/* Flags will be discussed later */
+			_,	/* Флаги (будут обсуждаться позже) */
-			true,	/* Has a minimum */
+			true,	/* Включить минимальное значение */
 .1,
-			true,	/* Has a maximum */
+			true,	/* Включить максимальное значение */
 .0)
 }</pawn>
-The default value can be any type of data, and it does not restrict future data types that can be used.  However, the minimum and maximum constraints always interpret the value as a float.
+Значение по умолчанию может иметь любой тип данных, и оно не ограничивает будущие типы данных, которые можно использовать. Тем не менее, минимальные и максимальные ограничения всегда должны быть числом с плавающей точкой (float).
-If you create a ConVar that already exists, you will receive a Handle to that ConVar.  Furthermore, the Handle itself will be identical, as neither plugin will own the Handle.  The description, default value, or constraints will not be changed.
+Если вы создаете квар, который уже существует, вы получите Handle на этот квар. Кроме того, сами Handle будут идентичны, поскольку плагин будет владеть Handle. Описание, значение по умолчанию, или ограничения не будут изменены.
-=Using/Changing Values=
+=Использование/Изменение значений=
-Managing ConVars is very simple.  For example, let's say we want to change <tt>mp_startmoney</tt>, but save the old value and restore it later.  Re-using our <tt>mp_startmoney</tt> code from <tt>FindConVar</tt>:
+Использовать квары очень просто. Например, мы хотим изменить <tt>mp_startmoney</tt>, но сохранить старое значение и восстановить его позже. Повторно используем наш код <tt>mp_startmoney</tt> от раздела <tt>Получение кваров</tt>:
 <pawn>new g_oldmoney