Spring RTS Engine

Split from viewtopic.php?f=1&t=33366.

This one doesn't make sense. If it's always continuous (1), why is the default 0? Why is this even listed if it's removed?

int collisionVolumeTest Default: 0 Removed in 90.0 (Now always continuous)
The type of test used to detect collisions. Can be 0 (discrete) or 1 (continuous). Use the latter for catching high speed projectiles which may otherwise 'skip through' small collision volumes, but beware of the increased performance cost.

it was default 0, then changed to default 1 and then the tag was removed as a whole

Why is this even listed if it's removed?

Cause it's not auto-generated ?

So should it be removed or have its default set to 1?
I'm asking because my version of boxxy still generates that and I wasn't sure if it still had any effect (sometimes tags are only deprecated, but not fully removed).

you got the source luke

How to explain deep self inflicted laser wounds to your doctor - a Guide .pdf

might help

knorke (and possibly others) felt it better to maintain old doc for deprecated tags / lua API for those working on older engine versions etc.

So, for all those engine versions where the tag did (does?) exist, the default of 0 is correct.

gajop wrote:Why is this even listed if it's removed?

It is listed because answers questions like this:

gajop wrote:I wasn't sure if it still had any effect

If it was deleted from wiki then one could not be sure if it maybe just missing as an oversight.
Similiar if things change, like parameters being added to functions.

In theory such documenation would have resolved many discussions before they start. In practice it never worked because in this community a link to sourcecode or git history that shows something (like if a tag/variable is string or boolean) is a weaker arguement than "spring works in strange ways."

Afaics tags that are removed can be removed once they are removed, and tags that are deprecated/changed can be kept and marked deprecated/changed. The engine changelog is the place to record "removed XYZ", and the point of deprecation is that it gives time for games to update. In general I don't think we should support game development in long gone engine versions, and in most respects we don't.

Silentwings wrote:The engine changelog is the place to record "removed XYZ".

Is a straight text file. Not a good place to have the only record of removals.

For what reason?

edit: Hmm - maybe it would be nicer to include links to source/commits. There is https://springrts.com/wiki/EngineChange ... ontentDevs.

I agree with Silentwings here. Things that are fully removed shouldn't be listed here. A wiki change log would be better.

On Love2d wiki they're super clear about added, deprecated, removed, and renamed API.
For example: http://www.love2d.org/wiki/SpriteBatch:addq





It would be great to have Spring API changes as nicely documented.

Then I understand you might feel Spring is different, or run a different wiki software, or that if I want that I should do it myself, whatever.

We are all bitches posting, waiting for the weakest one to give in and do the hard work..

I was wiikiadd once too you know - but then i took a edit to the knee..