Skip to main content

Separate an accepted vote from a failed reward listener

Applies to: NuVotifier; match the linked maintainer documentation to your installed platform and release.
Documentation checked .

NuVotifier receives vote records; it does not include a reward listener by default. A website’s successful test can therefore stop at the receiver while the player sees no coins, items or message. Establish which stage actually completed.

Before you change settings

Write down the receiver process, reward plugin and backend where delivery is expected. Save the test player’s starting balance and inventory if rewards modify them. Use a genuine account identity and one configured listing to avoid confusing an invented username with a delivery failure.

Follow the request through the plugin

  1. Send one external test and capture the receiver’s timestamp and accepted vote details. If no receiver event exists, stop here and check the listener endpoint, allocation and listing credentials.
  2. Confirm a compatible reward listener is loaded on the process that receives or legitimately forwards the event. Read startup errors rather than assuming the presence of its JAR means it is active.
  3. Look for the reward plugin’s receipt of the same player and service identifier. On a network, follow the forwarding stage between the proxy and backend before editing reward amounts.
  4. If receipt is confirmed, inspect site matching, eligibility, offline queues and the particular reward action. Run a bounded local processing test only to isolate that downstream stage.

Confirm the intended result

A complete test should show receipt, processing and the intended player-visible result. Record each stage separately so a future support report identifies the missing link. Verify the player reconnects normally if the reward requires online delivery.

If the test fails

An administrative local vote can pass while the public listener is unreachable. Conversely, an accepted listener event can fail to match a configured service name. Do not treat either test as proof of the whole chain or repeatedly send rewards while diagnosis is incomplete.

Revert the single listener or reward setting you changed if another working site stops processing. Preserve event logs and queued records. Do not reinstall the server or erase vote data to resolve a missing listener hook.

Sources and related help

No comments to display