Store partially compressed game inputs for reconcatenation
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
Research direction
Start by tracing where the server stores player inputs and handles a spectator request, then inspect how inputs are concatenated and compressed. Keep the compressed portion available for later spectator requests and verify that appending newly compressed inputs produces a valid replay without recompressing prior inputs.
Written by the indexing model from the issue text.
Description
Currently the server holds the player inputs in a table.
When a player requests spectate, the server concatenates all inputs so far, compresses them and puts them in a partial replay that is sent to the new spectator.
The result of the concatenation is discarded.
This discard is unnecessary with the way compression is used.
Assume the following inputs when the spectator requests first:
AAAAggggAABBFE
This compresses to A4g4A2B2F1E1
Later another spectator joins and the full inputs are now:
AAAAggggAABBFEEEABBBBBFlkkkkggggggggiiiiigggggiiiiigggggiiiiiiigg
the only new inputs are
EEABBBBBFlkkkkggggggggiiiiigggggiiiiigggggiiiiiiigg and would compress to E2A1B5F1I1k4g8i5g5i7g2 on its own
The concatenation of two sections of inputs concatenate to the valid compressed string
A4g4A2B2F1E1E2A1B5F1I1k4g8i5g5i7g2
Every single concatenation for a new spectator can be expected to only add 2-3 character worth of string but avoids redoing previous work.
This is probably not really important with the current state of things but it makes things slightly easier for the server when people join as spectators on long matches.
- Dominant language
- Lua
- Stars
- 30
- Forks
- 20
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 17
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from panel-attack/panel-game
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
panel-attack/panel-game#822 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
panel-attack/panel-game#779 ·
Maintainers usually reply within 1 day
-
bug Client-side priority: 0 - high
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
panel-attack/panel-game#776 ·
Maintainers usually reply within 1 day
-
enhancement priority: 1 - middle
Difficulty 4/5 3-5 days Newbie friendliness 48/100
panel-attack/panel-game#821 ·
Maintainers usually reply within 1 day
-
Animation scenes draw every part separately, costing hundreds of draw calls a framePossibly taken @JamesVanBoxtel claimed this 4 days ago. OpenClient-side enhancement graphics
panel-attack/panel-game#814 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in panel-attack/panel-game
Similar issues
-
slice weekend
Difficulty 2/5 1-3 hours Newbie friendliness 71/100
Life-Framework/Life-Framework#3212 ·
Maintainers usually reply within 1 day
-
bug discord guide:01b-riverglades locale:enUS triage v4.1.1
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
petertriho/nvim-scrollbar#127 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100