Jump to content

CamDawg

Member Since 18 Sep 2003
Offline Last Active Private

Posts I've Made

In Topic: SCS v32 Release Candidate (now Version 6) Available for Testing

26 November 2018 - 12:14 PM

Secondhand bug report: Fireshield blocks insects cast directly, but not from the secondary spread--e.g. casting Insect plague on a fighter next to a fireshielded mage will get insects spread onto the mage.

FWIW I'm unable to repro this with RC5.


In Topic: SCS v32 Release Candidate (now Version 6) Available for Testing

26 November 2018 - 09:48 AM

Secondhand bug report: Fireshield blocks insects cast directly, but not from the secondary spread--e.g. casting Insect plague on a fighter next to a fireshielded mage will get insects spread onto the mage.


In Topic: The probability field in effects

21 November 2018 - 01:05 PM

And I was hoping Galc would take credit for being the person who originally pointed out that second bug (effect ordering) to me, but he's modest as well as smart.


In Topic: SCS v32 Release Candidate (now Version 6) Available for Testing

21 November 2018 - 01:03 PM

Thanks. What version of the game?

2.5.16.6 BG2 EE.

The issue of being disrupted by 0 damage has been fixed on all EE platforms except BG2EE. BG2EE will be getting this fix with the upcoming 2.6 patch.

In Topic: The probability field in effects

21 November 2018 - 12:56 PM

Another oddity I noticed some time ago: if a spell contains effects in multiple probability ranges (e.g. 0-9, 10-19, 20-29, ...), you might experience effects triggering from two or more (or zero) independent ranges on rare occasions. This is caused by a quirk in the game engine if auto-pause conditions "Spell cast" or "End of round" are active.

Oh right, forgot to mention this as well. Yeah, auto-pause on spell cast can do two fairly bad things--one, as you've already mentioned, is that it can re-roll the probabilities so that not every effect gets the same roll (for further reading, any old thread about the duration of the Friends spell in the Fixpack). Another, but lesser known problem, is that it can sometimes cause the engine to apply spell effects out of order, which can cause all sorts of bad things for spells like Otiluke's where the order is necessary for the proper functioning of the spell.

 

edit: I should note that while auto-pause on spell cast is the most common way to experience these bugs, *any* pause at the critical moment can produce the same result.