Fiann of the Silver Hand Posted November 25, 2015 Posted November 25, 2015 (I'm crossposting this to the relevant areas.) Re: effect 294, set existence delay IESDP says that param 1 is undefined, and param 2 sets the delay between barks (-1 = do not play at all, 0 = "normal", 1+ = increasing time between with 1 as fastest) These were the tests I ran for varying params on VOIWES. p1: 0 p2: anything result: no difference between them or with unmodded (i.e. fired very infrequently) p1: 1 p2: 10 result: super short delay (< 0.5 second) and interrupting itself to start a new one; continuously runs p1: 10 p2: 10 result: slightly longer delay than above (more of the bark played), but still interrupts itself; continuously runs p1: 20 p2: 10 result: delay between barks varied anywhere from <1 second to about 6 seconds; could still interrupt and run in bursts p1: 0 p2: 60 result: same as unmodded p1: 1 p2: 60 result: fired immediately and started anew when completed; no interrupt p1: 30 p2: 60 result: fired immediately, with ~1 to 3 second delay between; no interrupt p1: 200 p2: 60 result: fired immediately, with delays between from 6 to 34 seconds Clearly param 1 controls the range of the delay between barks, and param 2 seems to set the minimum delay amount. For the chanters in Candlekeep, a setting of 100 & 60 seemed to replicate BG1 behavior.
Avenger Posted November 25, 2015 Posted November 25, 2015 Param2 is unused as far as i know. DLTCEP says: The effect modifies stat #184 to param1
Fiann of the Silver Hand Posted November 26, 2015 Author Posted November 26, 2015 Hah. That would explain it all if it were simply IESDP & NI being wrong about which param is unused.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.