I hear you, I was talking more to Zero then haha.
I screenshotted the leaderboards before they were refreshed so if anyone wants to see them, here you go. https://imgur.com/a/SMmyQ0J
Should it invalidate glitchless runs? It might be too hard to remove from my muscle memory!
My two cents, I think glitched and glitchless speedruns are both as valid as each other. Some people see it as "everything goes, whatever is fastest", and some care more for the integrity of the game, doing it as fast as possible but with intended mechanics. Neither is right or wrong, hence having separate categories so everyone can get involved.
Fair enough. This is the first game I've used Speedrun.com for and I'm a relative newcomer compared to you lot so I didn't really have an opinion on the situation.
I think archiving all the runs from previous versions is a great idea though, some of those Burg.L% runs were quite old and it's a bit sad to see them just gone, plus it snapshots the different strats used throughout the game's development.
I thought less categories would be better as there wouldn't be a load of obscure categories that only one person is running, however maybe more is better. If there's only 5 categories and someone isn't interested in any of them then they're not gonna submit anything, but if there is a lesser run category they do like, maybe just because they're on the site for that one they'd be more inclined to try some others too, and if not it's still more activity than without them. Adding each difficulty and any%/glitchless to each category even though we're not at 1.0 yet could be a good idea too if it gets more people playing.
And to be fair to Zero, he posted a week ago that the refresh would be happening and no one replied. So with no one to tell him they didn't like the idea, I guess he was just gonna go ahead with it right?
That's a reasonable way to share your opinion.
You're damn right you had some help finding that one! ;) GGs! Good shout on respawning at kid cave from hedge, glad I watched your run first before running mine haha
Do you have footage of that Wyatt? Sounds useful
Yooo nice mate! Squeaked through by 0.1 of a second for the WR, good stuff.
I was going back and forth between playing my regular save and speedrunning and with the large number of runs I finished or bailed on all my saves got pretty jumbled up so it's a bit of a task to clear them out. However I noticed if you quit while dead the game doesn't make a logout save.
So if you also don't wanna mass produce saves while running quick runs, just use the give up option in the menus before you hit quit. Could also set your autosave interval to 20 minutes so you'll be less likely to create autosaves as well, just don't forget to change it back when you start playing normally again.
I dunno, getting all chips and unlocking all mutations are two very different looking runs. But there's also not many people running this game right now so could be good to keep the number of official categories low until it's more populated.
Okay I got one mutation in 47 seconds and it's not exactly an interesting run, so maybe it should require one tier 3 mutation or one mutation purchased from BURG.L? Natural Explorer and Fresh Defense could be close times for tier 3, but I think Parry Master would be fastest by a lot. If going for one from BURG.L, it would be that speedrun plus routing in 2200 science along the way, as in the oak lab there's the big 500, two 100s and the bot for another 100.
Good idea! For the SuperMutant I'm guessing we'd keep Mom Genes in but ignore Reliable Friend?
Here's a cute 1:35. Unfortunately invalid due to being on the public test
Ahh cool, yeah that could add a lot of confusion.
You think we should play on custom difficulty so we can play mild and change it so menus don't pause the game? What other options there would be allowed?
I think everyone does have access to the public test don't they? Looking at the instructions to join on xbox.com you just need to wait for the registration to complete. Happy to eat my words if anyone's tried to register for it and been rejected for whatever reason.
I guess there could be unintended advantages on the public test version though so I'd be fine (current invalid runs aside) with runs only being allowed on the latest live version. Maybe just add a note about that to the rules.