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
Interface 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.
Common Error Patterns
attempt to index a nil value— usually a missing config value or an unregistered itemSCRIPT ERROR— a Lua error; the message names the file and line[oxmysql]errors — database connection or missing tables (re-checksql/install.sql)
Actions Seem Ignored
If clicking buttons does nothing occasionally, you may be hitting the anti-spam rate limits. These are the server-side cooldowns:
| Action | Cooldown |
|---|---|
| Place/remove equipment (printers, benches, tables) | 1 second |
| Load USB | 1 second |
| Start/collect print | 1 second |
| Install upgrade | 1 second |
| Start/complete craft | 1 second |
| Select/eject blueprint | 0.5 seconds |
| Browse USB items | 0.5 seconds |
Getting Help
If none of the above solves your issue:
- Reproduce the problem and copy any console lines mentioning
oxide-weaponprinting - Verify all items are registered correctly in your framework
- Confirm
sql/install.sqlwas imported successfully - Contact Oxide Studios support with the console output and a description of what you did
Support
Need more help?
- Discord: https://discord.gg/dZ6q8FyGhm
- Website: https://www.oxidestudios.dev/
- o-link (required abstraction layer): https://github.com/Oxide-Studios/o-link