i Entire installation instructions for the Baldur's Gate Mega-Mod

WARNING: cannot verify action ~SetTokenObject(“DORCNAME”,)~:
Failure(“lexing: empty token”)
should say: ~SetTokenObject(“DORCNAME”,PLAYER1)~
WARNING: cannot verify trigger ~CheckStatGT(Player,12,CHR)~: Not_found
should say: ~CheckStatGT(Player1,12,CHR)~
These and all similar warnings signify typos from the mod author which cause an error in the ACTION.IDS.
The suitable script block will fail in the game..
WARNING: cannot verify action ~Global(“freebae”,”GLOBAL”,1)~: Parsing.Parse_error
should say: ~SetGlobal(“freebae”,”GLOBAL”,1)~
These and all similar warnings signify errors which cause an error in the ACTION.IDS. The suitable script
block will fail in the game.
It is astonishingly difficult to compare the Debug file and the program code to find a problem which is caused
by a single missing type!
The errors shown are only examples of similar errors. These errors were of course corrected a long
time ago!
3. Error in the program code
APPENDIX
Messages like the following must be exactly checked anyway. Whether an error is slight or not, depends on
the fact which block is changed: it can mean that some scripts are not installed and thereby some creatures
are not as clever as provided, however, can lead also to serious malfunction in the game.
WARNING: cannot find block matching [BGTTweak/3/xKAGAIN.BAF]
These and all similar warnings, point out that the block to which something should be added has already been
changed by a previous mod, which is why this action has failed.
Warning: cannot find block matching [redemption/bcs/ AR6200asc.bcs]
A special case of the previous one: Redemption and Longer Road search not only for specific script blocks,
but also for blocks in files in the override folder. If they are biffed, the installation fails.
Not enough arguments to [NumTimesTalkedTo]. Recovering.
These and all similar warnings signify an error in the mod. The corresponding script block or dialogue will fail
in the game.
- 242 -