Not an Issue Support for Multiple Platforms on the Same Tree?

Papster

Supporter
It would be pretty cool if tree houses were able to be placed at different heights from the current default. For example, claim a tree and gain the default platform but build another one an equal distance higher. I assume players can still swng on a vine to a claimed tree so it would be nice if when they landed they were still below a tree house.

One more would be a command to remove ownership of trees somehow.
 
Not sure if I fully get what you mean, but players can just build up from the platform. It's just the starting point, they can extend it however they like, and if they don't want the lower levels they can remove them

View attachment Desktop 2025.05.22 - 12.20.00.57.mp4

One more would be a command to remove ownership of trees somehow.
Players only own the building parts placed on the platform, not the tree itself, the tree remains untouched, unless you meant the tree becoming unclaimed again so the platform can be respawned? if that's what you mean, then yeah, I can look into adding something for abandoned trees
 
Last edited:
Building above and then trying to destroy lower levels did not work for me. Destroying the lower levels caused all levels to disappear. Perhaps it had to do with the height. I was trying to build above the vine so someone could not easily swing from another tree and land on top of the build
 
Building above and then trying to destroy lower levels did not work for me. Destroying the lower levels caused all levels to disappear. Perhaps it had to do with the height. I was trying to build above the vine so someone could not easily swing from another tree and land on top of the build
Did you make sure Disable Tree Stability is set to true?
 
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