diff --git a/polymer/eduke32/source/lunatic/doc/lunacon.txt b/polymer/eduke32/source/lunatic/doc/lunacon.txt index fdb48714d..076ea91cf 100644 --- a/polymer/eduke32/source/lunatic/doc/lunacon.txt +++ b/polymer/eduke32/source/lunatic/doc/lunacon.txt @@ -64,9 +64,10 @@ The stand-alone LunaCON script, `lunacon.lua`, needs {LuaJIT}[LuaJIT] for execution and {LPeg}[LPeg] as additional dependency.footnote:[In order to translate some very large CON files, minor modifications have to be made to LuaJIT and LPeg. Refer to `lunatic/doc/how_to_build_lunatic.txt` in the EDuke32 -source distribution for details.] It expects one or more names of root CON -files together with any number of options, in any order (arguments starting -with a dash are always interpreted as the latter). +source distribution for details.] The script also requires `con_lang.lua` to be +present. It expects one or more names of root CON files together with any +number of options, in any order (arguments starting with a dash are always +interpreted as the latter). .Example usage ---------- @@ -153,10 +154,12 @@ set the output behavior of the stand-alone translator, or toggle various error conditions. `-fno` (stand-alone only):: -Disable printing out the generated code and any diagnostic messages. +Disable printing out the generated code and validating its syntax. `-fno=onlycheck` (stand-alone only):: -Disable printing out the generated code, keeping only the diagnostics. +Disable printing out the generated code, but validate whether it is +syntactically legal Lua code. A failure of this check represents a bug with +LunaCON itself. `-ferror-nostate` (default: on):: If enabled, an attempt to call a `state` that was not previously defined diff --git a/polymer/eduke32/source/lunatic/doc/lunatic.txt b/polymer/eduke32/source/lunatic/doc/lunatic.txt index 5af702bb2..e58d071ef 100644 --- a/polymer/eduke32/source/lunatic/doc/lunatic.txt +++ b/polymer/eduke32/source/lunatic/doc/lunatic.txt @@ -1004,7 +1004,7 @@ thought to be overlaid with a structure containing as many members as the array has elements, all having the element's type. Currently, there are with two kinds of names: weapon names and inventory -names. In the following, they will be marked using a the following notation: +names. They will be marked using notation like this: ========== _`i16`_ +ammo_amount[_weapon_]+ @@ -1042,7 +1042,7 @@ velocity is multiplied before calculating its new position. On various occasions, the ultimate scaled factor is the difference of `runspeed` and at most 8192. -_`i8`_ `curr_weapon`:: +`curr_weapon`:: The index of the player's currently selected weapon. @@ -1058,7 +1058,7 @@ The first argument `fadefrac` specifies the starting blending coefficient; `r`, components, respectively. + Both `fadefrac` and the component intensities are first clamped to the range -[0.0 .. 1.0]. The resulting values are interpreted as a fraction, 0.0 meaning +[0.0 .. 1.0]. The resulting values are interpreted as a proportion, 0.0 meaning no blending/no color and 1.0 meaning full blending/full color.footnote:[Currently, for implementation reasons, a value of 1.0 results in only _almost_ full blending or presence of the specified color component.] diff --git a/polymer/eduke32/source/lunatic/test.elua b/polymer/eduke32/source/lunatic/test.lua similarity index 99% rename from polymer/eduke32/source/lunatic/test.elua rename to polymer/eduke32/source/lunatic/test.lua index 1b54f08e9..953df1335 100644 --- a/polymer/eduke32/source/lunatic/test.elua +++ b/polymer/eduke32/source/lunatic/test.lua @@ -277,8 +277,12 @@ gameevent -- Test of INTERNAL member _pals. -- NOTE: setting colors partially is bad! E.g. after an item is -- picked up, col[0] and col[1] remain and tint everything greenish. - ps._pals[2] = 20 - ps._pals.f = 30 + if (DBG_ ~= nil) then + -- XXX (unrelated to these lines): issuing tinting makes it flicker + -- sometimes in the GL modes. + ps._pals[2] = 20 + ps._pals.f = 30 + end end }