Rust:Тонкости администрирования сервера uMod или Oxide
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head> <meta http-equiv=Content-Type content="text/html; charset=windows-1251"> <meta name=ProgId content=Word.Document> <meta name=Generator content="Microsoft Word 15"> <meta name=Originator content="Microsoft Word 15"> <link rel=File-List href="Start.files/filelist.xml"> <link rel=Edit-Time-Data href="Start.files/editdata.mso"> <link rel=themeData href="Start.files/themedata.thmx"> <link rel=colorSchemeMapping href="Start.files/colorschememapping.xml"> <style> </style> </head>
<body lang=EN-US link=blue vlink="#954F72" style='tab-interval:36.0pt'>
Start<o:p></o:p>
Installation<o:p></o:p>
Server requirements<o:p></o:p>
The uMod platform requirements vary depending on the game server.<o:p></o:p>
More information about uMod support for specific games may be found on the <a href="https://umod.org/documentation/umod/game-support">Game Support</a> page.<o:p></o:p>
Installing uMod<o:p></o:p>
Via Direct Download<o:p></o:p>
- Download the uMod version <a href="https://umod.org/games">specific to your game</a>.<o:p></o:p>
- Copy the files over your existing server installation<o:p></o:p>
Plugins<o:p></o:p>
Plugins are self-contained bits of code which modify game server behavior.<o:p></o:p>
For more information about plugins, view the <a href="https://umod.org/documentation/umod/plugins/getting-started">Plugins - Getting Started</a> page.<o:p></o:p>
<a href="https://umod.org/plugins">View all available plugins</a><o:p></o:p>
Extensions<o:p></o:p>
Extensions are generally large projects which add functionality to uMod or make substantial changes to a server.<o:p></o:p>
<a href="https://umod.org/extensions">View all available extensions</a><o:p></o:p>
- <a href="new%202.html#config-directory">Config directory</a><o:p></o:p>
- <a href="new%202.html#file-name">File name</a><o:p></o:p>
- <a href="new%202.html#valid-json">Valid JSON</a><o:p></o:p>
- <a href="new%202.html#applying-changes">Applying changes</a><o:p></o:p>
Plugin configuration<o:p></o:p>
Most plugins will generate a JSON configuration file once loaded. With this file, a server owner may change how a plugin works.<o:p></o:p>
Config directory<o:p></o:p>
Configuration files are found in the config folder which is located by default in oxide/config (unless the server host has moved it).<o:p></o:p>
File name<o:p></o:p>
A plugin configuration file will have the same name as the plugin itself.<o:p></o:p>
For example, a plugin that is installed as MyPlugin.cs (if it is configurable) will be accompanied by a JSON file named MyPlugin.json<o:p></o:p>
Do not rename the configuration file or change the file extension.<o:p></o:p>
If a plugin is installed but not configurable, no configuration file will be present.<o:p></o:p>
If a plugin is configurable but no configuration file is available, the plugin may be broken; in this case, check the log files under the oxide/logs directory for errors.<o:p></o:p>
Valid JSON<o:p></o:p>
All plugin configuration files are saved as JSON (JavaScript Object Notation). Configuration files must be valid JSON. Use a validator such as <a href="https://jsonlint.com">jsonlint.com</a> to ensure the configuration is valid JSON.<o:p></o:p>
Applying changes<o:p></o:p>
After making changes to a plugin configuration file, reload the plugin in the server console by using the oxide.reload command. For example:<o:p></o:p>
oxide.reload MyPlugin<o:p></o:p>
<o:p> </o:p>
Continue to <a href="https://umod.org/documentation/umod/plugins/permissions">setting permissions</a>..<o:p></o:p>
Plugin installation<o:p></o:p>
Installing uMod plugins usually only takes a few mouse clicks.<o:p></o:p>
Server requirements<o:p></o:p>
To install the plugin on the server, the server provider must support Oxide 2.0 or higher, else the plugins will not load or do anything.<o:p></o:p>
If the server is not online, start it. Then, check that Oxide is fully installed by testing the oxide.version chat or console command.<o:p></o:p>
Download the source code<o:p></o:p>
Download a plugin from the <a href="https://umod.org/plugins">plugins page</a>;<o:p></o:p>
Do not rename the plugin or change the file extension.<o:p></o:p>
Remote server<o:p></o:p>
If the server is not hosted locally, connect to the server via an FTP client. If unsure of the FTP details, please contact the server host.<o:p></o:p>
Plugins directory<o:p></o:p>
Find the plugins folder which is located by default at oxide/plugins if it has not been changed by the server host<o:p></o:p>
Upload the source code<o:p></o:p>
Upload the plugin file into the "plugins" folder and it will be loaded automatically if Oxide is currently installed<o:p></o:p>
Continue to <a href="https://umod.org/documentation/umod/plugins/configuration">configuring the plugin</a>..<o:p></o:p>
Updating<o:p></o:p>
If a plugin is already installed and an update is available simply overwrite the original (.cs) file and the new version will be loaded automatically.<o:p></o:p>
Plugin configuration<o:p></o:p>
Most plugins will generate a JSON configuration file once loaded. With this file, a server owner may change how a plugin works.<o:p></o:p>
Config directory<o:p></o:p>
Configuration files are found in the config folder which is located by default in oxide/config (unless the server host has moved it).<o:p></o:p>
File name<o:p></o:p>
A plugin configuration file will have the same name as the plugin itself.<o:p></o:p>
For example, a plugin that is installed as MyPlugin.cs (if it is configurable) will be accompanied by a JSON file named MyPlugin.json<o:p></o:p>
Do not rename the configuration file or change the file extension.<o:p></o:p>
If a plugin is installed but not configurable, no configuration file will be present.<o:p></o:p>
If a plugin is configurable but no configuration file is available, the plugin may be broken; in this case, check the log files under the oxide/logs directory for errors.<o:p></o:p>
Valid JSON<o:p></o:p>
All plugin configuration files are saved as JSON (JavaScript Object Notation). Configuration files must be valid JSON. Use a validator such as <a href="https://jsonlint.com">jsonlint.com</a> to ensure the configuration is valid JSON.<o:p></o:p>
Applying changes<o:p></o:p>
After making changes to a plugin configuration file, reload the plugin in the server console by using the oxide.reload command. For example:<o:p></o:p>
oxide.reload MyPlugin<o:p></o:p>
<o:p> </o:p>
Continue to <a href="https://umod.org/documentation/umod/plugins/permissions">setting permissions</a>..<o:p></o:p>
- <a href="new%202.html#players">Players</a> <o:p></o:p>
- <a href="new%202.html#grant-a-permission-to-an-individual-player">Grant a permission to an individual player</a><o:p></o:p>
- <a href="new%202.html#revoke-a-permission-from-an-individual-player">Revoke a permission from an individual player</a><o:p></o:p>
- <a href="new%202.html#show-a-players-permissions">Show a player's permissions</a><o:p></o:p>
- <a href="new%202.html#showing-which-player-or-group-has-a-permission">Showing which player or group has a permission</a><o:p></o:p>
- <a href="new%202.html#groups">Groups</a> <o:p></o:p>
- <a href="new%202.html#grant-a-permission-to-an-entire-group">Grant a permission to an entire group</a><o:p></o:p>
- <a href="new%202.html#revoke-a-permission-from-a-group">Revoke a permission from a group</a><o:p></o:p>
- <a href="new%202.html#adding-a-player-to-an-existing-group">Adding a player to an existing group</a><o:p></o:p>
- <a href="new%202.html#removing-a-player-from-an-existing-group">Removing a player from an existing group</a><o:p></o:p>
- <a href="new%202.html#adding-an-entirely-new-group">Adding an entirely new group</a><o:p></o:p>
- <a href="new%202.html#removing-an-existing-group">Removing an existing group</a><o:p></o:p>
- <a href="new%202.html#setting-the-title-or-rank-of-a-group">Setting the title or rank of a group</a><o:p></o:p>
- <a href="new%202.html#setting-the-parent-group-of-another-group">Setting the parent group of another group</a><o:p></o:p>
- <a href="new%202.html#showing-a-groups-members-and-permissions">Showing a group's members and permissions</a><o:p></o:p>
- <a href="new%202.html#showing-all-groups-or-permissions">Showing all groups or permissions</a><o:p></o:p>
- <a href="new%202.html#using-wildcards">Using wildcards</a><o:p></o:p>
- <a href="new%202.html#conclusion">Conclusion</a><o:p></o:p>
Permissions<o:p></o:p>
Permissions allows server owners to give players unique abilities and benefits on their servers.<o:p></o:p>
Administering permissions is easy; simply enter the desired command and you're done! If your server does not have a console, you can use any compatible RCON tool or remote console to send the commands to the server. Most Oxide/uMod-supported games also support the permission commands in the chat, or will soon.<o:p></o:p>
For this guide, the permission epicstuff.use will be used as an example. Keep in mind that permissions only exist if provided by a plugin or Oxide/uMod itself.<o:p></o:p>
By default, the groups that are created by Oxide/uMod are: admin and default. These can be changed by editing those under the umod.config.json file. The admin group will automatically be assigned to players that are recognized as admin by the server. The "default" group will automatically be assigned to ALL players that connect to the server.<o:p></o:p>
Players<o:p></o:p>
Grant a permission to an individual player<o:p></o:p>
oxide.grant player Wulf epicstuff.use<o:p></o:p>
Revoke a permission from an individual player<o:p></o:p>
oxide.revoke player Wulf epicstuff.use<o:p></o:p>
Show a player's permissions<o:p></o:p>
oxide.show player Wulf<o:p></o:p>
Showing which player or group has a permission<o:p></o:p>
Sometimes this command is helpful when tracking down who has a permission.<o:p></o:p>
oxide.show perm epicstuff.use<o:p></o:p>
Groups<o:p></o:p>
Grant a permission to an entire group<o:p></o:p>
oxide.grant group admin epicstuff.use<o:p></o:p>
Revoke a permission from a group<o:p></o:p>
oxide.revoke group admin epicstuff.use<o:p></o:p>
Adding a player to an existing group<o:p></o:p>
Adding a player to a group will give them all of the permissions assigned to that group.<o:p></o:p>
oxide.usergroup add Wulf admin<o:p></o:p>
Removing a player from an existing group<o:p></o:p>
Removing a player from a group will remove from them all of the permissions assigned to that group.<o:p></o:p>
oxide.usergroup remove Wulf admin<o:p></o:p>
Adding an entirely new group<o:p></o:p>
oxide.group add vip<o:p></o:p>
oxide.group add vip VIP 0<o:p></o:p>
Removing an existing group<o:p></o:p>
oxide.group remove vip<o:p></o:p>
Setting the title or rank of a group<o:p></o:p>
The group title is usually a short description of a group, sometimes used for chat titles. The rank is a number which sorts a group based on its importance.<o:p></o:p>
oxide.group set vip "[VIP Member]"<o:p></o:p>
oxide.group set vip "[VIP Member]" 1<o:p></o:p>
Setting the parent group of another group<o:p></o:p>
A group will inherit all permissions from its parent group.<o:p></o:p>
oxide.group parent admin default<o:p></o:p>
Showing a group's members and permissions<o:p></o:p>
oxide.show group admin<o:p></o:p>
Showing all groups or permissions<o:p></o:p>
To show all of the permission groups, simple use the command below.<o:p></o:p>
oxide.show groups<o:p></o:p>
The show all of the registered permissions from plugins and Oxide/uMod, use the command below.<o:p></o:p>
oxide.show perms<o:p></o:p>
Using wildcards<o:p></o:p>
A wildcard is something that covers multiple things at once time. For permissions, this is the * symbol. You can use the wildcard (*) to grant multiple permissions at one time. This can be done with all permissions or per plugin based on prefix.<o:p></o:p>
oxide.grant group admin *<o:p></o:p>
oxide.grant player Wulf umod.*<o:p></o:p>
Conclusion<o:p></o:p>
The same commands are also available with the "o." prefix (ex. "o.grant").<o:p></o:p>
That's the basics to permissions for Oxide/uMod. Permissions give you a fantastic way to manage staff without worrying about them abusing powers from the game's admin functionality (such as flight, noclip, super speed, etc.) so they can still enjoy the game but also help monitor your server at the same time.<o:p></o:p>
- <a href="new%202.html#data-directory">Data directory</a><o:p></o:p>
- <a href="new%202.html#file-names">File names</a><o:p></o:p>
- <a href="new%202.html#valid-json">Valid JSON</a><o:p></o:p>
Data Files<o:p></o:p>
Data files are JSON files that plugins may use to store arbitrary data.<o:p></o:p>
Data directory<o:p></o:p>
Data files may be found in the data folder which located by default in oxide/data (unless the server host has moved it).<o:p></o:p>
File names<o:p></o:p>
Data files do not follow any naming convention, a plugin author may specify any name when creating a data file.<o:p></o:p>
It is recommended to plugin authors, when creating a large number of data files, to create them in a subdirectory specific to their plugin.<o:p></o:p>
Valid JSON<o:p></o:p>
All plugin data files are saved as JSON (JavaScript Object Notation). Data files must be valid JSON. If editing a data file manually, use a validator such as <a href="https://jsonlint.com">jsonlint.com</a> to ensure the data file is valid JSON.<o:p></o:p>
Server requirements<o:p></o:p>
The uMod platform requirements vary depending on the game server.<o:p></o:p>
More information about uMod support for specific games may be found on the <a href="https://umod.org/documentation/umod/game-support">Game Support</a> page.<o:p></o:p>
Installing uMod<o:p></o:p>
Via Direct Download<o:p></o:p>
- Download the uMod version <a href="https://umod.org/games">specific to your game</a>.<o:p></o:p>
- Copy the files over your existing server installation<o:p></o:p>
Plugins<o:p></o:p>
Plugins are self-contained bits of code which modify game server behavior.<o:p></o:p>
For more information about plugins, view the <a href="https://umod.org/documentation/umod/plugins/getting-started">Plugins - Getting Started</a> page.<o:p></o:p>
<a href="https://umod.org/plugins">View all available plugins</a><o:p></o:p>
Extensions<o:p></o:p>
Extensions are generally large projects which add functionality to uMod or make substantial changes to a server.<o:p></o:p>
<a href="https://umod.org/extensions">View all available extensions</a><o:p></o:p>
- <a href="new%202.html#config-directory">Config directory</a><o:p></o:p>
- <a href="new%202.html#file-name">File name</a><o:p></o:p>
- <a href="new%202.html#valid-json">Valid JSON</a><o:p></o:p>
- <a href="new%202.html#applying-changes">Applying changes</a><o:p></o:p>
Plugin configuration<o:p></o:p>
Most plugins will generate a JSON configuration file once loaded. With this file, a server owner may change how a plugin works.<o:p></o:p>
Config directory<o:p></o:p>
Configuration files are found in the config folder which is located by default in oxide/config (unless the server host has moved it).<o:p></o:p>
File name<o:p></o:p>
A plugin configuration file will have the same name as the plugin itself.<o:p></o:p>
For example, a plugin that is installed as MyPlugin.cs (if it is configurable) will be accompanied by a JSON file named MyPlugin.json<o:p></o:p>
Do not rename the configuration file or change the file extension.<o:p></o:p>
If a plugin is installed but not configurable, no configuration file will be present.<o:p></o:p>
If a plugin is configurable but no configuration file is available, the plugin may be broken; in this case, check the log files under the oxide/logs directory for errors.<o:p></o:p>
Valid JSON<o:p></o:p>
All plugin configuration files are saved as JSON (JavaScript Object Notation). Configuration files must be valid JSON. Use a validator such as <a href="https://jsonlint.com">jsonlint.com</a> to ensure the configuration is valid JSON.<o:p></o:p>
Applying changes<o:p></o:p>
After making changes to a plugin configuration file, reload the plugin in the server console by using the oxide.reload command. For example:<o:p></o:p>
oxide.reload MyPlugin<o:p></o:p>
<o:p> </o:p>
Continue to <a href="https://umod.org/documentation/umod/plugins/permissions">setting permissions</a>..<o:p></o:p>
Plugin installation<o:p></o:p>
Installing uMod plugins usually only takes a few mouse clicks.<o:p></o:p>
Server requirements<o:p></o:p>
To install the plugin on the server, the server provider must support Oxide 2.0 or higher, else the plugins will not load or do anything.<o:p></o:p>
If the server is not online, start it. Then, check that Oxide is fully installed by testing the oxide.version chat or console command.<o:p></o:p>
Download the source code<o:p></o:p>
Download a plugin from the <a href="https://umod.org/plugins">plugins page</a>;<o:p></o:p>
Do not rename the plugin or change the file extension.<o:p></o:p>
Remote server<o:p></o:p>
If the server is not hosted locally, connect to the server via an FTP client. If unsure of the FTP details, please contact the server host.<o:p></o:p>
Plugins directory<o:p></o:p>
Find the plugins folder which is located by default at oxide/plugins if it has not been changed by the server host<o:p></o:p>
Upload the source code<o:p></o:p>
Upload the plugin file into the "plugins" folder and it will be loaded automatically if Oxide is currently installed<o:p></o:p>
Continue to <a href="https://umod.org/documentation/umod/plugins/configuration">configuring the plugin</a>..<o:p></o:p>
Updating<o:p></o:p>
If a plugin is already installed and an update is available simply overwrite the original (.cs) file and the new version will be loaded automatically.<o:p></o:p>
Plugin configuration<o:p></o:p>
Most plugins will generate a JSON configuration file once loaded. With this file, a server owner may change how a plugin works.<o:p></o:p>
Config directory<o:p></o:p>
Configuration files are found in the config folder which is located by default in oxide/config (unless the server host has moved it).<o:p></o:p>
File name<o:p></o:p>
A plugin configuration file will have the same name as the plugin itself.<o:p></o:p>
For example, a plugin that is installed as MyPlugin.cs (if it is configurable) will be accompanied by a JSON file named MyPlugin.json<o:p></o:p>
Do not rename the configuration file or change the file extension.<o:p></o:p>
If a plugin is installed but not configurable, no configuration file will be present.<o:p></o:p>
If a plugin is configurable but no configuration file is available, the plugin may be broken; in this case, check the log files under the oxide/logs directory for errors.<o:p></o:p>
Valid JSON<o:p></o:p>
All plugin configuration files are saved as JSON (JavaScript Object Notation). Configuration files must be valid JSON. Use a validator such as <a href="https://jsonlint.com">jsonlint.com</a> to ensure the configuration is valid JSON.<o:p></o:p>
Applying changes<o:p></o:p>
After making changes to a plugin configuration file, reload the plugin in the server console by using the oxide.reload command. For example:<o:p></o:p>
oxide.reload MyPlugin<o:p></o:p>
<o:p> </o:p>
Continue to <a href="https://umod.org/documentation/umod/plugins/permissions">setting permissions</a>..<o:p></o:p>
- <a href="new%202.html#players">Players</a> <o:p></o:p>
- <a href="new%202.html#grant-a-permission-to-an-individual-player">Grant a permission to an individual player</a><o:p></o:p>
- <a href="new%202.html#revoke-a-permission-from-an-individual-player">Revoke a permission from an individual player</a><o:p></o:p>
- <a href="new%202.html#show-a-players-permissions">Show a player's permissions</a><o:p></o:p>
- <a href="new%202.html#showing-which-player-or-group-has-a-permission">Showing which player or group has a permission</a><o:p></o:p>
- <a href="new%202.html#groups">Groups</a> <o:p></o:p>
- <a href="new%202.html#grant-a-permission-to-an-entire-group">Grant a permission to an entire group</a><o:p></o:p>
- <a href="new%202.html#revoke-a-permission-from-a-group">Revoke a permission from a group</a><o:p></o:p>
- <a href="new%202.html#adding-a-player-to-an-existing-group">Adding a player to an existing group</a><o:p></o:p>
- <a href="new%202.html#removing-a-player-from-an-existing-group">Removing a player from an existing group</a><o:p></o:p>
- <a href="new%202.html#adding-an-entirely-new-group">Adding an entirely new group</a><o:p></o:p>
- <a href="new%202.html#removing-an-existing-group">Removing an existing group</a><o:p></o:p>
- <a href="new%202.html#setting-the-title-or-rank-of-a-group">Setting the title or rank of a group</a><o:p></o:p>
- <a href="new%202.html#setting-the-parent-group-of-another-group">Setting the parent group of another group</a><o:p></o:p>
- <a href="new%202.html#showing-a-groups-members-and-permissions">Showing a group's members and permissions</a><o:p></o:p>
- <a href="new%202.html#showing-all-groups-or-permissions">Showing all groups or permissions</a><o:p></o:p>
- <a href="new%202.html#using-wildcards">Using wildcards</a><o:p></o:p>
- <a href="new%202.html#conclusion">Conclusion</a><o:p></o:p>
Permissions<o:p></o:p>
Permissions allows server owners to give players unique abilities and benefits on their servers.<o:p></o:p>
Administering permissions is easy; simply enter the desired command and you're done! If your server does not have a console, you can use any compatible RCON tool or remote console to send the commands to the server. Most Oxide/uMod-supported games also support the permission commands in the chat, or will soon.<o:p></o:p>
For this guide, the permission epicstuff.use will be used as an example. Keep in mind that permissions only exist if provided by a plugin or Oxide/uMod itself.<o:p></o:p>
By default, the groups that are created by Oxide/uMod are: admin and default. These can be changed by editing those under the umod.config.json file. The admin group will automatically be assigned to players that are recognized as admin by the server. The "default" group will automatically be assigned to ALL players that connect to the server.<o:p></o:p>
Players<o:p></o:p>
Grant a permission to an individual player<o:p></o:p>
oxide.grant player Wulf epicstuff.use<o:p></o:p>
Revoke a permission from an individual player<o:p></o:p>
oxide.revoke player Wulf epicstuff.use<o:p></o:p>
Show a player's permissions<o:p></o:p>
oxide.show player Wulf<o:p></o:p>
Showing which player or group has a permission<o:p></o:p>
Sometimes this command is helpful when tracking down who has a permission.<o:p></o:p>
oxide.show perm epicstuff.use<o:p></o:p>
Groups<o:p></o:p>
Grant a permission to an entire group<o:p></o:p>
oxide.grant group admin epicstuff.use<o:p></o:p>
Revoke a permission from a group<o:p></o:p>
oxide.revoke group admin epicstuff.use<o:p></o:p>
Adding a player to an existing group<o:p></o:p>
Adding a player to a group will give them all of the permissions assigned to that group.<o:p></o:p>
oxide.usergroup add Wulf admin<o:p></o:p>
Removing a player from an existing group<o:p></o:p>
Removing a player from a group will remove from them all of the permissions assigned to that group.<o:p></o:p>
oxide.usergroup remove Wulf admin<o:p></o:p>
Adding an entirely new group<o:p></o:p>
oxide.group add vip<o:p></o:p>
oxide.group add vip VIP 0<o:p></o:p>
Removing an existing group<o:p></o:p>
oxide.group remove vip<o:p></o:p>
Setting the title or rank of a group<o:p></o:p>
The group title is usually a short description of a group, sometimes used for chat titles. The rank is a number which sorts a group based on its importance.<o:p></o:p>
oxide.group set vip "[VIP Member]"<o:p></o:p>
oxide.group set vip "[VIP Member]" 1<o:p></o:p>
Setting the parent group of another group<o:p></o:p>
A group will inherit all permissions from its parent group.<o:p></o:p>
oxide.group parent admin default<o:p></o:p>
Showing a group's members and permissions<o:p></o:p>
oxide.show group admin<o:p></o:p>
Showing all groups or permissions<o:p></o:p>
To show all of the permission groups, simple use the command below.<o:p></o:p>
oxide.show groups<o:p></o:p>
The show all of the registered permissions from plugins and Oxide/uMod, use the command below.<o:p></o:p>
oxide.show perms<o:p></o:p>
Using wildcards<o:p></o:p>
A wildcard is something that covers multiple things at once time. For permissions, this is the * symbol. You can use the wildcard (*) to grant multiple permissions at one time. This can be done with all permissions or per plugin based on prefix.<o:p></o:p>
oxide.grant group admin *<o:p></o:p>
oxide.grant player Wulf umod.*<o:p></o:p>
Conclusion<o:p></o:p>
The same commands are also available with the "o." prefix (ex. "o.grant").<o:p></o:p>
That's the basics to permissions for Oxide/uMod. Permissions give you a fantastic way to manage staff without worrying about them abusing powers from the game's admin functionality (such as flight, noclip, super speed, etc.) so they can still enjoy the game but also help monitor your server at the same time.<o:p></o:p>
- <a href="new%202.html#data-directory">Data directory</a><o:p></o:p>
- <a href="new%202.html#file-names">File names</a><o:p></o:p>
- <a href="new%202.html#valid-json">Valid JSON</a><o:p></o:p>
Data Files<o:p></o:p>
Data files are JSON files that plugins may use to store arbitrary data.<o:p></o:p>
Data directory<o:p></o:p>
Data files may be found in the data folder which located by default in oxide/data (unless the server host has moved it).<o:p></o:p>
File names<o:p></o:p>
Data files do not follow any naming convention, a plugin author may specify any name when creating a data file.<o:p></o:p>
It is recommended to plugin authors, when creating a large number of data files, to create them in a subdirectory specific to their plugin.<o:p></o:p>
Valid JSON<o:p></o:p>
All plugin data files are saved as JSON (JavaScript Object Notation). Data files must be valid JSON. If editing a data file manually, use a validator such as <a href="https://jsonlint.com">jsonlint.com</a> to ensure the data file is valid JSON.<o:p></o:p>
<o:p> </o:p>
</body>
</html>