What changed in EDuke32, build by build

It didn't turn out that useful and was giving a warning with one of the preceding changes.

Also, very slightly tweak a factor toward a "brighter" (farther visible) scene overall to account for the "circular" nature of the fragment distance (as opposed to an "ortho" distance in Build).

It was only ever used as upper bound to the time that a visibility change decays, but since it does that in an exponential fashion, there's really no point.

Now, if p->visibility differs from the constant visibility, the former converges toward the latter by three-quartering the difference each second totalclock increment (1/60th second). Negative player visibilities are not handled consistently throughout the different renderers, so make it look the same as 0 (can view to infinity).

So there's no "jump" from vis!=0 to vis=0 making the texture appear brighter.

Also override LTO to 0 in Lunatic builds.

Also, in test.elua, add a currently failing must-fail test (i.e. it wrongly succeeds where it should not!).

Because that function might have inserted tsprites itself, e.g. for the fake floor shadow. Also add one "spritesortcnt < MAXSPRITESONSCREEN" bound check in legacy ROR code.

That is, for shade of objects, use shade tables. For visibility, use GL fog. Mixing these two does not produce satisfactory results in areas where both shade and visibility darkening are high, such as around the E1L1 restroom.

- 'copy' may have them as source, 'getarraysize' works fine - 'setarray' and 'resizearray' are obviously forbidden - 'readarrayfromfile' and 'writearrayfromfile' is not implemented for them (use case?) Also, in the Makefile: don't use realpath on directories. It may give an empty string.

Add doc/how_to_build_lunatic.txt and doc/lpeg-lunatic.patch.

Don't yet make this official API though, since there are unresolved issues with newly created tsprites potentially being fed back to the animation loop. Add xmath.angvec(), xmath.bangvec(), tspr:set_sectnum(), tspr:setpos().

Having to tag these few variables and functions as ATTRIBUTE((used)) seems sensible, but what follows is just strange. OSD_Printf? headspritesect?

- swap 2d and 3rd args in xmath.rotate() -- now rotate(point, ang, pivot) - add vec3 method 'rotate', calling xmath.rotate - store game tic count in savegames

- some renames of functions/methods - con.actorvar: explicitly allow (for now) boolean and number values - added gv.gametic, player.holdskey(), player.all(), actor.check*()/hit*(), gv.rendmode, gv.REND, <bitint>:mask(), spr:getheightofs() - make read of nil var in "finalized" (live) module produce error, too - add test/helixspawner.lua

E.g. con.action{0, 4, delay=20}; for convenience, viewtype and incval are initialized to 1 (not 0) here.

That is, its value was only referenced during the duration of a function call that had previously set it. It was also never accessible from CON.

Using macros like AC_COUNT(t). Clean up related code: - comment out the dead condition noted in the previous commit - Lunatic: use get_count() instead of get_t_data(0) in one place, rename to _get_t_data(), i.e. make that method internal

... due to making hi/lotag unsigned in r3174. This commit keeps the compiler warning, the next one will remove it.

Also, get rid of the strange filename[len]=255 hack in loadboard() and make its file name arg const char* at last.

Also, clean up the saving/loading logic a bit: - On load failure, display message with purple color. - Take over the current file name ('boardfilename') only on success. - Check SaveBoard() return values in various places.

In other words, for a test rectangular sector, a sprite would be inside the sector in on all 4 edges and all 4 corners. Previously, it would have been the lower right portion only (*excluding* LL and UR corners), which led to map editing issues.

The main thing to note is the "half-open" nature of the x/y range checks.

- Pass original module name (dot=dirsep) to module via our require() - geom.lua: fix some operations using the vector type constructor - geom.lua: provide constructor for ivec3, useable like vec3

Also, an external 'minitext' with optional shade and pal. args and documentation for ps:padecol().

They don't get registered on Windows for some reason, and mapstate debugging is best carried out using scripting code, anyway.

- Handle local gamevars. - Restore gamevars from require('end_gamevars').

It's hard to call this a fix, since ideally, buffer sizes like these would be only as large as needed in the worst case.

See http://forums.duke4.net/topic/6526-eduke32-crashing-when-loading-a-dukeplus-map-save

(This is the module that implements much of the "hard-coded" functionality formerly on the C side.)

Add a test case in test_tileoffsets.map.

Don't (yet?) commit the generated HTML.

However, from the command line, reverse the situation: dirseps must be passed as '/', dots are forbidden (except in the trailing ".lua").

It is a 32-bit signed integer. No version bump necessary, although CON code accessing this new member will not work with earlier revisions (obviously).

Also from Lunatic, make these members read-only and provide methods that allow setting them to either -1 or a number in [0..MAX{TILES,SOUNDS}-1].