There has to be a solution to the problem of "traifying a mod that is coded using the "Crossing the great Divide" approach aka OUTER_SPRINT variables". Please! PLEEEASE!
If I try to traify something like
EXTEND_BOTTOM %tutu_var%SCAR 14
+ ~!Alignment(Player1,19)
!Alignment(Player1,35)
!Alignment(Player1,51)
ReputationGT(Player1,11)~ + ~First, I would like to talk to you some more, Scar.~ + talking_battle
END
weidu chokes at the OUTER_SPRINT variable if I try to traify it. OK, it looks like syntax error, I can understand, so I replaced all "%" with "_PERCENTAGESIGN_". Leading to weidu still choking, at the use of "CD_STATE_NOTVALID" (not in the example) - why? This is not a syntax error, so weidu shouldn't care for traifying purpose. And next it complains that there exists no "_PERCENTAGESIGN_tutu_var_PERCENTAGESIGN_SCAR" dlg in the game. Why? It shouldn't care!
State is, it is impossible to traify a mod that uses OUTER_SPRINT variables, currently.
Would it be possible to let the traify process either use the libs of the mod I want to traify, or let it ignore dlg names and things the mod introduces if they are not (yet) installed?
I do not know how to solve this, without a lot of handwork. (I am talking about a mod with 35 components, btw.)
jastey - sad.