Ardanis

Unless we're talking about grindhouse level budgets, modern CGI is indistinguishable from actual footage. That's all there's to say imo.

RES actions accept any 8 characters. Nothing catches my eye, so I would suspect it may be a SPL itself - name, targeting, whatever. Does it work if you remove all other actions?

Minor nuances like this thread's subject aren't discussed by a council of game designers at round table. They're just put in by whoever is responsible for implementing the content on the "does it break something? If not, then let's roll with it" basis, before moving on to the next item from a very lengthy list.

Invision hitting new bottom with every new update. Why am I not surprised

It works if you put it the last in trigger block. gibberlings3.net/forums/topic/31466-looking-for-a-talked-to-such-and-such-condition/?tab=comments#comment-282595

There was some talk during SoD's development about using this trigger for AI, but it remained just a talk. I would assume it only, if ever, returns true when path is blocked by searchmap/doors.

Unless you know what you're doing, follow this template for launching cutscenes. Activation script: IF // triggers THEN RESPONSE #100 StartCutSceneMode() ClearAllActions() // optional StartCutSceneEx("#L_Cut07",TRUE) // if you need triggers within cutscene evaluated // StartCutscene("#L_Cut07") // or if you don't END Cutscene itself: IF True() THEN RESPONSE #100 CutsceneID(Player1) // actions EndCutSceneMode() END

As Lauriel says, can't you instead use global vars instead of myarea for regions? Master-slave relationship isn't particularly reliable. E.g. patch this into all master regions: IF !Global("current_region","global",3300) THEN RESPONSE #100 SetGlobal("current_region","global",3300) END For reputation change use SetGlobal("change_rep","global",1). Finally, put this into baldur.bcs: IF GlobalGT("change_rep","global",0) Switch("current_region","global") THEN RESPONSE #1100 IncrementGlobal("rep_1100","global",1) IncrementGlobal("change_rep","global",-1)

Almost the entire dialog consists of "choose party member" states, four initial and then four per each party member if PC refuses to bet them. I'm a little rusty to give you an actually working piece, but the logic would be like: COPY_EXISTING - bdthrix.dlg override READ_LONG 0xc states x = 0 FOR (i=21; i<24; ++i) BEGIN READ_LONG states + i * 16 + 8 trans_num SET insert%i% = ( (trans_num - 1) / 4) * x x = (x<3) ? x+1 : 0 END FOR (i=30; i<85; ++i) BEGIN READ_LONG states + i * 16 + 8 trans_num SET insert%i% = ( (trans_num - 1) / 4) * x

The original dialog is already twice, if not thrice, as messy, so... I'd be cautious about making it even worse. Looking at it again, I recall you can refuse Thrix his choice of a party member and have him choose again. So technically you can go with 3rd idea and append NPC at the bottom - even if two mods will conflict there, you can still write "nope, choose someone else" option to stay in line with the original, and get the previous NPC mod as a next choice.

I would read the number of transitions in each state, divide it by 4, and insert mod transitions at (trans_num / 4) * (state_ind - 21) points. EDIT So basically, what you suggest in 1, it seems. As for compatibility... You might have a point, but imo it's the least evil nonetheless - because in order to break something it requires another mod to 1) try to edit vanilla transitions and 2) do it without reading data first. PPS ...and also 3) be willing to poke the awful mess that is Thrix dialog file with a ten foot pole. This dialog was the worst in the entire SoD by a huge margin, bec

I am - special characters need to be preceded by \, to reverse them as a part of regexp formula. A-aand it only needs to be done when matching the string COPY_EXISTING ~SHOUT.BCS~ ~override~ DECOMPILE_AND_PATCH BEGIN REPLACE_TEXTUALLY ~Heard(\[NOTEVIL\],99)~ ~Heard([NOTEVIL],99) Detect(LastHeardBy)~ REPLACE_TEXTUALLY ~Heard(\[NOTGOOD\],99)~ ~Heard([NOTGOOD],99) Detect(LastHeardBy)~ END BUT_ONLY IIRC the only regexp allowed in replacement string is \1, \2 etc. to denote a match variable: REPLACE_TEXTUALLY ~\(Heard\)~ ~True() \1~ // We

If you donate the amount equal or greater than value corresponding to the current reputation (specified in reputati.2da), then it will increase by 1 point. No means of detection that I know of. You could try appending StartStore() actions with SetGlobal() to run a check afterwards if reputation is now greater than it used to be before starting dialog.

Those vars look like arguments for party AI scripts, to turn off item usage by clones. They don't affect actual item flags.

It certainly works.