JJM Modifications

Troubleshooting

Common issues and how to resolve them.

Admin Menu Won't Open#

  • Confirm jm-adminmenu is listed in server.cfg with ensure jm-adminmenu.
  • Make sure your player's license identifier is assigned to a group that has admin.menu allowed.
  • Check the server console — permission check results are logged with a [DEBUG] prefix to help identify mismatches.
  • Try running /adminmenu instead of pressing F5 to isolate key binding issues.

Permission Denied Errors#

  • Double-check that the add_principal line in server.cfg uses the exact license format: identifier.license:xxxxxxxx.
  • Confirm the ACE entries for the relevant group are present and spelled correctly.
  • Membership in group.admin or group.superadmin acts as a fallback for all permission checks, so adding the player to either group will grant full access.

Weather or Time Controls Not Working#

Warning

If you run an external weather or time script such as qb-weathersync, cd_easytime, vSync, or BigDaddy-Weather at the same time, those scripts will conflict with the weather and time controls in this menu. Either disable the external script or simply avoid using those controls in the admin menu. All other features (troll, player management, etc.) work normally regardless.

If you removed your weather script and now the advanced weather controls are not visible, reinstall the weather script or choose one of the compatible options listed above.

Bans Not Blocking Players#

  • Verify oxmysql starts before jm-adminmenu in server.cfg.
  • Confirm the jm_bans table was created by checking with SHOW TABLES LIKE 'jm_%';.
  • Look for SQL errors in the server console related to the ban query.
  • Ensure the MySQL event scheduler is enabled if you rely on automatic temporary ban expiration.

Database Errors — Table Doesn't Exist#

  • Re-import database.sql and verify the import completed without errors.
  • Check that the mysql_connection_string points to the correct database.
  • Confirm the MySQL user has full privileges on the target database:
GRANT ALL PRIVILEGES ON database_name.* TO 'username'@'localhost';FLUSH PRIVILEGES;

oxmysql Not Found#

Inventory Give Not Working#

  • Make sure at least one of ox_inventory, qbx_inventory, or qb-inventory is installed and started.
  • Set Config.InventoryIntegration.PreferredSystem to match your inventory resource ("ox", "qbox", or "qb") rather than leaving it on "auto" if auto-detection fails.
  • Confirm the executor has the admin.developer permission.

Version Check Fails at Startup#

  • This is a non-critical warning. It means the resource could not reach the remote version endpoint — likely a firewall or connectivity issue on the server machine.
  • All functionality works normally regardless of whether the version check succeeds.