Arma 3: Scripted Database - Revision history

Lou Montana: Add Obsolete note

2025-10-03T15:35:17Z

Add Obsolete note

← Older revision		Revision as of 17:35, 3 October 2025
Line 1:		Line 1:
	{{TOC\|side}}		{{TOC\|side}}
	{{Feature\|~~informative~~\|~~{{GVI\|arma3\|2.02}}~~ For better peformance (faster access and write speeds) you can use [[HashMap]]s instead.}}		{{Feature\|obsolete\|For better peformance (faster access and write speeds) you can use [[HashMap]]s instead.\|arma3\|2.02\|}}
	A [[Arma 3: Scripted Database\|Scripted Database]] is a simple way to manage information with ingame functions from ~~Bohemia Interactive~~ and has been introduced in [[{{tkoh}}]]. Instead of using file operations it is a semi persistent sqf database. This means that the database is only available during the mission and can be modified with ingame commands. The downside is that it will be wiped when the mission ends or the game/server crashes. To make the database persistent you can save it periodically to the [[profileNamespace]].

			A [[Arma 3: Scripted Database\|Scripted Database]] is a simple way to manage information with ingame functions from {{Name\|bi}} and has been introduced in [[{{tkoh}}]].
			Instead of using file operations it is a semi persistent sqf database. This means that the database is only available during the mission and can be modified with ingame commands.
			The downside is that it will be wiped when the mission ends or the game/server crashes. To make the database persistent you can save it periodically to the [[profileNamespace]].


