Poll: Remove Return Fire and Roam

[Saktoth]

#564

[Google Frog]

If we could replace return fire with fire when decloaked.

Roam is only used to tell your units that it's ok for them to run off and die (manoeuvre for that matter too). I want some of my units to run off and die though, for example fighters.

[Google Frog]

It's good to have the option. Make a 'simplified unit states' widget.

[Saktoth]

Return fire is useless here, a widget that auto fires when decloaked is far better, yes.

Use patrol for run off and die, having a toggle instead of cycling through states will lead to far fewer mistakes.

[licho]

Wire roam to autoskirm and autoswarm?

[maackey]

Winner: No (53%)

[Saktoth]

Id like to hear what you actually think these could possibly be used for.

Dont say cloak, cloak is much better wired to hold fire when cloaked/fire at will when uncloaked, and to be aware of its state, rather than 'oh noes i be getting shot'.

[Google Frog]

Well my auto-moat widget generates a moat around DDMs, Stardusts and Warriors when those units are set to return fire. Without return fire I'd have to lua a button to do it which is too much effort for a silly widget.

Wire roam to autoskirm and autoswarm?

That is also a good idea. Autoskirm and Autoswarm can potentially make units wander all over the map.

[CarRepairer]

What is this moat widget you speak of? Does it make large moats so glaives can't get close enough to swarm?

[Google Frog]

Replying to CarRepairer:

What is this moat widget you speak of? Does it make large moats so glaives can't get close enough to swarm?

Eventually it would but making a moat so that vehicles can't cross is much faster.

[Saktoth]

We shouldnt have people keep accidentally setting their units the wrong setting (i do it all the time, dont know about you) just so you can use this custom, rarely used function to activate a widget (in fact, that you used it for that is an example of how useless it is).

Googles moat widget makes the unit fire at the ground and dig a hole for itself.

[CarRepairer]

Replying to Saktoth:

We shouldnt have people keep accidentally setting their units the wrong setting (i do it all the time, dont know about you) just so you can use this custom, rarely used function to activate a widget (in fact, that you used it for that is an example of how useless it is).

I agree and I think roam is 100% useless, but return fire has its uses. But I do hate the triple state settings.

What I would love is for as many as possible two-state settings, and change the behavior so left-clicking the button turns stuff on and right-clicking the button turns stuff off. This could apply to holdfire/fireatwill, off/on, holdpos/maneuver, repeaton/off, and whatever else I can't think of.

Googles moat widget makes the unit fire at the ground and dig a hole for itself.

lol.

[Google Frog]

Googles moat widget makes the unit fire at the ground and dig a hole for itself.

It makes moats and digs holes.

I don't think we should remove it as there are some uses. Make a widget that removes it. It might be a good idea to make a gadget that allows people to reverse toggle the states with right click.

[Google Frog]

Removes 'Return Fire' and 'Roam' states.

[Google Frog]

Here's a widget that makes toggling between 2 states easy.

[Google Frog]

Adds reverse toggle for fire and movestates

[Google Frog]

Here's a reverse toggle state one. Now that there are widgets that can do everything anyone would ever want to do with fire/movestates you can go off and set up your own interfaces (don't move/shoot widgets complete everything you'd want to ever do).

Unless of course this ticket wants to turn into a default interface ticket. In that case I don't think my quick method of removing states is noob friendly enough.