GermanyOlder runs may haven't shown the chapter complete screen because the rule that the chapter complete screen has to be shown was just added on April 16th, 2019, according to #announcements on the discord.
There is already an existing leaderboard for pico8-celeste: https://www.speedrun.com/celestep8
Yeah, but currently only the rules for Any% got changed regarding the timing start. And maybe the next time there should be a seperate forum post by someone when the rules get changed, I don't think everyone checks the rules everytime before they doing runs :D
When did the starting point for Any% changed? Wasn't it like the starting points in the other categories? :0
I did a run of it just for fun before without practicing before :D But it is the only run I did of it so far. https://www.youtube.com/playlist?list=PLaSZq93-qwKFP0WdZuMHxwWlFXLGr36Oc
A new version of the Auto Splitter is now available in LiveSplit.
You can read more about the update here: https://github.com/Starcrunsher/TitanSoulsAutoSplitter/blob/master/README.md
The Auto Splitter can directly be used via the "Edit Splits" menu of LiveSplit or you can download the script and use it in your LiveSplit layout. The direct link to the autosplitter file is https://raw.githubusercontent.com/Starcrunsher/TitanSoulsAutoSplitter/master/TitanSoulsAutoSplitter.asl
I came up with that idea because I wanted to run a category which contains all levels of the game, but with real times of 6h+ All Teensies and 100% are too long for me at the moment.
To run NG+ All Levels you would start with a 100% save file (like the one linked in the Resources page), and complete all levels in any given order without additional restrictions. So I would suggest the timing starts after the loading screen of the first level you enter, and the timing ends at the end of the last level you will complete (depending on your oder of the level after the last hit on a boss, entering the exit door on a normal level, reaching the end of a invaded level or music level).
I did two runs today, and the the load removal was around 2-3 seconds slower than the frame-based game time (while streaming, so with a moderate CPU load with some CPU spikes here and there), so it shouldn't be that big of a problem I think.
The other problem at least for me is that your new autosplitter is not working for me, after checking the pointer path for levelState in cheat engine I noticed the value is either 0 or ??, but the pointer path for that in the current autosplitter is working perfectly fine for me.
I wouldn't mind changing the autosplitter to a load remover. I think only runners that experience many framedrops (and because of that many slowdowns) in their run wouldn't be that happy about changing the autosplitter to a load remover because that would give them an disadvantage.
I could test how big the difference between the old timing and the load remover is for me in my next runs und would post my results here. If the difference might be too big (which theoretical shouldn't be that big), the current times on the leaderboard might have to be retimed when switching to a load remover so that new runners didn't have a disadvantage to the old times.
Is the part of the autosplitter broken which checks if it was at the end of the level? If so, then I never noticed, that it broke... because I was lazy and changed it so I didn't had to split the invaded levels by myself xD The rest of the autosplitter works at least for me ^^
Yes, the PC autosplitter linked in the resources is a load remover, too, but the timer you use must be pausable to remove the load times. You could also use the autosplitter in Livesplit, which you can download via the splits settings when you set the game to Rayman Legends. That is a autosplitter and load remover, too. To be exact, the Livesplit Autosplitter is technically not a load remover, it uses ingame time, so it should be more precise.
The autosplitter code in the guide doesn't work for me either, but after changing it to the following (removing reset, gameTime and isLoading), it works for me (except for the kill at Truth):
state("TITAN"){ int killsCount : "TITAN.exe", 0x003165EC, 0x38; int frames : "TITAN.exe", 0x003165EC, 0x30; } start{ return (old.frames == 0 && old.frames < current.frames); } split{ return (old.killsCount + 1 == current.killsCount); }
