Skip to content

Conversation

rhit-daughewd
Copy link
Member

No description provided.

@rhit-daughewd
Copy link
Member Author

Current Implementation uses the previous fuzzy search inputs and returns all outputs uncapped. The outputs are sorted by score but may be excessive for broad searches, more restrictive range may be necessary depending on the number of commands in full release.

@Borketh
Copy link
Member

Borketh commented Oct 7, 2025

Can I get an example of the new behaviour?

@rhit-daughewd
Copy link
Member Author

Searching commands for "file" get the following results in the test server.

Here's what I found:
?profiles
?logfilter
?newprofile
?unifiedgrid
?vanillaprofile
These were found by fuzzy matching. If it's not fuzzy enough, complain to Borketh#3347.

This is a reasonable output in test but depending on the number of responses in the full release it may need to be capped. This is especially relevant for simple searches, for example searching "f" results in this on the test server.

Here's what I found:
?ff
?fin
?fun
?sf+
?ewaf
?fred
?felix
?feyko
?config
?sftools
?sod-off
?manifest
?profiles
?debuginfo
?logfilter
?offscreen
?debug-info
?epicverify
?newprofile
?oldconfigs
?verifyepic
?factorygame
?factroygame
?steamverify
?unifiedgrid
?verifysteam
?bufferoverflow
?factorygamelog
?vanillaprofile
?factorygame.log
?perfect-circles
These were found by fuzzy matching. If it's not fuzzy enough, complain to Borketh#3347.

@Borketh
Copy link
Member

Borketh commented Oct 8, 2025

I think that could be partly mitigated by refusing to search for single characters. There are plenty of dual character commands in practice, but no singles.

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

Labels

None yet

Projects

Status: 🆕 New

Development

Successfully merging this pull request may close these issues.

>search matching algorithm does not find substrings

2 participants