Dynamic Third Person (Legacy Thread)

Return to plugin
Recent First Highest Voted
New bug found. When you die in third person, the death screen turns black and you cant see anything. You can hover over where the buttons should be but cannot see anything. Is there a way to switch the player back to first person upon death?

Scratch that. Something else is the cause.
 
Last edited:
Upvote 0 Downvote
threefourseven said:
Ok, thank you I will wait for you to update it then!
Click to expand...
So I ran a lot of tests but unfortunately no luck, it was working a few months ago, but it looks like recent Rust updates have caused it to stop. I'll put this on hold for now and revisit it later, though I'm worried it's another thing blocked by Facepunch :/ I'll keep you updated
 
Upvote 0 Downvote
A SMALL IDEA IF POSSIBLE , ADDING A OPTION WHEN ITS ALWAYS 3RD BUT WHEN HOLDING A ITEM FROM HOTBAR OR DRIVING A VEHICULE EXCEPT FOR HORSE IT GOES BACK TO FIRST PERSON AUTOMATIC AND KEEPS SWITCHING ... IS THAT POSSIBLE ?
 
Upvote 0 Downvote
You must log in or register to reply here.
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. Make sure 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 -