[SUGGESTION] A few simple tweaks

They refer to various categories, so no particular name of topic:

-In server browser, how about sorting by amount of players by default?
-In cvar list, how about making search work as "contains" filter rather than "starts with"? For example, one of first settings are "accuracy_color". If I type "color", those do not show in results, because name does not start with "color" - I have to type "accuracy". It would come in handy for further cvars, because we wouldn't have to guess, what a name starts with, instead any part of name would do.
-"Instant action", if selects DM or TDM, should make target score dependent on set amount of bots. Now you can get 1on1 DM up to 30 or even 50 if TDM, which IMO is too much. My idea would be 10*number_of_bots, up to 50 or 60.
-In LMS mode, how about showing amount of lives left in upper right corner, where frags would be shown in DM? Currently, there are only zeros next to names.

- no ... server list should be sorted by ping ... so new people will try good servers for them first (note this is me coming from the US where there are very few low ping servers)

- yes .. yes .. yes .. YES

- sounds reasonable

- wait... theres a frag counter in the corner? ... how long has that been there? (yes thats a good idea too)

If you want to search for things that contain 'color', all you need to do is enter *color* (note the asterisks).

Or if you want to search for things that end with 'color': *color

If you want to search for things that contain 'color', all you need to do is enter *color* (note the asterisks).

Or if you want to search for things that end with 'color': *color

Bump old thread, because it doesn't work for me, at least in current autobuild. Ticket time? Though I guess "contains" filter would still be superior option, because it's consistent with filtering for server browser.

If you want to search for things that contain 'color', all you need to do is enter *color* (note the asterisks).

Or if you want to search for things that end with 'color': *color

Bump old thread, because it doesn't work for me, at least in current autobuild. Ticket time? Though I guess "contains" filter would still be superior option, because it's consistent with filtering for server browser.

*color* works perfectly fine for me in git.

"Contains" filter is problematic, because then there is no way to reliably list cvars that start with a certain prefix. It's restrictive compared to what we have now, which is by the way consistant with the cvarlist command (match beginning of cvar, or whole cvar if there are wildcards).

Nevermind, I keep on forgetting about ending one.

How about two checkboxes for automatic adding asterisk in the beginning or and end? Sth like:

Code:

if(checkbox_add_asterix_beginning.checked)
   filter = "*" + filter;
if(checkbox_add_asterix_end.checked)
   filter += "*";
//and then actual filtering

That way you kill two birds with one stone: you don't have to worry about forgetting typing them and nothing would get broken, as if you leave them unchecked, you get current behavior.

Or maybe, just maybe, push that button marked "*" on your keyboard.

I agree that it is not clear at first how the patterns are matched. The problem is to build on top of the cvarlist matching. With buf_cvarlist, f there is no asterisk in pattern, then the list is matched against "pattern*". If there is one, it is matched against "pattern".

What you want to do is to use "*pattern*" when "Contains" is checked, while "contains" unchecked uses "pattern". Or maybe "pattern*". I don't think anyone would want to do exact matching, and it seems exact matching can't be done with buf_cvarlist anyway.

Feel free to give this a try if you want to learn some QC, it's a fun little project that lets you dig into the amazing menu code. It's in qcsrc/menu/xonotic/dialog_settings_misc_cvars.c

OK, thanks, I might sometime later.