Not an Issue Hard to Jump from Tree to Ladder Hatch

Papster

Supporter
Getting from the tree to the ladder on the hatch is extremely challenging and, for me, I have success less than 10% of the times I try. Perhaps this is not the best method for access but it would be nice if it could work well. Trying to place a regular ladder does not work at all.
 

Attachments

Hmm, I'm not sure this is something the plugin should manage, it just provides the foundation, what players do with it, like how they build is really up to them, but I'm open to suggestions if you have something specific in mind
 
Understood. For me it is not the end of the world to struggle with ladder hatch entry. I think the ladder hatches are inconsistent due to inconsistencies in the trees so pretty difficult to handle that. In the video the entry at the left is what I have found to be the best access. Just a normal door installed inside, and at a 90° to the default platform.
 
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