MegaMek / megamek

MegaMek is a networked Java clone of BattleTech, a turn-based sci-fi boardgame for 2+ players. Fight using giant robots, tanks, and/or infantry on a hex-based map.
http://www.megamek.org
GNU General Public License v2.0
296 stars 282 forks source link

RFE: Client Setting for Sensor Defaults #5868

Open Saklad5 opened 2 months ago

Saklad5 commented 2 months ago

Almost all units come with a set of sensors to choose from, with different strengths and weaknesses. Right now, MegaMek always defaults to using a unit's active probe if installed, and radar if not.

Radar is generally a poor choice on military units, especially next to options like magscan and infrared. As a result, I often start each fight tediously tweaking the sensor setting of each unit as I deploy them.

Rather than simply tweaking the default order to match my own preferences, I propose adding a client setting consisting of an ordered list of all sensors known to MegaMek. Each unit can then default to the first sensor it has on the list when deployed.

SimonLandmine commented 2 weeks ago

As an additional option, in some circumstances, it might be useful to be able to set the 'sensor in use' in the Unit Configuration window in the Lobby. However, having a Client Setting (as requested above, in a similar choice to weapons display order) for 'Preferred Sensors' would potentially be more useful, especially with larger forces, avoiding having to configure each in turn.

Saklad5 commented 2 weeks ago

The active sensors may already be adjusted in “Round Zero”, as you deploy units.

SimonLandmine commented 2 weeks ago

Yes, but configuring in the lobby would raise the potential for pre-saving sensor selection as a MUL along with other configuration. Also, I was noting one of the requests from the Discord. :-)

Saklad5 commented 2 weeks ago

Ah, that does make sense.

repligator commented 1 week ago

See also https://github.com/MegaMek/mekhq/issues/4044

Saklad5 commented 1 week ago

See also MegaMek/mekhq#4044

While similar, this issue isn't about equipment state. In MegaMek, sensors are treated separately from any specific component.

SuperStucco commented 1 week ago

Yes, but configuring in the lobby would raise the potential for pre-saving sensor selection as a MUL along with other configuration. Also, I was noting one of the requests from the Discord. :-)

A more general method of associating sensor mode with chassis and/or model also has applications for Princess. If the player thinks a certain sensor mode is good for a unit, then 'good for the goose, good for the gander'.

Saklad5 commented 1 week ago

To some extent, yes.

I'm not proposing associations like that, though: just an ordered list of sensors, where the first one present is picked.

There are some nuances that cannot be captured by that. For instance, active probes are basically useless on the space map next to active radar, but better for spotting ground targets when flying low enough. Magscan is almost useless in urban environments, while infrared is of limited utility in hilly areas. And, of course, active probes are dead weight if they are being jammed.

Princess would be better off with that kind of logic, ultimately. Simply sticking with player-specified defaults might be a small improvement, but not a true substitute.