Hm, will the change also allow us to let a team stay alive even after all its units are destroyed so having 0 units would be a valid state? Would be useful for stuff like team games where all teams of an alliance should remain alive as long as the alliance survives so units can still be given to the "dead" teams and of course mods that have a different loss condition while allowing you to create units even without existing units.

No. If you lose your last unit your team is dead. Afaik there is no option to change that.
So if you start without any unit you are alive forever because you can't be killed.

Ultimately the game end condition should be moved completely to Lua too IMO. No default end condition built into engine, just a Lua call-out to trigger game end with a (list of) winning (ally)teams.

Uh... whats the problem with setting defaults, and then overriding those with lua?

Harder to adapt.

If the default game end condition is in Lua already, you can just copy the gadget and modify it a bit.

If the default game end condition is in C++, you have to port it to Lua first, and figure out how to disable the C++ code.

to avoid game ending when all units are destroyed you can have an indestructible and not noticeable null unit to hold the game

Which, of course, is an ugly hack that would be better replaced with an overridable default Lua gadget that implements the current behavior.

Exactly.

My point is that in the future the mods actually take more lines of lua code than the engine uses c++ code...

And that is a good thing because if you want all that extra code then yay, but if you don't then you can be uber lightweight. It also means a tidier stabler and faster core engine.

Yeh but it also means to update 100 mods intead of 1 engine if theres some bug in their lua codes they all share.

I don't like it that you've chosen this particular subject to troll, if your serious about it then stop raising and arguing exactly the same points and regurgitating the same discussion

Im not trolling

When the engine updates the player has to download spring again.

When a mod updates, the players don't have to do anything. Their client downloads it automatically.

Imho, the best behavior in general is an over-ridable default gadget, but obviously the Spring devs disagree since we're starting to see breaking changes with a nice package of "here's how to get the old behavior back" which I suppose is a bit cleaner for new projects.

note that some mods take 400megs, engine takes 18megs

and i expect every mod be huge like that in the future...

With the pool format or the old SD package system for CA, updating can be piecewise, rather than re-downloading the whole archive.

Updating a bug fix in a 400meg mod requires downloading 1k. As Neddie stated.

Trademark, you are an old dinosaur who is stuck in the past in every way. You are out of the loop when it comes to lua, when it comes to the rapid system and you should stop talking and start listening.

You will see, just remember, i told ya.

CA archive is ~90MB, unpacked 200MB.
Unpacked, LuaRules is 2.1MB (including ~350k Images), LuaUI is 16MB (biggest part is sounds and images, Widgets are less than 4 MB).

Biggest chunks in CA are unittextures, models and sounds.