Fallen Tree Remains

Fallen Tree Remains 1.2.0

Sign in to download
Leaves a dead log and stump after a tree is cut down, which can also be harvested
This Rust plugin adds a QoL to tree cutting by making trees leave behind a dead log and a stump when chopped down, instead of just disappearing.




Dead Logs

Dead logs are reflective of the tree's biome. For example, if you cut down a tree in the arctic biome, the spawned dead log will be covered in snow, blending with its surroundings. Furthermore, dead logs are spawned in the exact direction where the tree fell, adding to its realism.

There are 3 dead log prefab variations that spawn randomly for trees in each biome, except for trees in the arid biome such as palm trees, because there is no corresponding dead log prefab for this tree type.

Stumps

With the exception of trees in the arid biome, all trees will spawn a stump. The stump prefab is the same for all tree types.

Configuration

JSON:
{
  "Version": "1.1.0",
  "Chance To Spawn Snow Log": 100,
  "Chance To Spawn Dry Log": 100,
  "Chance To Spawn Wet Log": 100,
  "Chance To Spawn Stump": 100,
  "Spawn Wood Pile Instead Of Stump": false
}
Author
VisEntities
Downloads
111
First release
Last update

Ratings

5.00 star(s) 2 reviews

Also by VisEntities

Latest updates

  1. 1.2.0

    Jungle trees (kapok, trumpet, hura, and mauritia) now drop dry fallen logs just like other...
  2. 1.1.0

    Added a config option Spawn Wood Pile Instead Of Stump to spawn a wood pile instead of a stump...

Latest reviews

Another great plugin by VisEntites! Improves immersion and does what should always have happened when chopping down trees in Rust.
The logic conclusion when you chop down a tree. Excellent plugin!
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