{"version":"2.1.246","anchor":"built-in-plugins-that-require-trust-are-no-longer-enabled-on","canonical_anchor":"built-in-plugins-that-require-trust-are-no-longer-enabled-on","heading":"Built-in plugins that require trust are no longer enabled on someone else's behalf","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/built-in-plugins-that-require-trust-are-no-longer-enabled-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Built-in plugins that require trust are no longer enabled on someone else's behalf\n\nBuilt-in plugins that require trust no longer load when something other than you enabled them.\n\n**What**\n\nA built-in plugin marked as trusted-only is now skipped when it was turned on by a tier other than your own choice, rather than loading.\n\n**Details**\n\n- Skips are counted alongside the existing reasons `over_cap` and `untrusted_for_folder`, and reported the same way.\n\n**Evidence**\n\n`guard_builtin_not_own_choice`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}