🧹 Silly ClearProps – Clear Stuck Player Props (RedM / Standalone)
A cup or another animation prop is still attached to your character after an animation ends? Silly ClearProps gives players a simple /clearprops command to clean up attached object props on their own character.
Version: 1.0.0
✨ Features
- 🧹 One-command cleanup for props attached to the player's own character.
- 🔗 Nested attachments are included, with several cleanup passes for stubborn objects.
- 🌐 Multiplayer cleanup asks clients to remove attachments and requests server assistance for eligible networked objects.
- 🔫 Weapon protection covers built-in weapon, component and tool models, plus the client's equipped weapon slots.
- ⏱️ Configurable cooldown, set to 3 seconds by default.
- 🧩 Standalone: no framework, inventory, items or database setup required.
📦 Requirements
- A RedM server.
- OneSync / server-visible entity state for server-assisted cleanup of networked objects.
The resource can run alongside VORP, RSGCore or another framework. It does not use framework APIs or an inventory bridge.
⚙️ Installation
-
Copy the inner
Silly_ClearPropsfolder into your server's resources directory. It must containfxmanifest.lua,config.lua,client.luaandserver.lua. -
Add the resource to
server.cfg:ensure Silly_ClearProps -
Adjust config.lua if you want a different command or cooldown.
-
Start the resource and use
/clearpropsin game.
There are no item imports, SQL files or framework dependencies to install.
🎮 How to Use
- Finish or stop the activity that created the prop.
- Enter
/clearpropsin chat. - Attached object props on your character are checked and eligible objects are removed.
The command is available to all players and only cleans the caller's character. It has no target-player argument, console mode or built-in admin permission requirement. Repeated calls are limited by the configured cooldown.
🔧 Configuration
Both settings are in config.lua:
| Setting | Default | Purpose |
|---|---|---|
| Config.Command | 'clearprops' | Command name without the leading slash. |
| Config.CooldownSeconds | 3 | Minimum time between a player's cleanup requests, in seconds. |
For example, setting Config.Command = 'cleanprops' changes the command to /cleanprops.
🧩 Framework and Language Support
Framework-independent: the cleanup works without VORP or RSGCore integrations.
The resource has no player-facing notifications, menu or locale files. There is no language selector; the command name can be changed in the configuration.
📝 Practical Notes
- Cleanup can also remove legitimate object props from an activity that is still running. Stop that activity before using the command.
- Clothing and ped components are not object props and are outside this cleanup.
- If another resource continuously creates a prop again, stop its active function as well.
- Built-in model protection and equipped-weapon checks reduce unwanted weapon removal. Custom models outside the protected list are not covered by a blanket guarantee.
- The resource does not change inventory items or ammunition.
- Cleanup of networked objects depends on entity ownership, control and server-visible state.
The manifest is available in fxmanifest.lua. The included weapons.lua is not loaded by the current manifest.
💬 Support
Need help or want more scripts?

