Running the Worker
Spigot Sales Webhook can run continuously as a background worker or execute a single scan and exit.
gradlew.bat clean jar./gradlew clean jarThe jar includes runtime dependencies and is written to build/libs/spigot-sales-webhook-1.0.0.jar.
Continuous Mode
Section titled “Continuous Mode”Run without arguments:
java -jar build/libs/spigot-sales-webhook-1.0.0.jarThe worker:
- Loads
config.yml. - Runs a scan immediately.
- Waits
scan.interval-minutes. - Repeats until the process is stopped.
Use this mode for a VPS, home server, Docker container, or systemd service.
One-Off Mode
Section titled “One-Off Mode”Run one scan and exit:
java -jar build/libs/spigot-sales-webhook-1.0.0.jar --onceThis is useful for:
- testing a new config
- checking whether the cookie can access buyer pages
- manually triggering a scan from a scheduled task
- verifying Discord delivery
Notify Existing Buyers
Section titled “Notify Existing Buyers”The first scan normally creates a baseline without sending messages. To notify existing buyers too, enable it in config.yml:
scan: notify-existing-on-first-run: trueThen run a one-off scan:
java -jar build/libs/spigot-sales-webhook-1.0.0.jar --onceThis is most useful when you are intentionally backfilling Discord with current buyer history.
Retry Behavior
Section titled “Retry Behavior”State is saved after successful processing.
If Discord delivery fails while new sales are being sent, the worker logs the error and does not save those new sales as seen. They will be retried on the next scan.
If one plugin target fails to fetch, the worker logs that failure and continues scanning the remaining configured targets.
Working Directory
Section titled “Working Directory”Relative paths are resolved from the process working directory.
This affects:
config.ymllookupscan.state-file
For direct jar runs, either run the command from the project/root folder that contains config.yml, or bundle src/main/resources/config.yml before building.