Cryptic Callouts
In this section
Installation Requirements Configuration Available Callouts Updating Cryptic Callouts Troubleshooting Frequently Asked Questions
Documentation / Cryptic Callouts / Troubleshooting

Troubleshooting

🚨 This article is for Cryptic Callouts
4 min read
Updated Sep 29, 2026
41 views

This guide covers common installation, loading and gameplay problems with Cryptic Callouts.

Start with the checks that match your issue. Make one change at a time and test the result before changing anything else.

Cryptic Callouts Does Not Load

Check that:

  • You are using Grand Theft Auto V Legacy.
  • The plugin is installed in Grand Theft Auto V Legacy\plugins\LSPDFR\.
  • All accompanying files follow the folder structure supplied with the download.
  • The dependencies listed for your release are installed.
  • RagePluginHook launches the game successfully.
  • LSPDFR loads and allows you to go on duty.
  • Your installed versions meet the release requirements.
Installing only the plugin file may leave required accompanying files missing. Check the complete download and its installation instructions.

Callouts Are Not Appearing

If the plugin loads but you are not receiving its callouts:

  1. Confirm that you are on duty in LSPDFR.
  2. Check that the callouts you want are enabled in the configuration.
  3. Check the RagePluginHook log for registration or loading errors.
  4. Continue your patrol and allow further callout offers.
Callouts are not offered in a fixed order. Not receiving a particular scenario during one patrol does not establish that it is broken.

Check Your Logs

Review your RagePluginHook log and any relevant LSPDFR logs.

Look for entries mentioning:

  • Cryptic Callouts
  • Missing files or dependencies
  • Plugin loading failures
  • Callout registration failures
  • Exceptions during a callout

Check entries around the time the problem occurred, including those before the final error or crash message.

Keep a copy of the log from the affected session before launching the game again. Share the complete log when requesting support so the surrounding entries can be reviewed.

Problems After Installing or Updating

If the issue began after an installation or update:

  1. Confirm that all supplied files were copied to their intended locations.
  2. Review the release notes for additional installation steps.
  3. Check for new or changed dependencies.
  4. Confirm that your configuration matches the installed release.
  5. Review the log for errors from the affected session.

If you transferred settings from an older configuration, test with an unedited copy supplied with your current version.

Back up your customised configuration before replacing it. Restoring the supplied file resets the values stored in that file.
Avoid reinstalling several plugins or changing multiple settings at once. This makes it harder to identify which change affects the problem.

A Callout Stops Progressing

If a callout loads but an objective does not progress:

  1. Check the latest on-screen instructions.
  2. Note the callout name and the objective you were completing.
  3. Record what happened immediately before progress stopped.
  4. Check the log for an exception at that time.
  5. Note whether another plugin changed, arrested, removed or took control of an involved pedestrian or vehicle.

Useful details include whether a suspect fled, an involved character disappeared, an interaction prompt failed or the issue followed a particular action.

Report the exact stage where the callout stopped. “The callout broke” provides less useful information than a description of the last completed objective and what happened next.

Checking for Plugin Conflicts

Other modifications may affect pedestrian tasks, vehicle behaviour, spawning or callout handling.

To investigate a possible conflict:

  1. Back up your current setup.
  2. Temporarily disable optional plugins that may affect the same behaviour.
  3. Keep LSPDFR, Cryptic Callouts and their required dependencies enabled.
  4. Test the affected scenario again.
  5. Re-enable optional plugins in small groups and compare the results.
A problem disappearing during one test is a useful clue, but intermittent issues may require further attempts to establish a pattern.
Keep required dependencies installed during testing. Removing them can introduce separate loading problems.

Reporting a Problem

Include:

  • Your Cryptic Callouts version.
  • Your GTA V Legacy version.
  • Your LSPDFR version.
  • Your RagePluginHook version.
  • The affected callout name, if applicable.
  • What you expected to happen.
  • What actually happened.
  • The actions that led to the issue.
  • Whether the problem happens consistently or occasionally.
  • Your RagePluginHook log from the affected session.
  • Any troubleshooting steps you have already tried.

Screenshots or a short video can also help explain problems with prompts, positioning or scene behaviour.

If the game crashes, include what was happening immediately before the crash. If the callout continues running but behaves incorrectly, describe the behaviour and the stage at which it begins.
Was this helpful?
On this page
Cryptic Callouts Does Not Load Callouts Are Not Appearing Check Your Logs Problems After Installing or Updating A Callout Stops Progressing Checking for Plugin Conflicts Reporting a Problem