No Interaction Prompt Appears#
If an air hockey table does not display an interaction prompt, verify that the table has been registered correctly.
Tables can be registered using /ahcreator, through the configuration, or by enabling automatic table detection. Also make sure you are within the configured interaction distance.
Air Hockey Table Creator Does Not Open#
If /ahcreator reports a permission error, verify that your administrator account has the required ACE permission configured in server.cfg.
Remember that permissions are validated server-side, so reconnecting your client alone will not resolve the issue.
Tables Disappear After Restart#
Only tables created with /ahcreator are saved to the database.
If your tables disappear after restarting the server, verify that the SQL file has been imported correctly and that oxmysql is connected successfully.
Puck Is Invisible#
If the puck cannot be seen during a match, verify that your server is streaming a valid puck model.
If no compatible model is available, review your configuration and ensure the required assets are loaded correctly.
Puck Physics Feel Incorrect#
If the puck bounces unexpectedly, leaves the table, or goals are not detected correctly, use the available debug calibration commands to adjust the table dimensions, goal areas, and playing surface.
These tools allow custom table models to be calibrated without modifying the gameplay code.
Players Cannot Challenge Each Other#
Only nearby players can receive challenges.
Verify that both players are close enough to the table and that neither player is already participating in another air hockey match.
No Prize Is Awarded#
Quasar Air Hockey only charges the configured table entry fee.
The resource does not include prize payouts or betting rewards by default. If desired, custom reward systems can be implemented through your server's framework integration.
Notifications Do Not Appear#
Quasar Air Hockey automatically integrates with qs-interface and qs-textui when they are available. Otherwise, the resource falls back to its default notification and interaction system.
If you use a custom notification framework, you can integrate it through the editable framework files.