The BepInEx console will not appear when launching like it does for other games on Thunderstore (you can turn it back on in your BepInEx.cfg file). If your PEAK crashes on startup, add -dx12 to your launch parameters.
Split Stats Speedrunning Timer
Track your runs and additional stats with this speedrunning timer automatically!
| Last updated | 2 weeks ago |
| Total downloads | 1312 |
| Total rating | 2 |
| Categories | Mods Tools Misc Quality Of Life Client Side |
| Dependency string | catcraze777-Split_Stats_Speedrunning_Timer-1.1.1 |
| Dependants | 0 other packages depend on this package |
This mod requires the following mods to function
BepInEx-BepInExPack_PEAK
BepInEx pack for PEAK. Preconfigured and ready to use.
Preferred version: 5.4.2403README
peakSplitStats
A speedrunning timer for Peak, with many built in features! Designed for casual speedrunners as a client-side only mod to help visualize your current pace and keep track of past times automatically. Also includes a base MonoBehavior for other modders that would like to display their own info within this mod!
Features
- Very Customizable
- Automatic Splits
- Saves Runtimes to use for Green/Red/Gold splits.
- Categorizes runs to only display relevant records.
- Edited End Screen to Display the run's final pace.
- Extra info for current height and distance from next campfire/peak.
- Option to edit the current ascent text to display run category info.
- Supports the Terrain Randomiser for run categorization.
- Generalized components for other modders looking to add custom info to display.
Screenshots
Modder Info
If you'd like to add a custom component, please look into the BaseUIComponent abstract class and the InfoComponent class for documentation and how to implement your own custom UI element within SplitStats. An example plugin that adds a simple InfoComponent is provided in the ExampleUIAddon directory of this repository. Once you've properly made your component, add it into SplitStats using SplitStats.AddCustomStat(InfoComponentTemplate addonTemplate) or SplitStats.AddCustomComponent(BaseUIComponent newComponent), depending on how you chose to implement your UI element.
The results displayed from the example addon:
