Yeah that's a fair point about 100% Reset Abuse.

Another questions is whether this is an opportunity to evaluate whether we want to keep the timing the same.

As IGT now pauses the moment you kill Float and stays paused during the ending cutscene do we want to switch to using IGT as the primary timing method?

Hi all,

As you probably know a new update has gone live and I've had a chance to play the new content as well as check some of the older content to see what might have changed. I will compile my thoughts below. I didn't test Surprise Party but did do a 100% playthrough and do the new DLC.

General Thoughts:

• The new DLC content is phenomenal as a casual playthrough. As speedrun content it is far too punishing for me at least but I welcome the creation of a category for crazy people :P
• The Jump now does feel a bit more consistent. I used to sometimes land just on the tip of a platform and not have the time to get another jump off causing me to fall. This doesn't really happen anymore
• The Jetpack controls are a lot nicer and in particular make the final section a lot easier
• It seems much less likely that when sliding against walls you'll lose your momentum suddenly. I had it happen once in a 2 hour play session
• If you die whilst holding jump then you will respawn and immediately jump

Changes that affect the speedrun:

• Reset Abuse no longer works
• Certain tricks that relied on the Movement Precision bug such as Ice Skip in the Shadow Realm now no longer work
• This link shows some of the areas where Movement Precision changes have had an effect: https://imgur.com/a/moQUjFf
• The Jetpack's improved controls have slowed it down meaning that both sections that make use of it will see time losses
• Game time pauses when in the post-crackers cutscene before finding out your score

My thoughts on categories:

• We need a new variable for this patch as some of the changes will affect the times
• Reset Abuse should still be a separate variable and the rules description should make it clear that it is not possible on latest patch. Alternatively it could be its own category as well to stop submissions into the current patch table.
• Surprise Party will need its variables renamed from Legacy and Current to something like Update 1 (version 1.4), Update 2 (version 2.0), and Update 3 (version 3.0) I reckon.
• We should probably add the DLC as a category even though it's insanely difficult. Again this would need versioned to match releases. I believe it was added in version 2.0

Another small thing is that the save files have been converted to plain text so I should be able to use them to develop an autosplitter for the game. I have been experimenting with an early copy of a save file Alex gave me and got the majority of what I wanted working. I will keep the community posted on how I get on.

So let the discussion begin :)

So it appears the content update has actually fixed the glitch....

I guess we need to look into having Patch variables

Was literally just here to mention the rules hadn't been updated haha.

I have also stuck in the resources section a folder with splits for all category combinations (except surprise party legacy cos no one runs that) so new runners or returning ones can get up to speed easily.

I imagine you've already seen but it doesn't work in any of the space levels because the transition isn't instant there.

I mean I'm not sure if death abuse is an apt name as you're not using death as a mechanic. You're using the level reset which is different as it resets everything whilst death just resets cycles.

I know of 2 places it softlocks.

The first is the first ice level. The second is the first room in the shadow realm where you use the double jump to reach it.

The moment it happened:

Ok so the first order of business is naming the tick.

I called it something like "Reset Glitch" and Lemur has proposed "Screen Warp" or "Ol' Switcheroo" :P

Version 1.3 now live

• More general purpose fix for the multi-split issue at the end of certain chapters

You may need to force LiveSplit to get the latest file. These steps can help with that:

• Deactivate the autosplitter in LiveSplit
• Select settings to get the location of the file
• Browse to that location and delete the file
• Activate the autosplitter again

The autosplitter has now officially been integrated into livesplit as one of its supported scripts. Activating it can now be done when editing any splits for Valkyria Chronicles. I will continue to post updates here and keep the asl file listed in Resources but manual downloads should no longer be necessary.

I have updated the tool to version 1.2

• Load Removal now supported for both Windows Store and Steam versions of the game
• Splitting on Maximillian's final hit point now an optional setting (defaulted to true)

Now that the tool is feature complete I will look into getting it added to the Livesplit repository meaning that manual downloads of updates should no longer be necessary :)

I have updated the tool to version 1.1 to address some bugs found by Sniperdog during his tests

• Changed memory address for determining Maximillian's hit points pool
• Fixed a bug where completing 10-2 on Any% playthrough would cause multiple splits to trigger
• Fixed a bug where killing Maximillian wouldn't trigger a split
• Fixed a bug where loading a save in 18-2 would trigger a split

I have added an autosplitter to the Resources tab.

It supports final hit on Maximillion and "Operation Complete" splits on both Steam and Windows Store versions of the game.

Work is being carried out on supporting a load remover but in the meantime any feedback on the tool would be awesome as it has only had my own local tests so far.

I don't know if he has any plans to do another round of bug fixing to be honest. Plus he despises the Unity controller library so I can't imagine he'd be too happy looking at an issue like that. He is working on a final DLC though so maybe can mention it to him?

The 2 inputs to one button isn't shooting inputs, it's the jump input and shoot input which both automap to the Square button on a PS4 controller when using DS4. This only happens by default on that controller setup so I was just saying we probably shouldn't allow that particular input.

Oh yeah I forgot about JoyToKey.

Yeah in that case I think it's totally fine to rebind X to L1 to keep more stuff off the keyboard.

Analogue sticks I am still a little unsure of if it isn't as easy to do.

So what I do in my runs that I believe is acceptable is during those early boss fights I spam circle (default shoot) on my controller and x on the keyboard in rapid sequence since the game code doesn't seem to have forced delays between inputs. I also use the spacebar to jump at this time.

This doesn't really count as double inputs as I am pressing 3 different inputs just very quickly in succession.

I think this is fair as the game is basically unplayable without a controller so it's a fair assumption that players will have both M+K and a controller.

Perhaps rebinding space bar to L1 would be more convenient. I guess the question is whether that rebind is easy enough to do on other controllers.

So my concern with certain rebinds is that if they can't be done on the vast majority of controllers then that creates an unfair advantage to those with access to certain hardware.

For example the PS4 controller using a basic DS4 connection considers the Square input to be both a jump and shoot input which can also give an advantage on those fights. Now this is only available to those with a PS4 controller which I think gives an unfair advantage hence why I don't support its usage.

These are just my thoughts on it though.

Yes that's what I would go with. From that point onwards there is no additional input needed to complete the stage.

I'll amend the rules description to make it clear.

I have just done a test and you can still quit out of the white world after defeating Vektor thus allowing you to get your IL times without locking yourself out.

This means that you can do all the worlds except 1 over and over again for IL practice and then you need to commit to final world only.

So not as bad as it could be.