Musings about REPLACE_STATE_TRIGGER [solved]

[jastey]

Nearly all REPLACE_someplace_something commands work the way that you specify ~something to delete~ and ~something new to add~

Only REPLACE_STATE_TRIGGER replaces the whole trigger:

REPLACE_STATE_TRIGGER ~dlgname~ statnumber ~new trigger variables~

For compatibility reaons, I would like to have a non-destructive REPLACE_STATE_TRIGGER_IFONLY

-replace only, if ~something to delete~ is existent, other wise ignore

-in case of adding a trigger to a state: only, if UNLESS ~something else is not there~

Would this be possible?

If parts are already doable by other means, please enlighten me.

[jastey]

Well, duh, this was meant to be an edit of the above. 

Nearly all REPLACE_someplace_something commands work the way that you specify ~something to delete~ and ~something new to add~

Only REPLACE_STATE_TRIGGER replaces the whole trigger:

REPLACE_STATE_TRIGGER ~dlgname~ statnumber ~new trigger variables~

For compatibility reaons, I would like to have a non-destructive REPLACE_STATE_TRIGGER_IFONLY

-replace only, if ~something to delete~ is existent, other wise ignore

-in case of adding a trigger to a state: only, if UNLESS ~something else is not there~ [This would be needed if two mods add a new state trigger to a state that didn't have one before, so one doesn't destroy the trigger of the other]

Would this be possible?

If parts are already doable by other means, please enlighten me.

[Kulyok]

If it's not a first state in dialogue, wouldn't an ADD_TRANS_TRIGGER/ADD_STATE_TRIGGER with your own variable work better? You set your variable to 1 if you want it to go the mod way, and to 0 if you want it to go the vanilla game way.

[jastey]

ADD_STATE_TRIGGER can be useful, but in my case it is not. I need a state trigger to either be True() (my mod) or don't change it (in case the other mod is installed). Yes, I could track the other mod in other means, but what I posted above is an inconsistency in the REPLACE_bla_bla commands as I stated.

REPLACE_TRANS_ACTION e.g. gives the possibility to replace a single action, not destructively replaces all of them. Geat advantage: If the text to be replaced is not there it does nothing.

Wait - ADD_STATE_TRIGGER already exists? Why didn't I spot this when I was searching?

OK, it seems ADD_STATE_TRIGGER UNLESS is already implemented and what I need? Gha. Sorry for the bother.