Autocomplete caching should take into account values of other options

[freya022]

Current behavior

Currently, the client caches autocomplete results with what the user typed in the focused option

Desired behavior

The client should cache autocomplete results based on what the user typed in the focused option, as well as other options.

Why this is needed

I've seen the client give back invalid results after changing one of the previously set values.

Let's take an example

1. You are trying to find a function in a class
2. You start typing your command and put the class name, you then put the function name (let's say, "set")
3. The bot gives you suggestions and you realise you were searching in the wrong class
4. You then go back to the previous option (the class name), change it, and then go back to the function name option
5. You type "set" again
6. The bot still gave the exact same functions as the class you wrongfully chose before

This would be solved if the client cached autocomplete choices relative to the entire list of inputs

A video is worth more than a thousand words:

Discord_jEWgHWEnE3.mp4

[kingmigdor]

I think autocomplete restults shouldn't be cached anyways. I'm having problems with all use-cases I currently have, and even if autocomplete caching is needed, the bot can cache it itself.

[almostSouji]

I'm curious: what usecase do you have where autocomplete results will be invalid within 30 seconds?

I wanted to implement a dynamically searchable inventory and supply the number of items left in the result and found out that those are cached and will not decrement after item use/sale.

(to be clear: for me, it's not even required to depend on other options, but just the name being cached)

[Tobias-Pe]

Are there any updates to this problem for our use-case ?

I'm facing the same issue :/

Any one maybe even found a workaround ? :)

[zfbx]

I am curious how many people run into the case I did where I assumed it caches for a set amount of time, but it actually only caches for as long as the / command is up and once you delete all the text or send the command that cache clear again for the next command. when I was testing and restarting the bot I would just keep backspacing in the autocomplete and was missing results for that reason. The caching built in is actually quite reasonable for the event someone types and backspaces it doesn't re-search

[iakashpatel]

We are having same issue as well for our bot.
I hope discord Team fixes it asap.

[MaxAPCS]

+1 Really want this feature, my bot's autocomplete changes when other options change