Animal Pelts

Animal Pelts 1.4.1

Gives players custom pelts when skinning animal corpses
Documentation License Changelog (6) Reviews (3) Version History Discussion

1.4.1

  • You no longer need animalpelts.all to receive pelts. Pelts are now obtainable by default unless a specific permission is set for them. If a pelt has a permission, players must have either that permission or animalpelts.all to get it.
Please review the 1.4.0 update for the full list of new features.
  • Like
Reactions: (Manky)sieve

1.4.0

  • Added per-pelt permission support, allowing you to assign specific permissions for each pelt like animalpelts.bear, or leave the field empty to make the pelt available to all players.
  • Renamed animalpelts.use to animalpelts.all, which now acts as a global permission that grants access to all pelts, even those with individual restrictions.
  • Added “human” as an accepted keyword in the pelt.give command for giving the Human Pelt (in addition to “player”).
  • Like
Reactions: (Manky)sieve

1.3.0

  • Added config option to block Human Pelt drops when harvesting teammates or your own corpse.
  • Changed pelts to use an item that isn't part of any crafting recipes. This prevents them from being accidentally consumed when players craft.
  • Like
Reactions: (Manky)sieve and Evil_Orko

1.2.0

  • You can now get a Human Pelt from player corpses.
Human Skin (Light).png
  • Haha
  • Wow
Reactions: (Manky)sieve and Evil_Orko

1.1.1

  • Fixed null error in OnEntityKill.

1.1.0

  • Added support for multiple prefab variants per animal to improve compatibility with alternate corpse names (like the snake).
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

Cart

Total -