Jump to content


Member Since 27 Aug 2004
Offline Last Active Today, 01:30 PM

Topics I've Started


23 February 2018 - 02:12 PM

Anyone knows if this object actually do something?

I'm pretty sure it doesn't. Despite this note back from 2016:  http://www.shsforums...s-set-a-target/


:help:  :undecided:



actuallyincombat and combatcounter

03 February 2018 - 07:11 AM

These triggers check on variables in the 'current area'.


If you noticed that these triggers work sometimes differently in baldur.bcs - it is because baldur.bcs calls the current master area to check on combat.

So if the combat occurs in a non-master area, baldur.bcs won't detect it.



Effects (spl, itm, eff) saving throw field extra bits.

20 December 2017 - 09:03 AM

These are available since IWDEE was released.


Effects (spl, itm, eff) saving throw field extra bits.


I don't see this on IESDP so i guess this wasn't published yet.

32 - evade spell

64 - evade breath

128 - evade death

256 - evade wand

512 - evade polymorph

these bits are connected to the thief evasion ability, there is one bit for every saving throw type, respectively. (Sadly, i don't know much more about these)

I don't see them used, so if evasion works without them, then ( :undecided:).


1024 - ignore primary target

2048 - ignore secondary target


These are used when a .pro file has a line AOE (see scorcher.pro).

Effects marked by 1024 won't affect the direct target of the scorcher projectile

Effects marked by 2048 won't affect the bystanders.


opcode 234 wrong desc (affects EE and BG)

11 December 2017 - 11:54 PM

The amount/restriction type field (param2) has the order wrong.


The high word (3rd and 4th bytes) affect the restriction type (0, 1, 2)

The low word (1st and 2nd bytes) affect the number of usable slots (3 is the maximum by the way, as there are 3 resource fields in eff v2.0). 


Example in spwi908, which has no restriction (chain contingency) :  00a2h Parameter 2      00000003


That is a WRITE_LONG 3 or WRITE_BYTE 3, so low word, first byte, whatever we call it :)


Also a typo in the 0 type: Contingeny 

bardsongs and timing mode 10 in effects

07 December 2017 - 03:38 AM

For a very long time, i didn't know that timing mode 10 (exact duration) is the same as timing mode 0 (duration), except timing mode 10 doesn't multiply timing with 15.

DLTCEP had this timing mode named as 'trigger', because i've always tested the timing mode with 0 or very small durations, so it never occurred to me that this timing mode has an actual settable duration. IESDP has adopted same 'trigger' naming for this timing.

This timing mode exists in SoA and was likely implemented for the custom bardsongs. See SPCL542A. 


Note, the duration is set to 100 - this is the standard duration for a bard song pulse. The hardcoded vanilla bardsong uses the same timing internally.

Some bardsongs (SPCL751A) use a duration of 7 with timing mode 0. (7*15 is close to 100, but isn't exactly 100)