Jastey, I took a stab at "coding around this" here: https://forums.beamd...#Comment_666870
using one of your "engaged match blocks" from C#Ajantis ToB (edited) to demonstrate some difficulties coding around the problem in the first place.
I may play with it for fun, but I don't have romances screened by race - and it is installl order dependent - and - yuck. You can't have nested OR statements, so we can't just OUTER_SPRINT our way out of it. Anything in a .baf that says
has to be broken off into duplicat eblocks, because Race just became a multiple condition statement -
ACTION_IF MOD_IS_INSTALLED ~SUBRACE/SETUP-SUBRACE.TP2~ ~0~
OUTER_SPRINT player1human ~OR(8) Race(Player1,1) Race(Player1,50) Race(Player1,51) Race(Player1,52)Race(Player1,53) Race(Player1,54) Race(Player1,55) Race(Player1,56) ~
END ELSE BEGIN
OUTER_SPRINT player1human ~Race(Player1,1)~
I don't klnow if the engine will pick up the "readable" designations that mod uses or not - conventional format is either HALFORC or HALF_ELF, and these have spaces in between the words. So just the number seems safest.
sample of the APPEND to race.ids (humans) :
~50 Aasimar~ UNLESS ~^50~
~51 Deep Imaskari~ UNLESS ~^51~
~52 Firesoul Genasi~ UNLESS ~^52~
~53 Earthsoul Genasi~ UNLESS ~^53~
~54 Stormsoul Genasi~ UNLESS ~^54~
~55 Watersoul Genasi~ UNLESS ~^55~