Find an offline vote waiting in NuVotifier forwarding cache
A received vote can wait for a suitable delivery route. With NuVotifier plugin-messaging forwarding, the configured fallback affects where an offline player’s vote eventually goes. A queued event is not proof that the listing failed to send it.
Before you change settings
Record whether the network uses NuVotifier plugin messaging or a different plugin’s proxy transport. This procedure concerns NuVotifier’s own cache. Save forwarding settings and note one test vote’s player, service identifier and timestamp before testing reconnect behaviour.
Follow the request through the plugin
- Verify the proxy received the vote, then inspect whether forwarding is limited to the joined server. Identify the configured
joinedServerFallbackand excluded destinations. - If a fallback is configured, check whether it is reachable. The maintainer guide explains that a cached vote awaiting that fallback is not automatically redirected to whichever server the player next joins.
- If your intended policy is delivery on the next join, compare the documented empty fallback arrangement with the current configuration. Change the policy only after understanding votes already queued under the old route.
- Check the configured cache retention and storage type. Reconnect the test player once, follow the receiver and backend logs, and wait for the recorded vote to be delivered before sending another.
Confirm the intended result
The event should arrive at the destination chosen by your forwarding policy, within the configured retention window. Record which backend applied the reward. Confirm normal online delivery still works after adjusting an offline route.
If the test fails
A listener accepting the event and a reward plugin queuing an offline reward are different stages. If the backend already processed the vote, troubleshoot that plugin’s reward queue instead. Do not assume every proxy or forwarding method has NuVotifier’s caching behaviour.
Restore the previous fallback setting if the new policy sends events to an unintended backend. Preserve cache files and vote logs. Do not delete the cache or manually replay all votes while previously accepted events may still be pending.