{"version":"2.1.239","anchor":"plugin-names-checked-for-invisible-and-separator-characters","canonical_anchor":"plugin-names-checked-for-invisible-and-separator-characters","heading":"Plugin names checked for invisible and separator characters","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/plugin-names-checked-for-invisible-and-separator-characters","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Plugin names checked for invisible and separator characters\n\nPlugin names with @, colons, whitespace, path separators or invisible characters are now rejected.\n\n**What**\n\nA plugin manifest is now rejected with a validation error if its name is empty or contains `@`, `:`, whitespace, a path separator, or an invisible or control character. Naming a plugin after its own directory produces a specific hint.\n\n**Details**\n\n- A manifest version containing unprintable characters is treated as if absent, with a warning rather than a hard failure.\n\n**Evidence**\n\n`must be non-empty and must not contain \"@\", \":\", whitespace, path separators, or invisible\/control characters`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}