Suggestion Paste Bases in the Direction the Player Is Facing

Return to plugin
coresnap

coresnap

Supporter
When pasting in a base using copy/paste, the base always pastes facing the direction the player is facing - the direction the player was facing when copied (unless otherwise directed/specified when copying).
ie, if player was south of the building (behind it) and looking north (the front side) when copying the base, when pasting in the base, regardless of where the player is looking, the base will always spawn in the direction of where the player is facing.

When throwing a PFgrenade, the base always pastes facing north.
Would it be possible to implement this either by default or a config option to paste the base in using the direction the player is facing?
This would allow players to control the direction their base is facing. For now, obvi it's a trade-off for not having to build their own base. lol
The most pertinent use case I can provide for this is providing players with a HUGE non-symmetrical base that requires 'more' careful placement.

Is it also possible to add in ALL entities that were copied? ie, when copying base that had external walls, these do not paste when using grenade (these do show up when using cp plugin and native cp). Or is this possible and I'm not seeing it? I know there's an option for deployables, but this doesn't change my current paste (have tried multiple options).

Thank you, as always! Sorry for the onslaught of requests...but I do have one more you can shut down! :D
 
Recent First Highest Voted
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 -