[2.50.3] Something Strange with SetComboSolid

[DarkDragon]

Here is the proposed refactoring. Old ZASM data structure:

struct ffscript
{
word command;
long arg1;
long arg2;
char *ptr;
};

New one:

struct zasm
{
int16_t command;
int32_t arg1;
int32_t arg2;
};

struct ZAsmScript
{
// ZASM script types
// Would be an enum, if enums were portably serializable
const int16_t ZA_GLOBAL = 0;
const int16_t ZA_FFC = 1;
const int16_t ZA_ITEM = 2;
const int16_t ZA_GUY = 3;
const int16_t ZA_WPN = 4;
const int16_t ZA_LINK = 5;
const int16_t ZA_SCREEN = 6;

// Version of ZASM this script was compiled for
int16_t version;

// Type of the script (one of ZA_ values above)
int16_t type;

// Name of the script, if the script was compiled from ZScript
// For debugging and logging errors, etc.
int16_t name_len;
char *name;

// The ZASM itself
int16_t commands_len;
zasm *commands;
};

[DarkDragon]

This fix has been implemented. Specifically:
- Saffith's fix will take effect the next time a quest's script is recompiled. Old quests still use the old behavior. Old quests loaded into ZQ and saved, without recompiling scripts, will preserve the old behavior.
- All ZASM scripts now carry with them some metadata about their ZASM version, type, etc. Might be useful in the future.