5 replies to this topic

[Jepsolon]

Here is a bit of code I made: (# in parenthesis is the line number)

(253)
IF ~~ THEN BEGIN 30 // from: 4.7 10.7 25.8 26.8 27.8 28.8 29.8
SAY ~Very well. I shall wait here for you a while.~
IF ~~ THEN UNSOLVED_JOURNAL ~The fighter awaits my answer. He has asked me to make up my mind as soon as possible.~ EXIT
END

(258)
IF ~~ THEN BEGIN 31 // from: 14.2
SAY ~I am in need of able men, but I am not desperate for them.~
IF ~~ THEN REPLY ~Yeah, yeah, yeah, let's just get to it.~ DO ~SetGlobal("fighterJoined","LOCALS",1) JoinParty~
IF ~~ THEN UNRESOLVED_JOURNAL ~Looks like I'm stuck with the fighter.~ EXIT
IF ~~ THEN REPLY ~Bah! I have no for you.~
IF ~~ THEN JOURNAL ~I told the fighter go sod off. Bah!~ EXIT
END

And this is the reply WeiDU gave me:

D:\Games\Baldurs Gate II - Throne of Bhaal>weidu --tlkout dialog.tlk valren01.d
[weidu] WeiDU version 148
[./CHITIN.KEY] 182 BIFFs, 41793 resources
[./dialog.tlk.old] 74157 string entries
[TRIGGER.IDS] parsed
[ACTION.IDS] parsed

[action list near line 134, column 147 of valren01.d] PARSE WARNING at line 134
column 135-143
Near Text:
syntax error

[action list near line 144, column 65 of valren01.d] PARSE WARNING at line 144 c
olumn 53-61
Near Text:
syntax error

[action list near line 260, column 113 of valren01.d] PARSE WARNING at line 260
column 101-109
Near Text:
syntax error

[valren01.d] PARSE ERROR at line 261 column 3-4
Near Text: IF
syntax error

[valren01.d] ERROR at line 261 column 3-4
Near Text: IF
Parsing.Parse_error
ERROR: parsing [valren01.d]: Parsing.Parse_error

ERROR: Parsing.Parse_error


Please help.

-Jepsolon

[Andyr]

258)
IF ~~ THEN BEGIN 31 // from: 14.2
SAY ~I am in need of able men, but I am not desperate for them.~
IF ~~ THEN REPLY ~Yeah, yeah, yeah, let's just get to it.~ DO ~SetGlobal("fighterJoined","LOCALS",1) JoinParty~
IF ~~ THEN UNRESOLVED_JOURNAL ~Looks like I'm stuck with the fighter.~ EXIT
IF ~~ THEN REPLY ~Bah! I have no for you.~
IF ~~ THEN JOURNAL ~I told the fighter go sod off. Bah!~ EXIT
END

I don't know which line this is, but try replacing UNRESOLVED_JOURNAL with UNSOLVED_JOURNAL.

[Kismet]

A couple of comments. Using numbers for state lables can lead to confustion. It's better to use some sort of text and just let WeiDU convert it to numbers. The JOURNAL and UNSOLVED_JOURNAL should go on the same lines as the REPLYs. I think with adding journal entries in .d files you have to use a .tra file.

So your .d file would look like:

IF ~~ THEN BEGIN NPCWantsToJoin
SAY ~I am in need of able men, but I am not desperate for them.~
IF ~~ THEN REPLY ~Yeah, yeah, yeah, let's just get to it.~ DO ~SetGlobal("fighterJoined","LOCALS",1) JoinParty~ UNSOLVED_JOURNAL @0 EXIT
IF ~~ THEN REPLY ~Bah! I have no for you.~ JOURNAL @1 EXIT
END

And your .tra file would look like:

@0 = ~Looks like I'm stuck with the fighter.~
@1 = ~I told the fighter go sod off. Bah!~

And your .tp2 file would use:

COMPILE ~mymod\npcdialog.d~
USING ~mymod\npcdialog.tra~

[Jepsolon]

First of all thanks for the replys. They helped.

But could someone please tell me how to properly use @ commands for my journal entries, and how to make a .tra file, etc. I simply can't understand the tutorial that comes with weidu on this point:

First, let's create a TRA file:

C:\Program Files\Black Isle\BGII - SoA\> weidu --traify-tlk --min 2000 --max 2002
...
@2000 = ~Indeed! It's been quite tasty so far. Listen, we're not here to
devour everything. In fact, we'd like to help a little girl named
Jaella.~
@2001 = ~No, we haven't. We will devour you if you don't tell us what we
need to know.~
@2002 = ~Let us stop this charade. I'm only here to ask you a few
questions.~
...
You may also extract only those strings matching a regexp:

C:\Program Files\Black Isle\BGII - SoA\> weidu --traify-tlk --strfind lawyer
...
@36568 = ~Honor-bound and honor-branded, then, is it? Very well, lawyer,
you have set me free and for that I thank you.~
...
Finally, you may redirect the output to a file using --textout and read from a different TLK file by adding it on the command line.

Once you have a TRA file with a few entries you can create a TLK file from it:

C:\Program Files\Black Isle\BGII - SoA\> weidu --make-tlk my.tra --tlkout new.tlk
[c:\src\weidu\weidu.exe] WeiDU version 109
[C:\Program Files\Black Isle\BGII - SoA/chitin.key] 182 BIFFs, 41793
resources
[C:\Program Files\Black Isle\BGII - SoA/dialog.tlk] 82405 string entries
[my.tra] parsed
[my.tra] has 100 translation strings
New TLK will have 200 entries
[new.tlk] created, 200 string entries
String @1 in your TRA file will become string reference #1 in the TLK file. If your TRA file has ``holes'' the new TLK file will have blank entries. You may specify --make-tlk multiple times: the last TRA file to define a translation string determine that string reference.

If you could please elaborate on different specific commands and how they work, that would help me a lot

-Jepsolon

[Kismet]

Unless you have a whole ton of journal entries already done, I'd just do it manually. By that I mean make a text file put your journal entries in it like I posted before and save it as mynpcdialog.tra and replace the journal entries with the appropriate @#.

If you wanted to --traify the file you would use: weidu --traify mymod\dialog.d --dout dialog-new.d.

That would put dialog-new.d and dialog-new.tra in your BG2 main directory.

This is the appropriate part of the readme for converting a hardcoded .d file. http://www.weidu.org...iDU.html#htoc15

[Jepsolon]

Whoot!

It all works now. Thanks a bunch.

-Jepsolon