1import{C as o,M as i}from"./CodingEntry-39b86908.js";import{d as n,o as r,i as s,w as a,a as l,u as c,b as e,e as t}from"./index-9578dcdb.js";const p="/assets/livesplitanalyzer-35bcc8a6.png",d=e("p",null,[t(" I recently picked up speedrunning, and realized that there was a lack of tools to analyze performance and edit splitfiles created by "),e("a",{href:"https://livesplit.org/",target:"_blanck"},"LiveSplit"),t(" (or even fix them in the most extreme case of incoherent data), so I set up to make my own tool for this purpose. This was (still is actually) a really fun project to work on, which got a lot of positive feedback in my speedrunning community. I even got some help developping it, which was also a fun side of the project since I don't often have the occasion to do code reviews. From a technical perspective the website is made with Nuxt 2 and Typescript. The project is developped on "),e("a",{href:"https://github.com/Webcretaire/LiveSplitAnalyzer",target:"_blanck"},"GitHub"),t(" and is hosted "),e("a",{href:"https://webcretaire.github.io/LiveSplitAnalyzer",target:"_blanck"},"here")],-1),y=n({__name:"CodingModalLiveSplitAnalyzer",setup(h){return(f,m)=>(r(),s(i,{"hide-footer":"",title:"LiveSplitAnalyzer : tool to analyze speedrunning performance"},{default:a(()=>[l(o,{image:c(p)},{default:a(()=>[d]),_:1},8,["image"])]),_:1}))}});export{y as default};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.