Line 20:		Line 24:


	== ~~Creating A~~ Database ==		== Database Creation ==

	There are theoretically three options:		There are theoretically three options:

	=== ~~Declaring An~~ Empty Array ===		=== Empty Array Declaration ===

	The most straightforward option. Simply add <sqf inline>TAG_database = [];</sqf> to any script where you want to declare the database, eg [[Event Scripts#initServer.sqf\|initServer.sqf]].		The most straightforward option. Simply add <sqf inline>TAG_database = [];</sqf> to any script where you want to declare the database, eg [[Event Scripts#initServer.sqf\|initServer.sqf]].

	=== ~~Importing From An .xml File~~ ===		=== XML Import ===

	[[BIS_fnc_dbImportXML]] can convert the content of an xml file into an array which has the format of a Scripted Database. An xml file can be way easier to read than a nested array. Just keep in mind that you can't modify the xml file from within the game, meaning that once the mission restarts the default database from that file will be loaded and not the database which existed at the end of a mission.		[[BIS_fnc_dbImportXML]] can convert the content of an xml file into an array which has the format of a Scripted Database. An xml file can be way easier to read than a nested array. Just keep in mind that you can't modify the xml file from within the game, meaning that once the mission restarts the default database from that file will be loaded and not the database which existed at the end of a mission.

	=== ~~Importing From A~~ Config ===		=== Config Import ===

	A config can either be [[Description.ext]] ([[missionConfigFile\|mission config]]), the [[Campaign Description.ext]] ([[campaignConfigFile\|campaign config]]) or an addon's [[Config.cpp/bin File Format\|config.bin/.cpp]] ([[configFile\|global config]]). The [[BIS_fnc_dbImportConfig]] function can import the config classes from the config but not the values. This makes this function a bit useless as the same can be achieved with the other options but even better. Writing to the config is also only possible from outside the game and not with commands.		A config can either be [[Description.ext]] ([[missionConfigFile\|mission config]]), the [[Campaign Description.ext]] ([[campaignConfigFile\|campaign config]]) or an addon's [[Config.cpp/bin File Format\|config.bin/.cpp]] ([[configFile\|global config]]). The [[BIS_fnc_dbImportConfig]] function can import the config classes from the config but not the values. This makes this function a bit useless as the same can be achieved with the other options but even better. Writing to the config is also only possible from outside the game and not with commands.


	== ~~Operating A~~ Database ==		== Database Operation ==

	=== Classes And Values ===		=== Classes And Values ===

	The Scripted Database consists of classes and values. Classes can be identified by the class symbol "#" while the symbol for values is "&". The sole purpose of [[BIS_fnc_dbSymbolClass]] and [[BIS_fnc_dbSymbolValue]] is to return this sign. While the class is followed by an array which contains values, the value is only followed by its content which can be any data type. After the values content might follow another value or the array for that class can end. Here is an example of what the database looks like:		The Scripted Database consists of classes and values. Classes can be identified by the class symbol "#" while the symbol for values is "&". The sole purpose of [[BIS_fnc_dbSymbolClass]] and [[BIS_fnc_dbSymbolValue]] is to return this sign. While the class is followed by an array which contains values, the value is only followed by its content which can be any data type. After the values content might follow another value or the array for that class can end. Here is an example of what the database looks like:
	<sqf>["#PLAYERS",["#1234",["&NAME","Bob","&KILLS",20,"&RANK","Sergent"],["#5678",["&NAME","Davis","&KILLS",0,"&RANK","Private"]]]</sqf>		<sqf>["#PLAYERS", ["#1234", ["&NAME", "Bob", "&KILLS", 20, "&RANK", "Sergent"], ["#5678", ["&NAME", "Davis", "&KILLS", 0, "&RANK", "Private"]]]</sqf>
	Let's format that a bit differently:		Let's format that a bit differently:
	<sqf>		<sqf>
Line 65:		Line 69:
	</sqf>		</sqf>

	=== ~~Accessing~~ Values ===		=== Values Access ===

	To get the content of a value you can use the [[BIS_fnc_dbValueReturn]] function. The first parameter is the database from which the value should be returned. The second one is the path where the value is located. If the function can not find the specified value you can set a default return value with the third parameter similar to [[getVariable]]. The following code displays the rank the player currently has in the database and if no value exists it will mark the player's rank as "PRIVATE":		To get the content of a value you can use the [[BIS_fnc_dbValueReturn]] function. The first parameter is the database from which the value should be returned.
			The second one is the path where the value is located. If the function can not find the specified value you can set a default return value with the third parameter similar to [[getVariable]].
			The following code displays the rank the player currently has in the database and if no value exists it will mark the player's rank as "PRIVATE":
	<sqf>		<sqf>
	private _puid = getPlayerUID player;		private _puid = getPlayerUID player;
Line 77:		Line 83:
	So while the config is not editable the database is, which leads us to...		So while the config is not editable the database is, which leads us to...

	=== Editing ~~Values~~ ===		=== Values Editing ===

	Values can be edited with the function [[BIS_fnc_dbValueSet]]. Continuing with the example from above the player was just promoted and a new rank has to be set in the database (array TAG_database):		Values can be edited with the function [[BIS_fnc_dbValueSet]]. Continuing with the example from above the player was just promoted and a new rank has to be set in the database (array {{hl\|TAG_database}}):
	<sqf>		<sqf>
	private _newRank = rank player;		private _newRank = rank player;

Lou Montana: Some wiki formatting

2022-07-15T14:53:38Z

Some wiki formatting

← Older revision		Revision as of 16:53, 15 July 2022
Line 1:		Line 1:
	{{TOC\|side}}		{{TOC\|side}}
	{{Feature\|informative\|{{GVI\|~~Arma3~~\|2.02}} For better peformance (faster access and write speeds) you can use [[HashMap]]s instead.}}		{{Feature\|informative\|{{GVI\|arma3\|2.02}} For better peformance (faster access and write speeds) you can use [[HashMap]]s instead.}}
	A [[Arma 3: Scripted Database\|Scripted Database]] is a simple way to manage information with ingame functions from Bohemia Interactive and has been introduced in [[{{tkoh}}]]. Instead of using file operations it is a semi persistent sqf database. This means that the database is only available during the mission and can be modified with ingame commands. The downside is that it will be wiped when the mission ends or the game/server crashes. To make the database persistent you can save it periodically to the [[profileNamespace]].		A [[Arma 3: Scripted Database\|Scripted Database]] is a simple way to manage information with ingame functions from Bohemia Interactive and has been introduced in [[{{tkoh}}]]. Instead of using file operations it is a semi persistent sqf database. This means that the database is only available during the mission and can be modified with ingame commands. The downside is that it will be wiped when the mission ends or the game/server crashes. To make the database persistent you can save it periodically to the [[profileNamespace]].

Line 26:		Line 26:
	=== Declaring An Empty Array ===		=== Declaring An Empty Array ===

	The most straightforward option. Simply add ~~{{ic\|~~TAG_database {{=}} [];}} to any script where you want to declare the database, eg [[Event Scripts\|initServer.sqf]].		The most straightforward option. Simply add <sqf inline>TAG_database = [];</sqf> to any script where you want to declare the database, eg [[Event Scripts#initServer.sqf\|initServer.sqf]].

	=== Importing From An .xml File ===		=== Importing From An .xml File ===
Line 42:		Line 42:

	The Scripted Database consists of classes and values. Classes can be identified by the class symbol "#" while the symbol for values is "&". The sole purpose of [[BIS_fnc_dbSymbolClass]] and [[BIS_fnc_dbSymbolValue]] is to return this sign. While the class is followed by an array which contains values, the value is only followed by its content which can be any data type. After the values content might follow another value or the array for that class can end. Here is an example of what the database looks like:		The Scripted Database consists of classes and values. Classes can be identified by the class symbol "#" while the symbol for values is "&". The sole purpose of [[BIS_fnc_dbSymbolClass]] and [[BIS_fnc_dbSymbolValue]] is to return this sign. While the class is followed by an array which contains values, the value is only followed by its content which can be any data type. After the values content might follow another value or the array for that class can end. Here is an example of what the database looks like:
	["#PLAYERS",["#1234",["&NAME","Bob","&KILLS",20,"&RANK","~~Seargent~~"],["#5678",["&NAME","Davis","&KILLS",0,"&RANK","Private"]]]		<sqf>["#PLAYERS",["#1234",["&NAME","Bob","&KILLS",20,"&RANK","Sergent"],["#5678",["&NAME","Davis","&KILLS",0,"&RANK","Private"]]]</sqf>
	Let's format that a bit differently:		Let's format that a bit differently:
	<~~code~~>[		<sqf>
	"#PLAYERS", ~~{{cc\|~~The uppermost class containing information about the players}}		[
			"#PLAYERS", // The uppermost class containing information about the players
	[		[
	"#1234", ~~{{cc\|~~An imaginary user id to identify a player without doubt}}		"#1234", // An imaginary user id to identify a player without doubt
	[		[
	~~{{cc\|~~Following here are some stats that the player has}}		// Following here are some stats that the player has
	"&NAME", "Bob",		"&NAME", "Bob",
	"&KILLS", 20,		"&KILLS", 20,
Line 62:		Line 63:
	]		]
	]		]
	</~~code~~>		</sqf>

	=== Accessing Values ===		=== Accessing Values ===

	To get the content of a value you can use the [[BIS_fnc_dbValueReturn]] function. The first parameter is the database from which the value should be returned. The second one is the path where the value is located. If the function can not find the specified value you can set a default return value with the third parameter similar to [[getVariable]]. The following code displays the rank the player currently has in the database and if no value exists it will mark the player's rank as "PRIVATE":		To get the content of a value you can use the [[BIS_fnc_dbValueReturn]] function. The first parameter is the database from which the value should be returned. The second one is the path where the value is located. If the function can not find the specified value you can set a default return value with the third parameter similar to [[getVariable]]. The following code displays the rank the player currently has in the database and if no value exists it will mark the player's rank as "PRIVATE":
	[[private]] _puid = [[getPlayerUID~~]] [[~~player]];		<sqf>
	[[private]] _rank = [TAG_database, ["players", _puid, "rank"], "PRIVATE"] [[call~~]] [[~~BIS_fnc_dbValueReturn]];		private _puid = getPlayerUID player;
	[[hint]] _rank;		private _rank = [TAG_database, ["players", _puid, "rank"], "PRIVATE"] call BIS_fnc_dbValueReturn;
			hint _rank;
			</sqf>
	If you ever worked with configs then you might notice the similarity between the array and the config paths. This is how you access a config value:		If you ever worked with configs then you might notice the similarity between the array and the config paths. This is how you access a config value:
	[[getText]] ([[missionConfigFile]] >> "Players" >> [[getPlayerUID~~]] [[~~player]] >> "rank");		<sqf>getText (missionConfigFile >> "Players" >> getPlayerUID player >> "rank");</sqf>
	So while the config is not editable the database is, which leads us to...		So while the config is not editable the database is, which leads us to...

Line 77:		Line 80:

	Values can be edited with the function [[BIS_fnc_dbValueSet]]. Continuing with the example from above the player was just promoted and a new rank has to be set in the database (array TAG_database):		Values can be edited with the function [[BIS_fnc_dbValueSet]]. Continuing with the example from above the player was just promoted and a new rank has to be set in the database (array TAG_database):
	[[private]] _newRank = [[rank~~]] [[~~player]];		<sqf>
	[[private]] _puid = [[getPlayerUID~~]] [[~~player]];		private _newRank = rank player;
	[TAG_database, ["players", _puid, "rank"], _newRank] [[call~~]] [[~~BIS_fnc_dbValueSet]];		private _puid = getPlayerUID player;
	The previous database array will be overwritten by the function, see the ~~{{ic\|~~[[set]]}} command.		[TAG_database, ["players", _puid, "rank"], _newRank] call BIS_fnc_dbValueSet;
			</sqf>
			The previous database array will be overwritten by the function, see the [[set]] command.


	[[Category:Arma Scripting Tutorials]]		[[Category:Arma Scripting Tutorials]]

7erra: hashmap alternative

2021-11-06T16:30:29Z

hashmap alternative

← Older revision		Revision as of 18:30, 6 November 2021
Line 1:		Line 1:
	{{TOC\|side}}		{{TOC\|side}}
			{{Feature\|informative\|{{GVI\|Arma3\|2.02}} For better peformance (faster access and write speeds) you can use [[HashMap]]s instead.}}
	A [[Arma 3: Scripted Database\|Scripted Database]] is a simple way to manage information with ingame functions from Bohemia Interactive and has been introduced in [[{{tkoh}}]]. Instead of using file operations it is a semi persistent sqf database. This means that the database is only available during the mission and can be modified with ingame commands. The downside is that it will be wiped when the mission ends or the game/server crashes. To make the database persistent you can save it periodically to the [[profileNamespace]].		A [[Arma 3: Scripted Database\|Scripted Database]] is a simple way to manage information with ingame functions from Bohemia Interactive and has been introduced in [[{{tkoh}}]]. Instead of using file operations it is a semi persistent sqf database. This means that the database is only available during the mission and can be modified with ingame commands. The downside is that it will be wiped when the mission ends or the game/server crashes. To make the database persistent you can save it periodically to the [[profileNamespace]].

R3vo: Text replacement - "{{Inline code|" to "{{ic|"

2021-02-27T17:10:07Z

Text replacement - "{{Inline code|" to "{{ic|"

← Older revision		Revision as of 19:10, 27 February 2021
Line 25:		Line 25:
	=== Declaring An Empty Array ===		=== Declaring An Empty Array ===

	The most straightforward option. Simply add {{~~Inline code~~\|TAG_database {{=}} [];}} to any script where you want to declare the database, eg [[Event Scripts\|initServer.sqf]].		The most straightforward option. Simply add {{ic\|TAG_database {{=}} [];}} to any script where you want to declare the database, eg [[Event Scripts\|initServer.sqf]].

	=== Importing From An .xml File ===		=== Importing From An .xml File ===
Line 79:		Line 79:
	[[private]] _puid = [[getPlayerUID]] [[player]];		[[private]] _puid = [[getPlayerUID]] [[player]];
	[TAG_database, ["players", _puid, "rank"], _newRank] [[call]] [[BIS_fnc_dbValueSet]];		[TAG_database, ["players", _puid, "rank"], _newRank] [[call]] [[BIS_fnc_dbValueSet]];
	The previous database array will be overwritten by the function, see the {{~~Inline code~~\|[[set]]}} command.		The previous database array will be overwritten by the function, see the {{ic\|[[set]]}} command.


	[[Category:Arma Scripting Tutorials]]		[[Category:Arma Scripting Tutorials]]

R3vo: typo

2021-01-29T23:37:16Z

typo

← Older revision		Revision as of 01:37, 30 January 2021
Line 1:		Line 1:
	{{TOC\|side}}		{{TOC\|side}}
	A [[Arma 3: Scripted Database\|Scripted Database]] is a simple way to manage information with ingame functions from Bohemia Interactive and has been introduced in [[{{tkoh}}]]. Instead of using file operations it is a semi persistent sqf database. This means that the database is only ~~avialable~~ during the mission and can be modified with ingame commands. The downside is that it will be wiped when the mission ends or the game/server crashes. To make the database persistent you can save it periodically to the [[profileNamespace]].		A [[Arma 3: Scripted Database\|Scripted Database]] is a simple way to manage information with ingame functions from Bohemia Interactive and has been introduced in [[{{tkoh}}]]. Instead of using file operations it is a semi persistent sqf database. This means that the database is only available during the mission and can be modified with ingame commands. The downside is that it will be wiped when the mission ends or the game/server crashes. To make the database persistent you can save it periodically to the [[profileNamespace]].

R3vo: category

2021-01-02T11:27:55Z

Lou Montana: Text replacement - "{{SideTOC}}" to "{{TOC|side}}"

2020-12-29T01:26:37Z

Text replacement - "{{SideTOC}}" to "{{TOC|side}}"

← Older revision		Revision as of 03:26, 29 December 2020
Line 1:		Line 1:
	{{~~SideTOC~~}}		{{TOC\|side}}
	A [[Arma 3: Scripted Database\|Scripted Database]] is a simple way to manage information with ingame functions from Bohemia Interactive and has been introduced in [[{{tkoh}}]]. Instead of using file operations it is a semi persistent sqf database. This means that the database is only avialable during the mission and can be modified with ingame commands. The downside is that it will be wiped when the mission ends or the game/server crashes. To make the database persistent you can save it periodically to the [[profileNamespace]].		A [[Arma 3: Scripted Database\|Scripted Database]] is a simple way to manage information with ingame functions from Bohemia Interactive and has been introduced in [[{{tkoh}}]]. Instead of using file operations it is a semi persistent sqf database. This means that the database is only avialable during the mission and can be modified with ingame commands. The downside is that it will be wiped when the mission ends or the game/server crashes. To make the database persistent you can save it periodically to the [[profileNamespace]].

Lou Montana: Fix the fix

2020-03-16T15:09:08Z

Fix the fix

← Older revision		Revision as of 17:09, 16 March 2020
Line 70:		Line 70:
	[[hint]] _rank;		[[hint]] _rank;
	If you ever worked with configs then you might notice the similarity between the array and the config paths. This is how you access a config value:		If you ever worked with configs then you might notice the similarity between the array and the config paths. This is how you access a config value:
	[[getText]] ([[~~missionConfigfile~~]] >> "Players" >> [[getPlayerUID]] [[player]] >> "rank");		[[getText]] ([[missionConfigFile]] >> "Players" >> [[getPlayerUID]] [[player]] >> "rank");
	So while the config is not editable the database is, which leads us to...		So while the config is not editable the database is, which leads us to...

Lou Montana: Fix typos and add links

2020-03-16T15:08:30Z

Fix typos and add links

← Older revision		Revision as of 17:08, 16 March 2020
Line 1:		Line 1:
	{{SideTOC}}		{{SideTOC}}
	A [[Arma 3: Scripted Database\|Scripted Database]] is a simple way to manage information with ingame functions from Bohemia Interactive. Instead of using file operations it is a semi persistent sqf database. This means that the database is only avialable during the mission and can be modified with ingame commands. The downside is that it will be wiped when the mission ends or the game/server crashes. To make the database persistent you can save it periodically to the profileNamespace.		A [[Arma 3: Scripted Database\|Scripted Database]] is a simple way to manage information with ingame functions from Bohemia Interactive and has been introduced in [[{{tkoh}}]]. Instead of using file operations it is a semi persistent sqf database. This means that the database is only avialable during the mission and can be modified with ingame commands. The downside is that it will be wiped when the mission ends or the game/server crashes. To make the database persistent you can save it periodically to the [[profileNamespace]].


Line 25:		Line 25:
	=== Declaring An Empty Array ===		=== Declaring An Empty Array ===

	The most straightforward option. Simply add {{Inline code\|TAG_database {{=}} [];}} to any script where you want to declare the database, eg initServer.sqf.		The most straightforward option. Simply add {{Inline code\|TAG_database {{=}} [];}} to any script where you want to declare the database, eg [[Event Scripts\|initServer.sqf]].

	=== Importing From An .xml File ===		=== Importing From An .xml File ===

	[[BIS_fnc_dbImportXML]] can convert the content of an xml file into an array which has the format of a Scripted Database. An xml file can be way easier to read than a nested array. Just keep in mind that you can't modify the xml file from within the game, meaning that once the mission restarts the default database from that file will be loaded and not the database which ~~exsisted~~ at the end of a mission.		[[BIS_fnc_dbImportXML]] can convert the content of an xml file into an array which has the format of a Scripted Database. An xml file can be way easier to read than a nested array. Just keep in mind that you can't modify the xml file from within the game, meaning that once the mission restarts the default database from that file will be loaded and not the database which existed at the end of a mission.

	=== Importing From A Config ===		=== Importing From A Config ===

	A config can either be the ~~description~~.ext (~~misssion~~ config) or a config.bin(/.cpp) (global config). The [[BIS_fnc_dbImportConfig]] function can import the config classes from the config but not the values. This makes this function a bit useless as the same can be achieved with the other options but even better. Writing to the config is also only possible from outside the game and not with commands.		A config can either be [[Description.ext]] ([[missionConfigFile\|mission config]]), the [[Campaign Description.ext]] ([[campaignConfigFile\|campaign config]]) or an addon's [[Config.cpp/bin File Format\|config.bin/.cpp]] ([[configFile\|global config]]). The [[BIS_fnc_dbImportConfig]] function can import the config classes from the config but not the values. This makes this function a bit useless as the same can be achieved with the other options but even better. Writing to the config is also only possible from outside the game and not with commands.


Line 40:		Line 40:
	=== Classes And Values ===		=== Classes And Values ===

	The Scripted Database consists of classes and values. Classes can be ~~indentified~~ by the class symbol "#" while the symbol for values is "&". The sole ~~puropse~~ of [[BIS_fnc_dbSymbolClass]] and [[BIS_fnc_dbSymbolValue]] is to return this sign. While the class is followed by an array which contains values, the value is only followed by its content which can be any data type. After the values content might follow another value or the array for that class ~~ends~~. Here is an example of what the database looks like:		The Scripted Database consists of classes and values. Classes can be identified by the class symbol "#" while the symbol for values is "&". The sole purpose of [[BIS_fnc_dbSymbolClass]] and [[BIS_fnc_dbSymbolValue]] is to return this sign. While the class is followed by an array which contains values, the value is only followed by its content which can be any data type. After the values content might follow another value or the array for that class can end. Here is an example of what the database looks like:
	["#PLAYERS",["#1234",["&NAME","Bob","&KILLS",20,"&RANK","Seargent"],["#5678",["&NAME","Davis","&KILLS",0,"&RANK","Private"]]]		["#PLAYERS",["#1234",["&NAME","Bob","&KILLS",20,"&RANK","Seargent"],["#5678",["&NAME","Davis","&KILLS",0,"&RANK","Private"]]]
	Let's format that a bit differently:		Let's format that a bit differently:
	<code>[		<code>[
	"#PLAYERS", {{~~codecomment~~\|// The uppermost class containing information about the players}}		"#PLAYERS", {{cc\|The uppermost class containing information about the players}}
	[		[
	"#1234", {{~~codecomment~~\|// An imaginary user id to ~~indentify~~ a player ~~wihtout~~ doubt}}		"#1234", {{cc\|An imaginary user id to identify a player without doubt}}
	[		[
	{{~~codecomment~~\|// Following here are some stats that the player has}}		{{cc\|Following here are some stats that the player has}}
	"&NAME", "Bob",		"&NAME", "Bob",
	"&KILLS", 20,		"&KILLS", 20,
	"&RANK", "~~Seargent~~"		"&RANK", "Sergeant"
	],		],
	"#5678",		"#5678",
Line 69:		Line 69:
	[[private]] _rank = [TAG_database, ["players", _puid, "rank"], "PRIVATE"] [[call]] [[BIS_fnc_dbValueReturn]];		[[private]] _rank = [TAG_database, ["players", _puid, "rank"], "PRIVATE"] [[call]] [[BIS_fnc_dbValueReturn]];
	[[hint]] _rank;		[[hint]] _rank;
	If you ever worked with configs then you might notice the ~~similiarity~~ between the ~~path~~ array and the ~~path to a~~ config. This is how you access a config value:		If you ever worked with configs then you might notice the similarity between the array and the config paths. This is how you access a config value:
	[[getText]] ([[missionConfigfile]] >> "Players" >> [[getPlayerUID]] [[player]] >> "rank");		[[getText]] ([[missionConfigfile]] >> "Players" >> [[getPlayerUID]] [[player]] >> "rank");
	So while the config is not editable the database is, which leads us to...		So while the config is not editable the database is, which leads us to...

Lou Montana: Add SideTOC and wikicode format

2020-03-16T14:46:15Z

Add SideTOC and wikicode format

Show changes

← Older revision		Revision as of 13:27, 2 January 2021
Line 82:		Line 82:


	[[Category:Scripting ~~Topics~~]]		[[Category:Arma Scripting Tutorials]]