Dartboard Does Not Appear#
If the dartboard or interaction prompt is missing, verify that the resource started without errors and that the board has been created correctly.
Boards placed using the creator are loaded from the database when the resource starts. If you are using map-placed boards, make sure they are within the configured streaming distance.
Dartboard Creator Does Not Open#
If /dartscreator does not open, verify that your administrator account has the required ACE permission configured in server.cfg.
Also make sure Config.Debug is enabled if you are trying to use debug-only calibration commands.
Players Cannot Start a Match#
Make sure no player is already participating in another darts game and that both players are close enough to the dartboard.
If betting is enabled, verify that both players have enough money to pay the configured entry fee.
Score Is Not Updated Correctly#
The resource automatically applies official X01 scoring rules, including bust detection and turn validation.
If the score does not update correctly, ensure that both players remain connected throughout the match and that no server errors are reported.
Dartboards Disappear After Restart#
Custom dartboards are stored inside the qs_darts_boards database table.
If boards disappear after restarting the server, verify that the SQL file has been imported successfully and that oxmysql is connected to your database.
Money or Bets Are Not Working#
Player payments depend on the detected framework. On standalone servers no money is removed.
Verify that the selected payment method is configured correctly and that both players have sufficient funds before starting the match.
Debug Commands Do Nothing#
Calibration commands are only available when Config.Debug is enabled.
Enable debug mode, restart the resource, perform the required calibration, and disable it again before using the script on a production server.
Notifications Do Not Appear#
Quasar Darts automatically integrates with qs-interface and qs-textui when they are available. Otherwise, the resource falls back to its default notification and interaction system.