LiveSplit / LiveSplit/livesplit-core
Unify the Update Triggers
Open
enhancement
feature
needs further discussion
- Dominant language
- Rust
- Stars
- 227
- Forks
- 81
- Avg merge
- 22h 45m
- Merged PRs (30d)
- 3
Description
All the components should have customizable Update Triggers. At the same time we should also look into unifying the behavior across the different algorithms. Some start at the best segment, some start when losing time and so on.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Compare the update-trigger behavior across the different components and algorithms, then define how customizable triggers should work. Done means the components expose unified, customizable update triggers and their algorithm behavior is consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100