However, since GROUP constraints act as REQUIRE_PREDICATE, it ends up working like REQUIRE_PREDICATE (GROUP_ENABLED ~BG2 NPCs~ OR GROUP_ENABLED ~BG1 NPCs~) AND GAME_IS ~bg2 tob~ AND GAME_IS ~tutu tutu_totsc bgt~.
Well that is fairly counterproductive, because the game will never be *both* BG2 and Tutu. Should be a disjunction of two conjunctions, not vice-versa:
(GROUP_ENABLED ~BG2 NPCs~ AND GAME_IS ~bg2 tob~) OR (GROUP_ENABLED ~BG1 NPCs~ AND GAME_IS ~tutu tutu_totsc bgt~)
Now, I could remove the constraints from this component, based on the assumption there will always be an Edwin present regardless of platform. But my request was to look for all constraints for the GROUP and treat them as a conjunction (primarily for mod-added NPCs). By that, I meant the selected group - the BG2 NPC group is autoskipped here, so it shouldn't be looking at the constraints for it. Doesn't make much sense to remove the constraints from all GROUPs either. Any chance of restoring the v221 beta behaviour, only with the "conjunctive constraints" added (sounds a bit like "conjugal visits" eh)?