Connection ErrorBad RequestThis page went staleSession ExpiredSign in requiredForbiddenNot FoundToo Many RequestsServer ErrorBad GatewayService UnavailableGateway TimeoutHTTP Version Not Supported
Session Expired
Your session has expired. Please log in to continue.
Sign in required
You need an account to do that. Sign in or create one — it only takes a minute.
This page went stale
Your security token was rejected, usually because the page sat open too long or you signed in elsewhere. Nothing was saved. Reload the page and try again.
Request Failed
We encountered an issue while processing your request.
Please check your internet connection and try again.
As I mentioned above, the buttons don't even appear in the save/load menu, which is great. vova2112
However, there's nothing you can do about [quickload 'F8'] and [quicksave 'F5'] – these commands are hardcoded into the executable. Of course, you could break it by changing the values in a hex editor, for example, to quicklo1d and quicksa1e. But that's not a great solution.
Yes, the quickload and quicksave IDs are created in the executable. However, the bindings to f8 and f5 are written in the input_a2.cfg file, which is located in the documents folder. Yesterday, I simply commented out the lines: bind quicksave 'F5' and
bind quickload 'F8'. This helped, but I'll have to explain to users where to put this file or (God forbid) create an installer. I like your idea of changing the bits in the executable, as this map already uses a custom executable.
Added 1 minute ago }{0TT@6bI4
You could try using a script command to write to the console unbind COMMAND_NAME or bind COMMAND_NAME "MOUSE_B5"
I tried it. For some unknown reason, it only works in about 10% of cases.
PS. It worked using unbind quicksave unbind quickload