search

ImpactDevelopment / ImpactIssues

Please use this repo to report bugs and request features
https://impactclient.net/
220 stars 36 forks source link

Improve how .set finds nested options #1269

Open LeafHacker opened 5 years ago

LeafHacker commented 5 years ago

Is your feature request related to a problem? Please describe. Some options share name/ID with other options, which currently means only one can be targeted. I've also heard reports that mode sub-options can't be targeted.

Describe the solution you'd like Perhaps .set could use a nesting syntax along the lines of .set mod > sub > subsub > option value?

Describe alternatives you've considered Alternatively ensure IDs are unique per-module, find a way to let users easily discover IDs and maybe stop using names (maybe checking I'd before name is fine too).

Additional context Add any other context or screenshots about the feature request here.

Cerbiac commented 5 years ago

While sub-options can't be targeted, modes themselves can't be changed either. I mentioned it in another comment I made, but forgot to get around to making the issue.

(Modes are not treated as values and can't be changed with .set, so I'll make a suggestion on that.)

Vort commented 4 years ago

It would be nice to have ability of controlling flight speed with hotkeys.

5HT2 commented 4 years ago

You can use macros for that @Vort

Vort commented 4 years ago

@dominikaaaa I can't, since flight module gives no access to flight speed. As @LeafHacker said, it can be possible if .set command will support format like: .set flight > vanilla > speed 3.99.

impsp1 impsp2

It can be that it is already implemented in Impact, but I don't see how it is possible to find correct format for .set command.

5HT2 commented 4 years ago

Oh I see what you mean. Yep, that makes sense.