New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce message truncation #1279
Labels
Milestone
Comments
flambard-took
added a commit
that referenced
this issue
May 18, 2019
Address #1279 ensure maximum available space is used in the inven/equip prompts and subwindows.
flambard-took
added a commit
that referenced
this issue
May 18, 2019
This breaks protocol, but a backward-compatibility layer is included, so previous versions of the client would still work. This changeset add a new `client_version_atleast` function, to check minimal client version, and `client_version_ok` has been changed to utilize it.
flambard-took
added a commit
that referenced
this issue
May 18, 2019
Long messages that do not fit the screen can now be scrolled by pressing the SPACE BAR key.
flambard-took
added a commit
that referenced
this issue
May 18, 2019
in Message and Chat sub-windows.
flambard-took
added a commit
that referenced
this issue
May 18, 2019
flambard-took
added a commit
that referenced
this issue
May 18, 2019
flambard-took
added a commit
that referenced
this issue
May 22, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We always truncate our log messages at 80 chars, which often leads to loss of information.
It's interesting to note, that Ctrl+P/message recall screen on the client already supports messages of arbitrary length, we just never get those through.
Sadly, the s2c PKT_MESSAGE packet defines messages as '%s' (limited to 80 chars), not '%S' (limited to MSG_LEN), so we'll need to break protocol (subtly).
Other points of interest:
The text was updated successfully, but these errors were encountered: