With backwards comp I meant that currently, BG:EE content in SoD is detected by ~bgee~, which will change after the WeiDU update. I do understand that it is not feasible nor possible to code things before knowing them. My apologies if my post annoyed. But I fear the players' frustration once the changes apply and all BG:EE mods fail to install on SoD. I also fear for the mods that were updated in community effort because I know I won't do it again.
The above post was more of a sign of my current state of mind than criticism. I am kind of overwhelmed by all the changes. Personally, I need to halt modding activity until things have stabilized or I'll lose motivation completely. it's my personal problem currently.
One question for discussion, though: For bg1 and totsc, it was a must that the two games were detected individually, because the engine was different. Thus, a mod with bg1 content had to be coded differently if it was to be installed on a BG:TotSC game.
For the EE games constantly developped, though, do I see it correctly that the engines of BG:EE and SoD are updated at the same time with the same changes? Meaning, do we need a possibility to detect the different games or do we only need a way to detect whether the extended content is present. With the assumtpion of the engines being similar, I'd be happy with ~bgee~ detecting sod, too, and ~sod~ excluding a BG:EE game. It would be a content-detection for additional mod content, only. But inconsistent with the current definition of ~tutu~ ~tutu_totsc~, and probably also the definition of GAME_IS, I guess.
Can I achieve this with GAME_INCLUDES? If I change my current use of GAME_IS ~bgee~ to GAME_INCLUDES ~bgee~, will the mods install on SoD? Or is there an even better way?