Join the Game4Freak Discord Get exclusive plugin sneak peeks, talk directly with VisEntities, never miss important updates, and unlock special discount codes!

Ceiling Left Hanging in the Air After Support Was Removed

Placement of boxes and planters.
Players inside tree zones are given creative permissions, otherwise they wouldn't be able to build because jungle vines normally block building around those trees. It's intended so players can build tree houses. Because of that they can also do things like placing entities inside each other... you could consider that a small perk of building on trees lol

Ceilings hanging in the air.
The floating block might be related to flying around in noclip/vanish and repeatedly entering and leaving the tree build zone, which could potentially interfere with the creative permission being granted and removed. I'm not certain if that's the cause though, I'll take a closer look and see if I can reproduce it. If it is related to that, it likely wouldn't affect regular players during normal gameplay
 
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