I will update the rules to be clear on this :)

Maybe it can be added as an annotation and then a time penalty is added to the run as well. Might make things easier? I know no one runs this and it can be evaluated if a community ever does appear but I want to make sure it's in a good starting point.

Thinking about this again and how it should be handled. A separate category does seem unfair for something that can happen by accident but how do we realistically police the difference between accidents and deliberate. Maybe a time penalty is necessary and we need to just establish penalties for every single level and add them if any get skipped?

So whilst losing a potential PB run to a death in Space something strange happened and after a bit of testing I was able to get a consistent, easy setup.

In space, if you die whilst crossing the threshold to a new level the game gets confused and will teleport you to the otherside of the level you are in. This is similar to screen warp from 2.x but with a few key differences:

• From what I can see in how it behaves it ONLY works in Space levels as opposed to screen warp which worked everywhere but space
• It requires death rather than resetting the level to trigger
• It isn't frame perfect so can reliably be set up and triggere
• It doesn't seem to leak memory at the same rate as screen warp did

Here is the video demonstrating it:

Now this raises the question of classification. Screen Warp as we understood it was a 2.x exploit that required resetting the level rather than dying and it explicitly didn't work in space (although I assume this exploit will work in 2.x). Despite these differences though I believe it is operating under the same basic principle of the door changing but the level staying the same confusing the game and spawning you in the wrong place.

Should the exploit be part of the screen warp miscellaneous category or can we make it acceptable as part of the normal any% and 100% routes? I personally believe we should classify it as "death warp" or "space death warp" instead and make it usable in all normal categories and my reasons are as follows:

• It reasonably only applies in a few fixed places rather than something that breaks 90% of the game similar to how double shot allowed us to basically break a few bosses
• The setup in those instances is pretty easy so isn't going to introduce the horrid randomness of normal screen warp
• It is achievable on the current version of the game whilst screen-warp only works on an older version and was discovered at the end of that category's active period
• Screen Warp felt like a real game breaker and category alterer. This (and this is a personal bias) means we now have a cool and fun way to break a couple of really difficult sections in space but still keeping the wider spirit of the category. We are sill largely running from level to level rather than spending the entire run going back and forth at screen borders.
• Screen warp felt like it was just going to ruin the run which was part of the reason for its move to a misc category. This feels less like it will do that

Hey folks.

Just to say that we now have an Autosplitter for Adventure Mode which you can activate directly within Livesplit :)

It supports splitting on completion of each area along with dealing the final hit to the Warden.

If I make any changes I'll post about them here.

Added a bunch of additional variables that can be split on to give a bit more preference.

Turns out there was something wrong with the new game start support. No idea how it worked before in my tests but it flat out doesn't. I've made the decision to remove autostart support for Any% and 100% because it just was never reliable at all and could easily be confusing when starting a run. Autostart is still supported for Surprise Party though :)

Another small update to the autosplitter. Firstly it reorders some of the any% and 100% settings so they are in progression order. This shouldn't affect existing settings as the IDs are the same. The other change is it now changes how it determines a new game starting which should be more reliable than the previous method.

Added a small change to the autosplitter to support some additional splits people may want (I mean I wanted them so I added them lmao).

There is now autosplit support for reaching Skelord, Fatty, Blocka, the Tower Jetpack and Cotton. Allows for better tracking between the area and the boss. I didn't bother with Ludo because the Hub is so small and relatively simple anyway. If there is a request for it I can add it in.

Cool well I shall get back to writing the tool at some point!

Something to note for the autosplitter too that I noticed when doing runs last night. Due to a limitation of a library that it's using the autosplitter needs to be started AFTER the game has loaded. This can be annoying when you have to reset the game between each attempt but there isn't really a workaround sadly. You don't need to close and open Livesplit; just re-open the same category you're on and that works too/

I just think an arbitrary time penalty isn't the best approach either as the glitch could have saved you no time at all or a ton of time depending on the level.

I do get that it's a rough one if you are going for glitchless and get it. It wouldn't disqualify your run entirely though, it would just put it in the other category.

By default I have made all runs glitchless until I can filter through them properly.

Hello folks (I have no idea if anyone even still checks this game!)

I have been getting back into my speedruns and tooling for them specifically. I am hoping to maybe try and get an autosplitter set up for this game but it will need a lot of testing so may take some time.

Another thing I have been considering is based on a conversation I had with Necrp a while back regarding the Screen Skip glitch. It's a pretty game-changing glitch but due to the nature of it you could easily see a run gain massive time saves from just a few occurrences or die totally trying to get it to happen. For this reason I am thinking of going through all adventure runs (~22 in total) and split them into sub-variables based on whether they include the glitch or not. This means that we'll have a fairer representation of a "glitched" and "glitchless" categories similar to what you'd see in other games. I am also going to see when making the autosplitter if I can detect a Screen Skip glitch within it and provide an option for users to automatically reset the timer if it's detected.

If anyone is still interested in this game feel free to share your thoughts :)

It's certainly been a while...

Pushed a new update to support DLC category as best I can. I couldn't get it to autostart sadly. There just weren't any nice or obvious triggers for that. It does end when you grab the star at the end of the Nexus and it has some splits for various points in the Nexus too such as each major section and reaching a boss.

Pushed a new update to support using Game Time for Any% and 100% and it will read the in-game timer so we can now just ditch RTA for those categories entirely with all its bollocks load time differences.

I will update the rules to include that this can now be used although I am sure I will stick with the on-screen timer as well.

Surprise Party remains unchanged and needs to use RTA and the autosplitter will not auto-start the category if Game Time is set. It will also always return false on isLoading as well so even if GameTime is forced it will never pause the timer. Since Game Time will read directly from the in-game time it probably wouldn't be of any benefit to try to use anyway :P

Autosplitter is now integrated into Livesplit! If you are using the manually downloaded one you can ditch that and Activate the integrated one from your splits page :)

I have removed the autosplitter from the resources for the moment because I have been working on completely revamping it with help from the autosplitter tool development community.

I have been able to get access to the game memory itself so we no longer need to do slow inefficient save file reads or environment variable nonsense.

As of my current tests I have all the following working:

• Any% : All Keys, Ludo kill, Skelord kill, Fatty kill, Reaching Crackers, Last split (post fade out)
• 100%: All Any% splits, all stars, talking to heart
• Surprise Party: Completing each screen, interacting with present

All these categories also support autostart so you should be able to not need to press a single hotkey for livesplit in order for it to work.

The surprise party one I am particularly excited about as it should give frame-perfect readings without the need to retime videos.

Once I am happy with the results I will get it directly integrated into LiveSplit since it no longer requires any external setup to use now :)

So you have a number of questions here and I will try to cover them as best I can.

In terms of how you capture it and whether using your phone is OK or not that entirely depends on the board so if they do not specify and you are unsure it is best to ask in the specific game forum.

So livesplit is only as powerful as the tools the community have made for it. Some games have custom autosplitters written that can detect when to start/stop/split during a game but again you'd need to investigate for your specific game.

In terms of console it depends. I have seen some tools attempt to use image recognition for console games but I think for the most part the runners just hit the split button themselves at the correct point and for super competitive games might retime the run to get the accurate time.

Again with these specifics, the community for the game you are interested in will probably have a ton of advice to help you get started :)

Hope this can help a little.

Gotta do what you gotta do.

It was only 2 threads too :P