Store client time disposition
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.3k
- Forks
- 960
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 2
Description
While the proxy won't be able to send signed messages, the proxy can still send unsigned command/chat packets, which will, right now, be sent using the proxies current time. Many PC users do not have their system clocks setup to synchronize properly, thus causing clock drifting to be a somewhat common issue, potentially in the region of minutes, if we want to be able to send messages, we need to ensure that we reasonably track the clients time in order to use that to offset from our own clock for various operations
Contributor 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.
Research direction
Start by tracing how the proxy handles unsigned command and chat packets and where it currently uses the proxy's clock. Done means the client's time is reasonably tracked and its offset is used for the relevant operations, including unsigned messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100