VEIN Loot Respawn Troubleshooting
Empty containers can be a world rule, a timer, a location state, a build change, or an unsupported assumption about the config. The public dedicated-server reference does not publish a permanent loot-key table, so verify the current control before editing an INI.
Run a controlled test
- Record the branch, build, world, location, and time the container was checked.
- Confirm another player sees the same result.
- Check the current panel or generated configuration for an explicitly named loot/respawn control.
- Change one supported value in a test copy, then restart cleanly.
- Return to the same location and compare the result after the expected game-time or server-time interval.
Separate the likely causes
| Observation | Next check |
|---|---|
| One container is empty | Compare nearby containers and whether the area/world was recently loaded. |
| All containers stay empty | Check the active world, current setting, build, and logs before changing the host. |
| Only a migrated world is affected | Test a fresh world and keep the original save untouched. |
| Players disagree | Compare client builds, connection state, and whether the observation is replicated. |
What not to paste
Do not rely on an invented LootManager section, guessed multipliers, or a timer copied from an Unreal game with a similar genre. If the current package exposes no documented control, report the reproducible behavior and use the normal in-game rules.
Performance and fairness
More loot or faster respawn can change the server workload and the group's economy. Announce any change, back up first, and monitor CPU, memory, save duration, and player feedback on a persistent world.
Related guides
Host a persistent VEIN world with current panel options and backups.