{"version":"2.1.228","anchor":"lookalike-skill-names-can-no-longer-shadow-each-other","canonical_anchor":"lookalike-skill-names-can-no-longer-shadow-each-other","heading":"Lookalike skill names can no longer shadow each other","tier":"notice","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/lookalike-skill-names-can-no-longer-shadow-each-other","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Lookalike skill names can no longer shadow each other\n\nSkills with visually identical names can no longer sneak past collision checks.\n\n**What**\n\nSkill and command name collisions are compared after normalizing confusable characters, so a synced skill with a visually identical name can no longer slip past the check that drops it in favour of a local skill of the same name.\n\n**Details**\n\n- Names are put through NFKC, then separators, control characters, format characters, default-ignorable code points and the braille blank U+2800 are stripped.\n- All dash punctuation and the minus sign fold to `-`; five colon lookalikes (U+A789, U+2236, U+0589, U+05C3, U+02D0) fold to `:`.\n- Case folding is applied last.\n\n**Evidence**\n\n`\/[\\ua789\\u2236\\u0589\\u05c3\\u02d0]\/g`\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}