In windows build 1099 and build 1108, Game->GetComboData(0, 0, 0) or Game->GetComboCSet(0, 0, 0) may cause a crash when the map parameter is 0. This is easily seen in this quest:
http://www.mediafire.com/file/zyll0kh2vmm/ZCGDemo003.qst
This quest runs fine in build 1074. In build 1099 and 1108, running neary any instance of Game->GetComboData or Game->GetComboCSet will instantly crash the player because the map accessed is 0. Adding 1 or more to all the map parameters prevents the crash, but the workaround makes accessing the first map impossible.
Minor expirementing has revealed that not every instance of this causes a crash, but the value returned, when displayed with Trace(), is not the correct value of the combo accessed. It is most likely certain values for the screen parameter cause the crash, while others return from the wrong location.
Note: If 1 is supposed to be the minimum value for the map parameter, make the map accessed one less than it currently is (0 is the first map, 1 is the second map, etc).