{"version":"2.1.269","anchor":"skill-override-resolution-refactored-through-a-new-lpt-loo","canonical_anchor":"skill-override-resolution-refactored-through-a-new-lpt-loo","heading":"Skill-override resolution refactored through a new lPt() lookup","tier":"internal","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/skill-override-resolution-refactored-through-a-new-lpt-loo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Skill-override resolution refactored through a new lPt() lookup\n\nPer-skill override lookup refactored to use a single new resolution function\n\n**What**\n\nThe internal function that resolves whether a specific skill has been turned on or off by an override no longer makes two separate lookups (one for `policySettings`, one for `flagSettings`). Instead it makes a single call to a new lookup function, and reads that result's `source` field to decide whether the override came from policy or from a flag.\n\n**Why**\n\nThis is an internal simplification of how skill overrides are resolved; it doesn't appear to change what settings are available or how they behave.\n\n- Area: Skills\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}