DocsNotify

Troubleshooting

Causes the script reports or can have.

Not released yet. These pages are written from the code of manniche_notify and can change before the release.

ESX messages still go to esx_notify

The client console prints: [manniche_notify] esx_notify is running, so ESX messages still go there. Stop it in server.cfg to show them here.

Cause: esx_notify was started when manniche_notify loaded. Add stop esx_notify before ensure manniche_notify and keep the resource installed.

ESX messages are not taken over

Check that Config.replaceEsx is true. When it is false, the ESX hooks are not registered.

A message does not show

  • A message with an empty title and description is ignored.
  • Messages sent before the interface has loaded are queued, up to 20. More are dropped.
  • The resource must be started with ensure manniche_notify.