Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Command suggestions: getlastsegmenttime getlastsegmentbesttime

Open
#22 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
api

Research direction

Start by locating the command handling for the listed segment and comparison commands in LiveSplit.Server. Review how existing commands obtain split and segment times, then verify that each proposed command returns the requested value for the current comparison or named COMPARISON. No specific files or tests are mentioned in the issue.

Written by the indexing model from the issue text.

Description

Unless I'm wrong, I don't think it's possible to derive if the last segment was a gold split or not from the current implemented commands.

I would like to propose the following:

getlastsegmenttime: return only the time of the last segment
getlastsegmentbesttime: return the gold time of the last segment (this wouldn't be updated as of the current split, IE if a user just got a gold split -- it would return the saved gold split from before this run)

getlastsegmenttime: return the duration of the last segment
getcomparisonsegmenttime: return the duration of the current segment for the current comparison
getcomparisonsegmenttime COMPARISON: return the duration of the current segment for COMPARISON
getcomparisonsplittime COMPARISON: return the current split time for COMPARISON

I'd do this myself, the code doesn't look too difficult, but I'm running linux and I really don't have any experience building C# stuff :(

Dominant language
C#
Stars
52
Forks
33
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LiveSplit/LiveSplit.Server

All issues in LiveSplit/LiveSplit.Server

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.