Troubleshooting

If something is not working as expected, check the relevant section below before contacting support.

Blips not appearing#

• Confirm Config.EnableBlips = true in config.lua.
• Check that the individual blip has enabled = true.
• Verify the coordinates are valid for your server's map.
• Look for Lua syntax errors in the server console — a missing comma or quote in config.lua will prevent the resource from loading.

Duplicate blips#

Another resource on your server is creating the same blip. Set that blip to enabled = false (or the equivalent option) in the other resource's config. Do not disable it in both places or it will not appear at all.

Resource fails to start#

• Check that the folder is named exactly JM-Blips. Renaming the folder breaks verification.
• Confirm ensure JM-Blips is present in server.cfg.
• Review the server console for Lua parse errors pointing to config.lua.

Admin commands not working#

• You see "You do not have permission to use this command": verify your Steam64 ID and ACE permission setup in server.cfg. See the Permissions page for all supported patterns.
• Restart the server after editing server.cfg — ACE permission changes are not hot-reloaded.

Language file errors on startup#

If the console shows a message like Language file not found, check that Config.Language in config.lua matches an existing file in the lang/ folder (e.g. "en" → lang/en.lua). The resource will automatically fall back to English if the specified file is missing.

Notifications not showing#

• If Config.Notification.system is set to "auto", the resource tries JM-Notify, okokNotify, and mythic_notify in order. If none are installed it falls back to chat.
• If you have set a specific system (e.g. "jm") and notifications are absent, confirm that resource is installed and started.
• Set system = "chat" as a temporary measure to confirm blip events are firing correctly.

Version check warning#

If the console shows an update notice on startup, download the latest version from your CFX Portal granted assets. Running an outdated version may include known bugs that have already been fixed.