Another question, if you please

[Diana]

I want to code in a transition inthe dialogue file for Wallace the gnome in Trademeet.  Since I'm new at this I've essentially been trying to use Append statements with the triggers.

I wondering if some of the Weidu commands I haven't tried yet would accomplish what I want more efficiently.  What I want to do is transition to a new state in his dialogue file (Wall1) state 7 to give my npc's choices.  This parses perfectly in Weidu but I want it to happen sooner than by chance.

// Wallace in TradeMeet
APPEND WALL1
IF WEIGHT #-10 ~InParty("MyNPC")
See("MyNPC") !Dead("MyNPC")
!StateCheck("MyNPC"",STATE_SLEEPING)
Global("geniesgone","GLOBAL",1)
Global("Wallace","GLOBAL",1)~ THEN GetPoison
SAY @520 = @521
IF ~~ DO ~SetGlobal("Wallace","GLOBAL",2)~ EXTERN MyNPC GetPoison2
END
END

CHAIN MyNPC GetPoison2
@522
== Wall1 @523 = @524 DO ~GiveItemCreate("MISCA2","D#Silver",0,0,0)~
== MyNPC @525
== Wall1 @526
EXIT

I know I've seen in action.ids for such an occasion but I don't understand them.

Thanks.

[jcompton]

You're using the word "transition", which means going somewhere from an existing line of dialogue. If that's the case, where (what state in WALL1) are you transitioning FROM?

In that case, you would use an INTERJECT command.

However, if you want this to be a stand-alone dialogue for WALL1--that is, a dialogue that would OPEN with line @520 when you click-talked WALL1 with your conditions in place, then this is basically correct. The one extra note is that you can do the entire thing in a CHAIN:

CHAIN IF WEIGHT #-1
~InParty("MyNPC")
See("MyNPC") !Dead("MyNPC")
!StateCheck("MyNPC",STATE_SLEEPING)
Global("geniesgone","GLOBAL",1)
Global("Wallace","GLOBAL",1)~ THEN WALL1 GetPoison
@520 = @521 DO ~SetGlobal("Wallace","GLOBAL",2)~
== MYNPC @522
== Wall1 @523 = @524 DO ~GiveItemCreate("MISCA2","D#Silver",0,0,0)~
== MyNPC @525
== Wall1 @526
EXIT

[Diana]

However, if you want this to be a stand-alone dialogue for WALL1--that is, a dialogue that would OPEN with line @520 when you click-talked WALL1 with your conditions in place, then this is basically correct. The one extra note is that you can do the entire thing in a CHAIN:

Thank you, this is much more elegant coding and I did want it to work as a click-talk.  I'm assuming that this still will have to be part of an APPEND block as Wallace starts the dialogue. Will try it out with your suggestions when I get home.
 

[jcompton]

Thank you, this is much more elegant coding and I did want it to work as a click-talk.  I'm assuming that this still will have to be part of an APPEND block as Wallace starts the dialogue. Will try it out with your suggestions when I get home.

No, the use of CHAIN eliminates the need for an APPEND statement. What I've shown you is all you need.

[Diana]

I'll take your word for it as you're a master at this stuff but I'm surprised it will work with Wallace initiating the dialogue in the chain as this code sequence is called from MyNPCJ.D file and not the Wall1.d.  I always thought the first dialogue line in a Chain had to belong to the creature in whose file the commands are being run.

[jcompton]

I'll take your word for it as you're a master at this stuff but I'm surprised it will work with Wallace initiating the dialogue in the chain as this code sequence is called from MyNPCJ.D file and not the Wall1.d.  I always thought the first dialogue line in a Chain had to belong to the creature in whose file the commands are being run.

Nope.

CHAIN is sort of its own little entity. Since you define who the first speaker is (CHAIN DLGNAME statelabel), it doesn't matter where it appears. So you can put it anywhere, as long as all of the DLGs you reference already exist (that is, either exist in-game, or have previously been created by BEGIN DLGNAME statements.)

Also, a CHAIN implicitly ends a BEGIN DLGNAME.

[Diana]

CHAIN is sort of its own little entity. Since you define who the first speaker is (CHAIN DLGNAME statelabel)

Thanks again - you've made things much easier.

[jcompton]

No problem.

This is a good case, though, where you should let existing work be your guide. Banter Packs (one big CHAINfest) consist of just two .d files, one for SOA and one for TOB, despite the fact that various people start the conversations.

[Diana]

I'll take another look at them.  Like most people, I was using Blue's "Road to Banter" tutorial as my guide.

[Diana]

*Doing happy dance*
Thank you**2!
That advice has helped me think outside the "box" with other things.  It's given me more ideas how to link my banters to current ingame Bioware events with the EXTEND_BOTTOM command and, wonder of wonders, it worked!

 

[jcompton]

Modding does, on rare occasions, actually work.