No AFK Recycler

No AFK Recycler 1.1.0

Sign in to download
Prevents players from staying afk while using recyclers
Documentation License Changelog (1) Version History Discussion
This plugin ensures that players can't stay afk while using recyclers by automatically kicking them after a set period of inactivity.





How it Works

When a player starts using a recycler, the plugin sets a timer based on the configured duration. If the player is inactive for the specified time, they are automatically removed from the recycler, ending their looting session. However, each time an item is recycled before the timer expires, the timer resets, giving the player more time to continue using the recycler. Once the player leaves or finishes, the timer stops

Permissions

  • noafkrecycler.ignore - Players with this permission will not be kicked for inactivity while using recyclers.

Configuration

JSON: 
{
  "Version": "1.0.0",
  "Duration Until Kicking Player From Recycler For Inactivity": 300.0
}
  • Duration Until Kicking Player From Recycler For Inactivity - Defines how long in seconds, a player can stay idle while using a recycler before being automatically kicked from it.
Author
VisEntities
Downloads
13
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate Contribute on GitHub

Also by VisEntities

Latest updates

  1. 1.1.0

    Items from the recycler are now automatically moved to the player's inventory when they are...
Read more…
Back
Top
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.
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.
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. Make sure 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.
Cart

Cart

Total -