Before Opening a Ticket
Send these five things and most clothing issues are answered in one reply instead of five.
Difficulty: Reference · Affects: both
INFO
Search: support, ticket, help, contact, what to send, report a problem.
What to send
| Item | Detail |
|---|---|
| Product | Which Zaiders pack, and where it was purchased |
| Platform & build | Legacy or Enhanced, and your sv_enforceGameBuild value |
| Server version | FXServer artifact number |
| YMT count | Male, female, and creature metadata, across all resources — how to count |
| Symptom | Exactly when it happens: on join, on character load, on one item, one gender only |
Crash evidence
- The exact error line from the log, copied as text.
- The three-word crash hash, if there is one.
- The relevant
server.cfgexcerpt:sv_enforceGameBuild, anyincrease_pool_sizelines, and your clothingensureorder. - What changed immediately before it started — a new pack, a build change, an artifact update.
A short excerpt beats a full log. Copy the lines around the error, not the whole file.
Do first
Run the isolation steps and count your slots. Telling us "female character crashes, we are at 5 of 5 female slots on b3570" gets a real answer immediately. "It crashes" does not.
Never send
DANGER
License keys, server passwords, database credentials, or full unredacted config files.
