{"version":"2.1.223","anchor":"command-aliases-now-count-when-detecting-name-collisions","canonical_anchor":"command-aliases-now-count-when-detecting-name-collisions","heading":"Command aliases now count when detecting name collisions","tier":"notice","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/command-aliases-now-count-when-detecting-name-collisions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Command aliases now count when detecting name collisions\n\nYour custom command is now flagged when its name clashes with a builtin command's alias.\n\n**What**\n\nA user or plugin command whose name matches a builtin command's alias is now detected as a collision instead of quietly shadowing it.\n\n**Details**\n\n- Building the set of taken command names adds each command's `aliases` entries as well as its name.\n- The same alias awareness feeds the new tip filtering check (`n.name === e || n.aliases?.includes(e)`).\n\n**Evidence**\n\n`for (let g of h.aliases ?? []) s.add(g);`\n\n- Area: Slash Commands\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}