Troubleshooting
Solutions for common issues with Oxide 3D Weapon Printing organized by problem domain.
Startup Issues
Placement Issues
Printing Issues
Assembly Issues
Durability Issues
Upgrade Issues
NUI Issues
General Debugging
Reading the Console Logs
The resource logs through Oxide's logging bridge. By default, notable events print to the server console looking like:
[INFO][oxide-weaponprinting][lifecycle] resource initialized
[ERROR][oxide-weaponprinting][printer] failed to delete 3d_printers rowErrors and warnings from this resource always show this way — when something misbehaves, search the console for oxide-weaponprinting.
If you run the free oxide-logger resource, you also get finer-grained logs (player actions, prints, crafts, upgrades), log files, and Discord log channels.
Check Rate Limiting
If actions seem to be ignored silently, you may be hitting the server-side rate limit. Default cooldowns:
| Action | Cooldown |
|---|---|
| Place/remove equipment (printers, benches, tables) | 1000ms |
| Load USB | 1000ms |
| Start/collect print | 1000ms |
| Install upgrade | 1000ms |
| Start/complete craft | 1000ms |
| Select/remove blueprint | 500ms |
| Browse USB items | 500ms |
Getting Help
When reporting issues, include the following information:
- Server framework (ESX, QBCore, QBx, etc.)
- o-link version
- ox_lib version
- Error messages from the server console (F8 or terminal)
- Steps to reproduce the issue
- Console lines mentioning
oxide-weaponprinting - Whether the issue involves printing, assembly, durability, or upgrades
Support
Need more help?
- Discord: https://discord.gg/dZ6q8FyGhm
- Website: https://www.oxidestudios.dev/
- o-link (required abstraction layer): https://github.com/WHEREISDAN/o-link