{"version":"2.1.242","anchor":"skills-report-unsaved-and-read-only-problems-as-a-heads-up-b","canonical_anchor":"skills-report-unsaved-and-read-only-problems-as-a-heads-up-b","heading":"Skills report unsaved and read-only problems as a heads-up block","tier":"notice","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/skills-report-unsaved-and-read-only-problems-as-a-heads-up-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Skills report unsaved and read-only problems as a heads-up block\n\nSkill problems like unsaved or read-only locations now print as a visible heads-up block.\n\n**What**\n\nLoading or refreshing skills can now queue warnings, such as a skill being unsaved or its location being read-only, and print them as a bulleted block under a \"\u26a0 Heads-up:\" heading instead of failing quietly.\n\n**Details**\n\n- The queueing call is made from three points in the skill load and refresh paths.\n- Each note is truncated to 1000 characters when serialised.\n- A second printer emits one indented pointer-prefixed line per note for a compact form.\n\n**Evidence**\n\n`\\u26A0 Heads-up:`\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}