Spring RTS Engine

I don't know what format yall are going to use for your heightmaps, but I suggest you standardize on a format the also contains the normalized depth component, example: channels: R(0) Nx (Normal X component) G(1) Ny (Normal Y component) B(2) Nz (Normal Z component) A(3) Dp (normalized depth) You can...

Spring.MoveCtrl.SetGravity()
be wary of incompetence.

unitname = "gmsnipercustom",

should probably be:

unitName = unitName,


alternatively, after the table definition:

unitDef.unitName = unitName

or

unitDef['unitName'] = unitName

The Spring C++ code no longer knows anything of FBI files. FBI files are actually parsed by lua code that is included in springcontent.sdz (the change came with a significant speed-up over the engine's boost based TDF parser). The best term to use would be "unitDef tags". Note that luadefs...

Look at the top of layout.lua. IIRC, the now defunct
gui_tooltips.lua also used the same mechanism (or
at least the one on my machine did).

IIRC, it only applies changes during Initialize() and ViewResize()
call-ins (so you can still resize it). It would also be easy to have
the widget kill itself after initialization.

minimap_relative.lua
(I think it was in SVN at one point)

wrong? how so?
(besides the fact that your quoted version got truncated...)

Related gadgets are already included in springcontent:

https://spring.clan-sy.com/svn/spring/t ... s/Gadgets/

P.S. They probably haven't been tested in a while.

I don't think that I finished adding ModValidMaps as an engine check.
That should probably be done before removing the old start scripts.

Don't know if anyone has been keeping it up to date:

http://spring.clan-sy.com/websvn/filede ... rev=0&sc=0

Fair enough. You're right, I'm wrong. Have fun

"removed from the engine" -- TdfParser is the engine's interface to TDF

"MapOptions can be used with TDF *.smd files" -- not useful? At the end of mapinfo.lua: if (Spring.GetMapOptions and mapInfo.defaultoptions) then local optsFunc = VFS.Include('maphelper/applyopts.lua') optsFunc(mapInfo) end Note that there's also a setupopts.lua in the same directory. Sorr...

TdfParser is only required for script.txt, and SM3 maps, iirc.

edit: I forgot, the old lua startscripts use it too.
(this all relating to the engine, and not AIs, etc...)

A couple of hints:
- MapOptions can be used with TDF *.smd files
- maps are loaded via mapinfo.lua, take a look there

bumpmapping -- too easy, too 90's, no fun
relief mapping, had a picture lying around here somewhere...

See the top of layout.lua for command button language
localization. I also had unit name / description language
localization started in the gui_tooltip.lua widget (which has
since been removed, iirc).

AllowStartPosition()