I've been reading the tutorials on how to do dialog. Look at this:
IF ~NumTimesTalkedTo(0)~ THEN BEGIN 0 // from:
SAY #28655 /* ~Who is it? Might I ask why you have disturbed my
meditations? My creative muse must be gently awakened, and your
stomping about is simply not conducive to this.~ [SARLES02] */
IF ~~ THEN REPLY #28656 /* ~My apologies. I will leave you to your
thinking.~ */ GOTO 1
IF ~~ THEN REPLY #28657 /* ~I apologize, but I have come to request your
talent on a commissioned artwork.~ */
DO ~SetGlobal("TalkedToSarles","GLOBAL",1)~ GOTO 2
END
and
SAY ~One~ = ~Two~ = ~Three~
In the first piece of code there is /* */ at the beginning of the text to be displayed, but this is not the case with the second piece of code. I also read that these marks can be used to comment, but that shouldn't be the case here; in this case weidu is meant to recognize the text. So is it necessary or not? If no, then why use it?
-Jepsolon

TEXT confusion
Started by Jepsolon, Feb 14 2004 05:26 PM
3 replies to this topic
#1
Posted 14 February 2004 - 05:26 PM
#2
Posted 14 February 2004 - 05:39 PM
In decompiled dialogs what you get is actually the pointer to the string, so SAY #28655 points to "Who is it? Might I ask why you have disturbed my meditations? My creative muse must be gently awakened, and your stomping about is simply not conducive to this." The stuff in comments is just for reference purposes.
In writing your own code it is not necessary. You would just use SAY ~One~ = ~Two~ = ~Three~
In writing your own code it is not necessary. You would just use SAY ~One~ = ~Two~ = ~Three~
#3
Posted 14 February 2004 - 06:09 PM
Great. Thanks. Suddenly it all makes sense.
-Jepsolon
-Jepsolon
#4
Posted 14 February 2004 - 06:23 PM
If you pass WeiDU the --text argument when you are decompiling a DLG file it will put the spoken text in the primary position and the strref number in the comment. You can also pass the --nocom argument if you don't want the comments.