Open
Conversation
res2k
force-pushed
the
rerelease-game
branch
4 times, most recently
from
fe3cada to
f02a7f1
Compare
res2k
force-pushed
the
rerelease-game
branch
3 times, most recently
from
9ce9b20 to
0d06189
Compare
res2k
force-pushed
the
rerelease-game
branch
from
6639ecd to
e71bbb9
Compare
res2k
force-pushed
the
rerelease-game
branch
from
1dce726 to
a738ebd
Compare
res2k
force-pushed
the
rerelease-game
branch
3 times, most recently
from
7a78380 to
7a65bd2
Compare
res2k
force-pushed
the
rerelease-game
branch
3 times, most recently
from
5b2ff50 to
75c564d
Compare
res2k
force-pushed
the
rerelease-game
branch
5 times, most recently
from
170796e to
26ba3e6
Compare
res2k
force-pushed
the
rerelease-game
branch
5 times, most recently
from
5685889 to
99b5dd8
Compare
res2k
force-pushed
the
rerelease-game
branch
from
5ee7bef to
f5d9b1c
Compare
res2k
force-pushed
the
rerelease-game
branch
2 times, most recently
from
4efd459 to
e19b9c8
Compare
* "No files" is a valid case for the dedicated server, so only print a developer warning * Don't crash if setting up "builtin pak" fails
(cherry picked from commit 5deaa37)
(cherry picked from commit b552ba0)
(cherry picked from commit f29cfd8)
(cherry picked from commit 9525565)
(cherry picked from commit cc43a2e)
(cherry picked from commit c6aea47)
(cherry picked from commit b25a0b1)
Closes #393. (cherry picked from commit 2c43c78)
(cherry picked from commit 2b44b3b)
(cherry picked from commit 365fde0)
(cherry picked from commit 6b75e8e)
* Update to cross-platform-actions v0.29.0 * Update FreeBSD to 14.3 * Fix FreeBSD package name
* server: handle q2proto_server_read errors properly when q2proto was added in commit 0bfa9ac, the error handling for q2proto_server_read() was incomplete. the original MSG_ReadByte() code properly handled unknown command bytes by dropping the client but the q2proto version only checks for Q2P_ERR_NO_MORE_INPUT and ignores all other errors like Q2P_ERR_BAD_COMMAND! this fix properly handles all q2proto errors by dropping the client with a descriptive error message
* handle configstrings differently depending on protocol and api * handle baseconfigstrings (for demos)
We don't always write demos with the same protocol as used for the communication with the server - notably, when connected to a q2repro server running a vanilla game, we communicate with the repro protocol, but record vanilla demos -, and dumping raw packets in that case produces demos that don't play. Luckily, q2proto (now) provides the necessary abstractions to write any protocol we want into the demo.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.