LiveSplit / LiveSplit/LiveSplit.Server
Cannot retrieve gametime.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 52
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
'getcurrenttime' is the only command that will directly retrieve livesplit's timer data, and it always retrieves via TimingMethod.RealTime. I've initialized game time. I've setcomparison to gametime. Doesn't matter. When I ask for 'getcurrenttime,' I always get back the RealTime.
Python:
```
import time
import socket
livesplit = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
livesplit.connect(("localhost", 16834))
livesplit.send("initgametime\r\n".encode())
livesplit.send("setcomparison gametime\r\n".encode())
livesplit.send("starttimer\r\n".encode())
livesplit.send("pausegametime\r\n".encode())
time.sleep(3)
livesplit.send("getcurrenttime\r\n".encode())
ls_time = livesplit.recv(1024).decode()[:-2]
print(ls_time)
```
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the behavior with the provided Python socket script, focusing on the initgametime, setcomparison gametime, and getcurrenttime commands. Trace the server entry point that handles getcurrenttime and its use of TimingMethod.RealTime; done means the command returns game time after the shown setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100