4 replies to this topic

[temnix]

A decompiled dlg shows that the engine writes to the journal in the manner of

 

JOURNAL #12345

UNSOLVED_JOURNAL #12345

 

I've been happily using AddJournalEntry(@X,INFO) since someone - I think it was Roxanne - told me about using the TRA file for these purposes on the G3 board. And it serves everywhere, though I don't know if Weidu has been updated to put quests in their proper compartments already or they are still in the same list. In any event, I can do most of the things I need from the journal with INFO-level entries. The method shouldn't make a difference.

 

But for drinks and rumors it seems to matter. The rumor dlg files of the game use straight string numbers, not a luxury I can afford with Weidu. That syntax won't accept @X from the TRA and attempts to write things with AddJournalEntry() at taverns fail. Actually, all dialogues with AddJournalEntry(), taverns or not, don't show as making journal entries in Near Infinity. See the picture:

 

 

They still update the journal in talks, so I wouldn't care, but when it comes to taverns, nothing happens. How can I go around or through it?

 

Also the "Action," in this case only setting a Global, doesn't work either from within a tavern. I wonder how those who've made custom drinks reveal areas and so forth have gone about setting Globals?

[Creepin]

Have you checked Gavin mod as you were advised earlier? Especially b!rumor.d looks like it is doing something you want to, all the while successfully linking @X from b!rumor.tra.

[Almateria]

You can force a .tra file for that dialog specifically by using COMPILE ~yourdialoguefile.d~ USING ~whateveryourmod/iscalled.tra~.

 

If you're modding EE, be sure to have an ADD_JOURNAL somewhere before compiling the dialog. Also compatible with USING a tra.

[temnix]

Creepin: not yet. I'll spend a little more time here first.

 

Almateria: you mean a different TRA than the main one? Like this:

 

COMPILE ~Mod/rumors.d~ USING ~Mod/TRA/OtherTRA.tra~ ?

 

How would that help, though? The problem isn't that I can't use the main TRA for AddJournalEntry() generally or for rumors; it's that no application of this action anywhere is recognized by the engine as flagging "Journal entry." The action works despite this, but the flag, apparently, matters for rumors. If I substitute another TRA, how will that make a difference? The only other way I know to write in the journal is that JOURNAL etc. style, which is no good without a definite string number.

[Almateria]

Have you checked the second solution, though? Enhanced Edition changed journal string handling, so you have to, uh, bake them into the game to have them appear in journal actions.

 

And JOURNAL TransAction totally accepts @ .tra references!