| 1 | high priority |
1 | high priority |
| 2 | |
2 | |
|
|
3 | - no hardcoding of face names, need to use fx(!). |
| 3 | - interpret both json and non-json messages for chatbox |
4 | - interpret both json and non-json messages for chatbox |
| 4 | - interpret pseudo-html and pod sequences in messages (maybe first fix the overall |
5 | - interpret pseudo-html and pod sequences in messages (maybe first fix the overall |
| 5 | protocol to not mix antique and modern styles?) |
6 | protocol to not mix antique and modern styles?) |
| 6 | - auto-switch tabs when server says so (flag value 32 or so). |
7 | - auto-switch tabs when server says so (flag value 32 or so). |
| 7 | - proper query/reply - autologin is fine, but the username or password |
8 | - proper query/reply - autologin is fine, but the username or password |
| … | |
… | |
| 11 | What is your password\? |
12 | What is your password\? |
| 12 | Please type your password again\. |
13 | Please type your password again\. |
| 13 | What is your name\? |
14 | What is your name\? |
| 14 | (alternatively, support a better api for creating characters and loging in in general, |
15 | (alternatively, support a better api for creating characters and loging in in general, |
| 15 | without cleartext password). |
16 | without cleartext password). |
|
|
17 | also, proper flags support (CS_QUERY_YESNO, CS_QUERY_SINGLECHAR, CS_QUERY_HIDEINPUT). |
| 16 | - command input needs major work: |
18 | - command input needs major work: |
| 17 | - it probably should trigger on all letters |
19 | - it probably should trigger on all letters |
| 18 | - it would need a mechanism similar to the existing client for abbreviations |
20 | - it would need a mechanism similar to the existing client for abbreviations |
| 19 | (so c becomes chat, rsft ready_skill find traps etc). |
21 | (so c becomes chat, rsft ready_skill find traps etc). |
| 20 | |
22 | |
