Spring RTS Engine

Loopbackattack can dramatically increase or decrease a fighter's usefulness. If it is turned on, a fighter may be super powerful, if it is off, it may be useless. I'm not exaggerating this at all.

There needs to be a way to set it ON or OFF permanently by the mod-maker, on a per-unit basis. I've asked about this before and everyone agrees but nobody with the skills to make the changes notices.

So as to not break compatibility we could use:
0=Not available
1=Optional
2=Always on

A more consistent approach would work the same as high trajectory:
0=not available
1=always on
2=optional

AFAIK no mods currently use this option anyway since, as mentioned, it is at best completely useless and at worst severely exploitable and obscure, so it wouldn't really matter which option is used. Please make this fix in time for the next release if that's possible, from what little I know of coding it shouldn't be difficult.

Thanks very much. For GEM at least this is of the same importance if not more important than proper hitboxes, but would require a tiny fraction of the work.

This would be epic win for Gundam except... loopback doesn't work if the target is a plane AFAIK.

The reason it is not used by anyone is because it is difficult to know what is available, how these settings exactly work, and an easy way to see what the default behaviors are in Spring right now unless you take the epic plunge into the code itself. There are so many options it is difficult to keep track of them all. And because there are so many built in exceptions, it makes it doubly difficult.

Someone went to the trouble of programming this feature, all it requires is a switch to be put in place so it's usable, and nobody can be bothered? This is insane.

Do you think I'm exaggerating? It is absolutely USELESS in its current state and any modder can see that. I've made threads on this issue before and not one single person disagrees, everyone wants it done.

Why? Because no mod developer in his right mind would even consider using this tag in its current state, so if nobody's going to be bothered putting a simple yes/no/selectable switch on it you might as well just remove the damn thing since it's garbage code.