Bug #35417

TazokSays blocks in AR2400.BCS and AR2900.BCS prevent further script blocks from firing

Added by Astro BryGuy over 1 year ago. Updated about 1 year ago.

Status:Closed - FixedStart date:02/08/2018
Classification:Public ItemDue date:
Assignee:-% Done:

100%

Category:-
Target version:Public Bug Reports - 2.5.17.0
Found In Version:Public Bug Reports - 2.5.10

Description

1. Add the following block to the end of AR2900.BCS via NearInfinity or DLTCEP.

IF
True()
THEN
RESPONSE #100
DisplayStringHead(Player1,2106)
END

2. Start a new game with Abdel Adrian.
3. Go to AR2900. See the words "Hello There" above his head.
4. Go to AR1900. Watch Bandit Camp movie.
5. Go back to AR2900. No more "Hello There" words above Abdel's head.

Observed
Script blocks added to the ends of AR2400.BCS or AR2900.BCS will not execute once AR1900 has been entered.

Expected
Script blocks added to the ends of AR2400.BCS or AR2900.BCS execute even if AR1900 has been entered.

Notes
The area scripts for AR2400 and AR2900 contain the following blocks:

AR2400.BCS:
IF
Global("TazokSays","GLOBAL",1)
THEN
RESPONSE #100
ActionOverride("Raiken",DestroySelf())
END

AR2900.BCS:
IF
Global("TazokSays","GLOBAL",1)
THEN
RESPONSE #100
ActionOverride("Teven",DestroySelf())
END

Since both blocks only depend on the variable TazokSays, and neither changes the variable, they both will continuously fire if TazokSays = 1. This has the effect of preventing any blocks appended to the ends of these BCS files from executing after the party has entered AR1900 (which sets TazokSays = 1).

Adding Exists("Raiken") and Exists("Teven") checks to AR2400.BCS and AR2900.BCS, respectively, should fix the issue. This is what I do in BG1NPC to mitigate, and it seems to work fine.

FYI - This was initially reported in January 2015, but is still present in v2.5.10.

https://forums.beamdog.com/discussion/39023/tazoksays-blocks-in-ar2400-bcs-and-ar2900-bcs-prevent-further-script-blocks-from-firing

History

#1 Updated by Anders Svensson over 1 year ago

  • Status changed from New to Resolved - Fixed

#2 Updated by Anders Svensson over 1 year ago

  • Status changed from Resolved - Fixed to Closed - Fixed
  • Target version set to Next Update
  • % Done changed from 0 to 100

Fixed in version 2.5.16.4.

#3 Updated by Anders Svensson about 1 year ago

  • Target version changed from Next Update to 2.5.17.0

Also available in: Atom PDF