A prototype Desktop version of LiveSplit One, using the Druid framework and the multiplatform livesplit-core library.
The Web Version is available at one.livesplit.org.
Download the latest release for your operating system and archictecture here: https://github.com/AlexKnauth/livesplit-one-druid/releases/latest
When you run LiveSplit One Druid, it needs to have permission to read memory of other processes.
- On Mac, that might require running it under
sudo. - On Linux, give it permission with one of:
- setting the capabilities to include
CAP_SYS_PTRACE, which can be done withsudo setcap CAP_SYS_PTRACE=+eip LiveSplitOneor some variation of that - setting
/proc/sys/kernel/yama/ptrace_scopeto 0, which can be done withecho "0"|sudo tee /proc/sys/kernel/yama/ptrace_scope - running it under
sudo
- setting the capabilities to include
- On Windows, it should just work. Windows allows memory reading by default.
In order to build LiveSplit One you need the Rust Compiler. You can then build and run the project with:
cargo runIn order to build and run a release build, use the following command:
cargo run --releaseThe config file and log file are located in the local data directory from data_local_dir:
- Windows:
C:\Users\<name>\AppData\Local\LiveSplit\LiveSplit One\data\config.yml - Mac:
/Users/<name>/Library/Application Support/org.LiveSplit.LiveSplit-One/config.yml - Linux:
/home/<name>/.local/share/livesplitone/config.ymlor/root/.local/share/livesplitone/config.ymlif running assudo
If you want a log file, edit the log section of the config file to say
log:
enable: true
level: INFO
clear: trueOnce you run it with an autosplitter open, a log.txt file should appear in the same directory as the config.