Skip to content

Dgun prioritisation (for coms)#5764

Open
Stiofan-K wants to merge 1 commit into
ZeroK-RTS:masterfrom
Stiofan-K:com-dgun-prioritisation
Open

Dgun prioritisation (for coms)#5764
Stiofan-K wants to merge 1 commit into
ZeroK-RTS:masterfrom
Stiofan-K:com-dgun-prioritisation

Conversation

@Stiofan-K

Copy link
Copy Markdown
Contributor

A workaround attempt to avoid forcefire/settarget from conflicting with dgun commands.

Does some manual shenanigans to gurantee that a dgun will (eventually) be prioritised over a set target/force fire command.
@Stiofan-K

Stiofan-K commented Jun 27, 2026

Copy link
Copy Markdown
Contributor Author

Doesnt feel like a clean fix, though I used it for Dante too. PR is more to get the ball rolling and some insights.

From observation, it seems that it's set target and forcefire that conflict with dgun orders, while a commander given a stop command and as such has no target set, prioritises it's dgun without need for workaround even if it shoots other things inbetween.

I've tried to unset the target through Spring.SetUnitTarget and the Unitrules param "target_type" as the unit_target_on_the_move gadget does it, but that didnt seem to do the same thing as a stop command, with some linger data that I assume causes the resulting jittering/aim conflict.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant