Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
^"setup parse"
^"Chat commands start with a [ICODE]/[/ICODE], while console commands can be entered directly in the F1 console or server console. Use find [ICODE]<keyword>[/ICODE] in console to search for available commands related to the plugin. Parameters in [ICODE]< >[/ICODE] are required, while [ICODE][ ][/ICODE] are optional."
^"after toc marker extraction"
^"Chat commands start with a <code class="bbCodeInline">/</code>, while console commands can be entered directly in the F1 console or server console. Use find <code class="bbCodeInline"><keyword></code> in console to search for available commands related to the plugin. Parameters in <code class="bbCodeInline">< ></code> are required, while <code class="bbCodeInline">[ ]</code> are optional."
^"after content diving"
^"Chat commands start with a <code class="bbCodeInline">/</code>, while console commands can be entered directly in the F1 console or server console. Use find <code class="bbCodeInline"><keyword></code> in console to search for available commands related to the plugin. Parameters in <code class="bbCodeInline">< ></code> are required, while <code class="bbCodeInline">[ ]</code> are optional."
^"setup parse"
^"This plugin uses Oxide's permission system. Grant or revoke permissions using [ICODE]oxide.grant[/ICODE] and [ICODE]oxide.revoke[/ICODE]. You can assign them to individual players or groups using their Steam id or group name."
^"after toc marker extraction"
^"This plugin uses Oxide's permission system. Grant or revoke permissions using <code class="bbCodeInline">oxide.grant</code> and <code class="bbCodeInline">oxide.revoke</code>. You can assign them to individual players or groups using their Steam id or group name."
^"after content diving"
^"This plugin uses Oxide's permission system. Grant or revoke permissions using <code class="bbCodeInline">oxide.grant</code> and <code class="bbCodeInline">oxide.revoke</code>. You can assign them to individual players or groups using their Steam id or group name."
^"setup parse"
^"Settings are stored in the config file found under the [ICODE]config/[/ICODE] directory. You can edit this file manually, then reload the plugin to apply your changes."
^"after toc marker extraction"
^"Settings are stored in the config file found under the <code class="bbCodeInline">config/</code> directory. You can edit this file manually, then reload the plugin to apply your changes."
^"after content diving"
^"Settings are stored in the config file found under the <code class="bbCodeInline">config/</code> directory. You can edit this file manually, then reload the plugin to apply your changes."
^"setup parse"
^"Persistent data is saved in the [ICODE]data/[/ICODE] directory. This includes things like saved settings, usage stats, or player progress depending on the plugin. Deleting a data file will reset stored progress or customizations."
^"after toc marker extraction"
^"Persistent data is saved in the <code class="bbCodeInline">data/</code> directory. This includes things like saved settings, usage stats, or player progress depending on the plugin. Deleting a data file will reset stored progress or customizations."
^"after content diving"
^"Persistent data is saved in the <code class="bbCodeInline">data/</code> directory. This includes things like saved settings, usage stats, or player progress depending on the plugin. Deleting a data file will reset stored progress or customizations."
^"setup parse"
^"Language files are located in the [ICODE]lang/[/ICODE] folder. To translate messages, copy the [ICODE]en.json[/ICODE] file into your target language folder (e.g. [ICODE]fr[/ICODE], [ICODE]de[/ICODE]) and edit the values. Reload the plugin after changes to apply new messages."
^"after toc marker extraction"
^"Language files are located in the <code class="bbCodeInline">lang/</code> folder. To translate messages, copy the <code class="bbCodeInline">en.json</code> file into your target language folder (e.g. <code class="bbCodeInline">fr</code>, <code class="bbCodeInline">de</code>) and edit the values. Reload the plugin after changes to apply new messages."
^"after content diving"
^"Language files are located in the <code class="bbCodeInline">lang/</code> folder. To translate messages, copy the <code class="bbCodeInline">en.json</code> file into your target language folder (e.g. <code class="bbCodeInline">fr</code>, <code class="bbCodeInline">de</code>) and edit the values. Reload the plugin after changes to apply new messages."
^"setup parse"
^"This section lists public methods exposed by the plugin for use in other plugins. You can call these via the [ICODE]CallHook[/ICODE] method. Ensure the plugin is loaded before calling its API to avoid null reference errors."
^"after toc marker extraction"
^"This section lists public methods exposed by the plugin for use in other plugins. You can call these via the <code class="bbCodeInline">CallHook</code> method. Ensure the plugin is loaded before calling its API to avoid null reference errors."
^"after content diving"
^"This section lists public methods exposed by the plugin for use in other plugins. You can call these via the <code class="bbCodeInline">CallHook</code> method. Ensure the plugin is loaded before calling its API to avoid null reference errors."
^"setup parse"
^"These are custom hooks that other plugins can listen for. Simply define a method with the same name and expected parameters in your plugin to handle the event. Hooks are triggered at key moments and are useful for extending or reacting to plugin behavior."
^"after toc marker extraction"
^"These are custom hooks that other plugins can listen for. Simply define a method with the same name and expected parameters in your plugin to handle the event. Hooks are triggered at key moments and are useful for extending or reacting to plugin behavior."
^"after content diving"
^"These are custom hooks that other plugins can listen for. Simply define a method with the same name and expected parameters in your plugin to handle the event. Hooks are triggered at key moments and are useful for extending or reacting to plugin behavior."
^"setup parse"
^"These hooks are injected into the game's code using Harmony. They let the plugin run code at key points in the game's internal logic. You can return values to block or modify behavior. Use with caution — these are powerful and can affect core mechanics."
^"after toc marker extraction"
^"These hooks are injected into the game's code using Harmony. They let the plugin run code at key points in the game's internal logic. You can return values to block or modify behavior. Use with caution — these are powerful and can affect core mechanics."
^"after content diving"
^"These hooks are injected into the game's code using Harmony. They let the plugin run code at key points in the game's internal logic. You can return values to block or modify behavior. Use with caution — these are powerful and can affect core mechanics."
You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser.
Chat commands start with a /, while console commands can be entered directly in the F1 console or server console. Use find <keyword> in console to search for available commands related to the plugin. Parameters in < > are required, while [ ] are optional.
This plugin uses Oxide's permission system. Grant or revoke permissions using oxide.grant and oxide.revoke. You can assign them to individual players or groups using their Steam id or group name.
Settings are stored in the config file found under the config/ directory. You can edit this file manually, then reload the plugin to apply your changes.
Persistent data is saved in the data/ directory. This includes things like saved settings, usage stats, or player progress depending on the plugin. Deleting a data file will reset stored progress or customizations.
Language files are located in the lang/ folder. To translate messages, copy the en.json file into your target language folder (e.g. fr, de) and edit the values. Reload the plugin after changes to apply new messages.
This section lists public methods exposed by the plugin for use in other plugins. You can call these via the CallHook method. Ensure the plugin is loaded before calling its API to avoid null reference errors.
These are custom hooks that other plugins can listen for. Simply define a method with the same name and expected parameters in your plugin to handle the event. Hooks are triggered at key moments and are useful for extending or reacting to plugin behavior.
These hooks are injected into the game's code using Harmony. They let the plugin run code at key points in the game's internal logic. You can return values to block or modify behavior. Use with caution — these are powerful and can affect core mechanics.
