{"version":"2.1.280","anchor":"debug-log-hint-message-reworded","canonical_anchor":"debug-log-hint-message-reworded","heading":"Debug-log hint message reworded","tier":"notice","area":"Debugging","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/debug-log-hint-message-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Debug-log hint message reworded\n\nThe dim hint pointing to debug logging now spells out what the debug file explains\n\n**Unclear.** It's not fully clear which specific warning or error message the new fixed suffix string is appended to.\n\n**What**\n\nA dim hint shown alongside some failure and log messages was reworded. It used to give a terse instruction; it now reads more explicitly, telling you to restart with `--debug-file <path>` to write a debug log explaining why something happened. A related fixed suffix string was also added, appearing to point users toward the debug log for more detail when a warning or error message is shown.\n\n**Why**\n\nThe clearer wording makes it more obvious that restarting with `--debug-file` produces a log explaining the cause of a problem, rather than just a generic debug dump, which should make it easier to know when and why to reach for it.\n\n- Area: Debugging\n- Names: `--debug-file`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}