Skip to content

TobEx: 19

DanBoulosDanBoulos Member Posts: 146
edited July 2012 in Fixed
Current Behaviour:

Effect #12 “Damage”: killing someone with magic fire damage causes a WEIRD damage assertion failure

Expected behaviour:

Effect #12 “Damage”: killing someone with magic fire damage does not crash the game

Revision:


Added DAMAGE_MAGICFIRE right after DAMAGE_FIRE to match DAMAGE_COLD/DAMAGE_MAGICCOLD. Avoids assert
Post edited by Bhryaen on

Comments

  • CadrosCadros Member Posts: 253
    Confirmed. Killing Nobelmen with burning hands did not crash the game
  • IgneousIgneous Member Posts: 368
    I can confirm fixed, as well.

    Tested by creating a Burning Hands knock-off and changing the damage types to 33554432 (Magic Fire). Placed the new version in the override folders of my Tutu and BGEE installations.

    In Tutu, using the new Burning Hands to slaughter a hapless tutorial monk crashed the game. (Couldn't see the error message, though. Application just hanged itself.)

    In BGEE, whee! No crash, either on damage or death. Only tested on a few creatures: tutorial monk, Winthrop, gibberling... but they all check out. Magic fire works, baby.
Sign In or Register to comment.

2024 Overhaul Games, a division of Beamdog. © 2024 Hasbro, Inc. All Rights Reserved. Baldur's Gate, Dungeons & Dragons, D&D, Forgotten Realms, Baldur's Gate, Wizards of the Coast and their logos are trademarks of Wizards of the Coast LLC in the U.S.A. and other countries, and are used with permission. Hasbro and its logo are trademarks of Hasbro, Inc. and are used with permission. © 1998 BioWare Corp. All Rights Reserved. BioWare, the BioWare Infinity Engine and the BioWare logo are trademarks of Bioware Corp. Black Isle Studios and the Black Isle Studios logo are trademarks of Interplay Entertainment Corp. Atari and the Atari logo are trademarks owned by Atari Interactive, Inc. All other trademarks are the property of their respective owners.