Troubleshooting
Symptom-indexed checklists for common oxide-medical issues — startup, injuries, illness, treatment, damage and death, vitals, and integration.
Common problems, in the order people usually hit them.
Start here for almost anything: run /med test as an admin. It exercises the whole system against your own character and prints a pass/fail line per check to the server console. If those all pass, the system is working and the problem is usually configuration or a misunderstanding of the design.
Installation
Nothing Seems to Happen
Treatment
Damage and Death
Vitals and Performance
Integration
Where to Look for What Happened
oxide-medical logs through the o-link logger. Every record creation, condition added, updated, treated or removed, every cardiac arrest, every exemption change and every state-changing /med command writes a structured entry naming the character and the condition.
These print to your server console out of the box, tagged [INFO][oxide-medical][<category>], with warnings in yellow and errors in red. If you run a logging resource that provides the o-link logger, they route there instead.
Setting Config.Debug = true adds verbose diagnostic lines, including every wound report the client sends and the body part and class it resolved to — which is the fastest way to find out why a particular weapon is not producing the injury you expect.