Farming Restriction

Farming Restriction 1.0.0

Sign in to download
Blocks all farming actions while building blocked, including trees, ore, and planters
Documentation License Version History Discussion
This Rust plugin blocks all farming activities for players who are building blocked (not authorized to a nearby tool cupboard). That includes gathering trees, ores, loose collectibles like hemp, and even crops from planters. If they're not authorized, they can't farm.




Permissions

  • farmingrestriction.bypass - Allows a player to farm even if they are building blocked.

Configuration

JSON: 
{
  "Version": "1.0.0",
  "Block Tree Farming When Building Blocked": true,
  "Block Ore Node Farming When Building Blocked": true,
  "Block Collectible Pickup When Building Blocked": true,
  "Block Planter Harvest When Building Blocked": true
}
  • Block Tree Farming When Building Blocked - Blocks hitting trees when building blocked.
  • Block Ore Node Farming When Building Blocked - Blocks hitting ore nodes when building blocked.
  • Block Collectible Pickup When Building Blocked - Blocks picking up collectibles (like hemp, stone, metal fragments) while building blocked.
  • Block Planter Harvest When Building Blocked - Blocks harvesting plants from growables/planters while building blocked.

Localization

JSON: 
{
  "Blocked.FarmingDenied": "You cannot farm here (building blocked)."
}
Author
VisEntities
Downloads
3
First release
Last update

Ratings

0.00 star(s) 0 reviews
Donate Contribute on GitHub

Also by VisEntities

Back
Top
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.
Cart

Cart

Total -