Robert Müller

I'd also consider `UI` a special case instead of using `Ui`.

> do we want to reuse/share command names for potentially different use cases in these 3 systems: chat, local console, remote console We already do. The command `echo` on the...

Possibly curl shuts down first (`curl_easy_cleanup` and `curl_global_cleanup`) which frees `CHttpRequest::m_pHeaders`, so the `CHttpRequest` destructor causes a double-free with its `curl_slist_free_all((curl_slist *)m_pHeaders)`.

The way I understand/expect it, `curl_global_cleanup(pHandle)` will free some curl internal structure for the given handle and `curl_global_cleanup` will free all the curl internal structures, invalidating all handles. Hence, calling...

Showing `Password incorrect` is the default behavior when connecting to any server that has a password, that's not a bug. Pressing the `Try again` button currently uses `ui_server_address` to connect....

> But maybe we should also extend redirect messages to include a password May need a separate discussion so please open another issue for that.

Seems like a duplicate of #2875, although allowing text or other input hasn't been explicity proposed in that issue.

The proposal in #2875 is about "interactive" help, so I think text inputs could also be included in that issue instead of tracking it separately.

I'll consider this duplicate of #2875. We should discuss on that issue which use cases we want to support. Supporting interactive text input definitely seems useful.

@def- Can you also share the map and RTP file? Not sure if directly related, but when reducing `NUM_SAMPLES` to `100` (so loading more sounds will fail) and loading a...