** In the trade routes menu, when doing "search" such as for "canned food" or other, the game hot keys are still active if typing quickly. For instance, typing _quickly_ takes me to the "diplomacy" screen or other such locations. I have to type _slowly_ in the "search" field of the trade routes for the hot keys not to activate.
** This problem is *new* with the latest game update and high-life DLC.
Hey @rastercubed and @SirHarryPierce, thanks for getting in touch and bringing this to our attention as well as apologies about the delayed response from our team.
Based on the comments made, I understand that issue doesn't occur each and every time, is that correct? If that is the case indeed, did you possibly identify any particular course of actions that will most likely lead to it?
Additionally, if any of you manage to capture this on video footage, it would be very good if you could provide us with it as we would then be able to forward it over to our development team for further review.
Let us know and we will take it from there!
Hey @sirharrypierce,
Thank you for the video, this is very helpful and clear.
Can I just check, in your experience does this happen every time that you type fast or is it completely random?
Many thanks,
Thanks for the reply sirharrypierce, I have now sent this video and information for our team to review to see if they can reproduce it also, with sticky keys enabled.
Thanks again everyone for bringing this to our attention.
Thanks for chiming in, @basti-cool! I appreciate the provided link.
I've added that this is still occurring to the report made, and this thread will be updated with more information once received. In the meantime, if you'd like to provide a clip showing the issue, I'd be glad to notate that as well!
Hey @sirharrypierce,
Thank you for taking your time out to share with us a video of this happening.
I have now shared this with the team to help the investigation.
In the mean time if we can help with anything else just let us know as we are happy to help.
Hello again Harry, thanks for letting us know this issue is still present after the last update 13.2.
I will forward this to the team and we will get back to you and everyone else in this thread, should our QA team need any particular additional info.
@sirharrypierce Apologies for the annoyance caused by this. Once there is an update on this issue we will reach back out.
Thank you.
Hey there guys!
There are hopes to resolve this issue in a future update, but the exact date of this hasn't yet been announced.
We will continue to keep you updated as and when more details are made available.
Thanks for your continued patience while this is looked into!
devtrackers.gg