Proposed change to dist= in EndMissionTake

[krzys_h]

I assume that you plan not to change the default values but to force to define them at all times, so that defult values become redundant.
In my opinion it's a better option than changing default values.

What I want to do is make dist= required if you specify the pos= too. So something like this is not allowed:

Code:

EndMissionTake pos=10;20 type=Titanium min=1

But both of those are:

Code:

EndMissionTake pos=10;20 dist=8 type=Titanium min=1 // equivalent to the previous, no longer allowed version
EndMissionTake type=Titanium min=1 // detects anywhere

This should make it so that outdated levels throw an error instead of loading with broken ending conditions, unless somebody put the SpaceShip at 0;0 and used defaults for both pos= and dist=.

Will have to update most of the missions.

That's exactly why I'm warning everyone beforehand. If you want your levels to be compatible with future versions, make sure you specify both pos= and dist=. If you want to keep maximum compatibility with old versions, ALWAYS specify both pos= and dist=. If you only care about versions after this change (which has not occurred yet!) you can drop pos= and dist= in conditions that check for the whole map.

What is the default range exactly? 8 metres?

Yes, the current default for dist= is exactly 8 meters