Posted by: plainab
« on: August 09, 2009, 06:24:07 PM »I had something similar with an inlined script that was being extended to the bottom of a pre-existing script.
I solved it by using OUTER_SPRINT to define a variable and then putting that variable inside %'s inside ~'s and a EVALUATE_BUFFER after the EXTEND_BOTTOM line. It worked like a charm.
In your case, if you didn't want to mess with a tra file, you could try the following...
Then again, .baf and .d can be handled differently by weidu so who knows for sure....
But it doesn't matter how you get it to work, so long as you get it to work. Of which it sounds like you already got something to work...
I solved it by using OUTER_SPRINT to define a variable and then putting that variable inside %'s inside ~'s and a EVALUATE_BUFFER after the EXTEND_BOTTOM line. It worked like a charm.
In your case, if you didn't want to mess with a tra file, you could try the following...
Code: [Select]
OUTER_SPRINT cut_text ~StartCutSceneMode being called~
COMPILE ~some.d~ //where your dialog file has ~%cut_text%~ instead of ~StartCutSceneMode being called~
EVALUATE_BUFFER
Then again, .baf and .d can be handled differently by weidu so who knows for sure....
But it doesn't matter how you get it to work, so long as you get it to work. Of which it sounds like you already got something to work...