Build 5888
SVN-
General
Minor changes to gamevar error handling
-
General
Misc cleanup. Removed ability to use .CON files found in the .GRP when the .CON files found in the directory can't be compiled.
SVN handles and Git names are merged into one person.
Minor changes to gamevar error handling
Misc cleanup. Removed ability to use .CON files found in the .GRP when the .CON files found in the directory can't be compiled.
Fix detection of menu sounds in EVENT_SOUND
Support saving specified CON arrays in map states
Remove some unused gamevars pertaining to the original multiplayer code. DONT_BUILD.
Fix EVENT_DISPLAYROOMS and EVENT_DISPLAYROOMSCAMERA RETURN values
Fix problem with C-CON sector and wall structure access. Oops.
CON compilation and debug message fuckery affecting virtually nobody
Clean up a couple instances of direct usage of a magic number in the CON compiler. DONT_BUILD.
Make the bitptr stuff in the CON compiler more readable.
Minor change to some gamevar warnings. DONT_BUILD.
Fix CON compiler errors. Me no smart.
Misc cleanup, add shorthand versions of getplayer, getactor, etc.
Treat "[]" as "[THISACTOR]" when accessing structure members through CON.
Add "klabs" keyword to CON, to take a gamevar and set it to its absolute value. The internal "inv" function to invert a gamevar's value has also been exposed externally.
Add commands added in previous commit to g_keywdate[], clean up a few CON compilation warning messages
Adds the following keywords from M32script into CON: shiftvarvarl, shiftvarvarr, ifvarvarle, ifvarvarge, ifvarvarboth, whilevarl, and whilevarvarl.
This also adds the shorthand versions of some commands, like "set" for "setvarvar", "add" for "addvarvar", "ife" for "ifvarvare", etc. There are about 30 of these. Because some of these names may already be used in some projects as variable names, this revision also includes a somewhat large change in variable naming rules: gamevars may now have the same names as CON keywords, with the caveat that the masked keyword is no longer accessible. This results in a warning at compile time but should ensure nobody's project ever stops compiling due to the introduction of new keywords.