Spring dev must honor backward compatibility! plsss

[knorke]

IMO its more fun if Spring dev simply document all tiny nuance here: http://springrts.com/wiki/Lua_Scripting
Its better to make some sensible comment there rather than making a code change that kill a Mod.

I would get confused too if the stuff is not consistent but if the documentation is right, then I could always refer to it I think.

It is what everybody thinks at first: "Why dont engine devs update wiki if they changed something? Why is change not explained more?"
Changes acuelly ARE all in changelog. ! means backward compability broke
But why not wiki or with more detail?
Nobody has time for anything.
There are ~5 people working on engine (rollers) but some dozens people working on mods. (walkers)
That means if rollers update wiki, it is not so efficient use of time.

[FLOZi]

In fact;
every change documented in the changelog that requires an update to current wiki pages is transferred
- primarily by myself. (Not to say that devs don't ever update the wiki - They most certainly do, and I get support from jk and kloot in particular if I don't understand e.g. how to document a new lua api function, or exactly how a new def tag works )

However, I do it after the release is made usually.

p.s. I have some thoughts about how the API info is presented but there are issues to work through there. LuaCallinReturn is my priority atm, note that with the template you can link directly to a particular function as I did with the def tags..

[zwzsg]

For those who decry the death of minor projects... resuscitate them. You (knorke and zwzsg) are far more capable of it than most.

I attempted to maintain a minor KDR_11k project afloat for a couple years, it was exhausting!

[FLOZi]

It is perhaps something we should do better as a community.

[PicassoCT]

Do avoid stuff that seems break prone..

[smoth]

In the the YEARS that I hsve done spring content dev wotk the only real killer was pathing related.

Oo
The "removal of .n entry in array tables" required updating of all games, including yours, or they became unplayable. (at very least some "default" widgets like healthbars broke)

Was a stupid easy fix.

"What engine change has broken game play!?!" appearently is a common thought, for you too: http://springrts.com/phpbb/viewtopic.ph ... 2&p=493107
You even made similiar thread as this one about engine changes breaking games: http://springrts.com/phpbb/viewtopic.php?f=12&t=23913

hurr dut a thread from 3ish years ago. Because in that time I have not changed at all. You love to believe peoples attitudes have not changed. I wish you would stop, because a post from 3 years ago hardly match my personal current attitude snd growth. After that thread my questions and concerns were partially answered with greater developer transparency about engine changes and by discission.

The fact that you cite such a dated thread is completely inappropriate.

[Forboding Angel]

I hate it when he does that. He seems to have this weird idea that peoples opinions can never change and once you have stated something in public, no matter how long ago or irrelevant, you must stick with it to the grave.

[knorke]

You mentioned the past yourself by saying "In the the YEARS that I hsve done spring" with years highlighted. So jun 2011 (=2 years) did not seem so old.

[Forboding Angel]

Knorke, it is possible to look upon the past differently in the future than you did at that present moment.