Lumberjack Job v2.8.1

Full Resource Replacement: Replace the updated files to apply these changes.
Webhooks: Add your URL to server.cfg with set qs_lumberjack_webhook "https://discord.com/api/webhooks/...". To send one event to its own channel, use the event name in lower case, for example set qs_lumberjack_webhook_moneypaid "...". Use set, never setr.
If your webhook URL was in config/config.lua, delete that webhook in Discord and create a new one, because every player could see it. Your old config keeps working, with a warning in the console.
Tournament fold key: Config.TournamentFoldKey is empty by default, so the key stays unbound until you set one (e.g. 'F7') or players bind it in Settings > Key Bindings > FiveM.
From now on, we will also publish updates through our official updates page: https://www.quasar-store.com/updates. Please start getting familiar with this platform, as it will become another place to follow our latest releases and changes.
If you encounter any errors, replace the entire script and run the SQL again.

Full Resource Replacement: Replace the updated files to apply these changes.
Webhooks: Add your URL to server.cfg with set qs_lumberjack_webhook "https://discord.com/api/webhooks/...". To send one event to its own channel, use the event name in lower case, for example set qs_lumberjack_webhook_moneypaid "...". Use set, never setr.
If your webhook URL was in config/config.lua, delete that webhook in Discord and create a new one, because every player could see it. Your old config keeps working, with a warning in the console.
Tournament fold key: Config.TournamentFoldKey is empty by default, so the key stays unbound until you set one (e.g. 'F7') or players bind it in Settings > Key Bindings > FiveM.
From now on, we will also publish updates through our official updates page: https://www.quasar-store.com/updates. Please start getting familiar with this platform, as it will become another place to follow our latest releases and changes.
If you encounter any errors, replace the entire script and run the SQL again.

v2.8.1 patch