Spring RTS Engine

1) I see commander and valkriye it came in next to each other on ground in middle of our territory.
2) I click attack on the valkryie to make the damn fighter attack it
3) Commander notices me, starts building defender.
4) fighter doesnt attack valkriye right away, it needs range, okay fine
5) fighter comes back around, and even though im clicking on the grounded valkriye - it doesnt shoot at it
6) instead it shoots at defender
7) it comes back around for a second pass, fires off one missile at valkriye, and defneder is finished - valkriye lives, avenger dies

tl;dr fighters dont obey the targets they're being given right away.

simialr situations have happened before.

Dragon45 wrote:1) I see commander and valkriye it came in next to each other on ground in middle of our territory.
2) I click attack on the valkryie to make the damn fighter attack it
3) Commander notices me, starts building defender.
4) fighter doesnt attack valkriye right away, it needs range, okay fine
5) fighter comes back around, and even though im clicking on the grounded valkriye - it doesnt shoot at it
6) instead it shoots at defender
7) it comes back around for a second pass, fires off one missile at valkriye, and defneder is finished - valkriye lives, avenger dies

tl;dr fighters dont obey the targets they're being given right away.

simialr situations have happened before.

Oh poor Dragon, I'm so sorry I lived to kill you that game.

Also: BA T1 fighters suck.

Well it's not an issue of living or not; it's just that the interface didn't behave in the way I expected. I obviously won't rely on that behavior next time, and obviously ill still just adapt in whatever ways i can until it does

It's a mod issue. THis does not belong in Help and Bugs.

well, it did happen to me in CA, too.

Its not a mod issue and t1 fighters dont suck.

It couldve been avoided by changing the fighters firestate. If its set to fire at will, it does try to attack the designated target, but it will also fire anything that comes in its path before it can attack that target. So its not guaranteed it has reloaded when that target comes up. But yeah nobody really changes firestates on the run like that on any unit except on janus...

Look at how miserable my T1 fighters went in the first 5 minutes against cefte atlas/comander combo.

I don't know if it's about the fighter or I was plain unlucky

http://replays.adune.nl/?1669

Microing BA T1 fighters is a pain.

Also, Nio and I were discussing making an engine change whereby you can set the priority target of units to a specific unit or unitID.

REVENGE wrote:Microing BA T1 fighters is a pain.

Also, Nio and I were discussing making an engine change whereby you can set the priority target of units to a specific unit or unitID.

This may not be necessary in BA as we have a TRANSPORTS group category already that probably should get priority.

REVENGE wrote:Also, Nio and I were discussing making an engine change whereby you can set the priority target of units to a specific unit or unitID.

I don't understand...

CarRepairer wrote:

REVENGE wrote:Also, Nio and I were discussing making an engine change whereby you can set the priority target of units to a specific unit or unitID.

I don't understand...

Per unit vs. unit target priority, presumably settable with lua.

it is not just fighters. Many other units have the same problem.
Yesterday many of the karganeths did not attack the commander, which I ordered them to do, but instead started to attack other units, after they FINALLY started attacking the commander (after 5 seconds or so.. after their prevous target got destroyed). Feel happy! youre not alone