Test quest rewards with a nearly full player inventory
A reward that works with empty pockets may behave differently when storage is almost full. Test delivery before advertising a valuable item reward to players.
Check the installed content
PikaMug Quests has its own quest editor and player progress storage. Confirm that you use this plugin rather than another project named Quests. Current maintainer documentation targets version 5 and newer; use the legacy reference when your installed release needs it.
Work through the change
- Record the reward item types, quantities and command-based grants. Save the reward definition and check the installed rewards reference for the supported delivery settings.
- Prepare a disposable staging account with a nearly full inventory and a completed recovery copy of its test state. Leave room for only part of the intended reward.
- Complete the quest normally and inspect the inventory, nearby ground and relevant messages. Compare the same completion with an empty inventory using a separate eligible test state.
- Test any reward integration that uses a command separately, since its delivery behaviour belongs to that plugin. Decide how the quest description should tell players to prepare inventory space.
Verify the result
The delivery outcome should be understood for both inventory states, with no assumed guarantee that every external reward command handles overflow the same way. Quantities should match the configured reward exactly.
If the result differs
If a reward appears missing, inspect drops and the command-provider logs before granting it again. If the quest completed but an integration failed, record that stage rather than repeatedly replaying completion.
Keep a recovery path
Restore the reward definition and disposable inventory checkpoint if needed. Keep a record of actual issued items so retries or compensation cannot duplicate a reward that was delivered somewhere unexpected.
References and related help
Check the maintainer reference: PikaMug Quests documentation.
Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.