ThailandIt should be noted that the game on Switch is called 'Ultimate Edition' and has the Outsider stuff included by default. So the 'no DLC' category here would technically allow Outsider.
Not sure what the best way to resolve this is. Probably should just allow DLC in Any%, I don't see any reason not to at this point. Or else have separate category for Switch or something.
The latest Steam version of the game doesn't work for recent NVIDIA drivers (v545 onwards). The game immediately crashes on startup. Devs are aware of this, but haven't fixed yet, but they have given a workaround: https://steamcommunity.com/app/1500/discussions/0/4205868583237711965/
Recently Uplink was officially added to the Steam version of Half-Life. I'm guessing this would need a separate category, as it uses the updated Half-Life engine.
Oh, I see. Indeed that was the first time I had tried using scroll wheel instead of keyboard. So I guess if I go back to using KB, it will be extremely unlikely for this glitch to happen even if I mash Use. Alrighty then, cheers.
Hello, my run got rejected for supposedly using a glitch: https://www.speedrun.com/mememe/runs/z5p911jm
Not that I'm disputing this or anything, I'm just trying to understand. I have no idea what the glitch in question is, or how to reproduce it. Can someone please explain so that I can avoid it in future? All I know is that I tried to use a valve at one point, and it appeared to bug out and caused me to die from the fire.
I did notice it happen during the run, but I assumed that since it killed me, it didn't actually yield any advantage to disqualify the run. Since, in the run I studied the route from (BlackbeltGingaNinja's), whenever he accidentally did a glitch he just ran backwards and re-ran that bit in order to negate the glitch. So I assumed the same would hold here.
Thanks for any explanation.
I do think timing should start the moment your dwarves are in the map. This is the way other games generally do it. Configuring settings pre-game is not normally included in speedruns. And including the time taken to generate the map is really strange to me; and also the reason I never felt motivated to speedrun, this because my PC takes a while to generate maps.
As for what in-game things to allow or disallow - I don't see any reason to disallow anything. Really it should be anything goes, as long as it is a fresh map, and you only stick to in-game options. I've never tried macros for instance, but if that was a legitimate feature the devs included for regular play, then by all means I think it should be permitted in speedruns too (as long as the macro was created during the run, and not beforehand, of course). Same goes for embark profiles, or anything else.
Currently there is only one full-game run on the board. (There were two others, but they don't seem to have VODs) I reckon there would be more interest in speedrunning the game if the rules weren't overly complicated, and allowed a wider range of strategies that could lead to shorter times than 8-9 hours.
I definitely think it should be RTA. No resets seems like a harsh restriction, and doesn't feel in the spirit of Any%.
The category naming seems to be the wrong way round. Normally the speedrunning convention is that you have 'Any%' which is anything goes, and something like 'Any% no X' which prohibits doing X. So you would expect Any% to allow ScummVM, and incidentally to be the fastest run.
I think the current 'Any%' should be renamed to 'Any% no ScummVM', and the 'Any% ScummVM' to be the true 'Any%'.
Yeah, it's kinda dumb, and dev-intended cheat codes are normally not allowed in speedruns.
Yikes, the current ruleset seems a bit of a convoluted mess at the moment. This is going to discourage runners from playing.
I definitely agree with not allowing third party speed-hacks, that kind of defeats the point of speedrunning and is not really what this website is about.
Segmented runs shouldn't be mixed with single-segment runs on the leaderboard. This creates a problem of legitimacy. Ideally it should just be single-segment, or make an additional misc category for the segmented runs if people want to practice before running single-segment.
Leaderboard shouldn't be ranked by LRT time if there isn't an autosplitter available. Better stick to RTA until there is one.
There is only one category, fixed at 'Normal/Default' settings with stringent requirements on the options. Considering that this takes several hours to complete, I think it would be better to simplify things and have a straightforward 'Any%' category which requires beating the campaign with whatever options the runner wishes.
I assume you are talking just about individual levels (IL)? Full game runs should be RTA, because time spent between missions matters too, and people could also just reload individual missions indefinitely until they get good IGT times displayed for each.
No. I could make one if it becomes more active in future, but I don't think we're at that stage yet.
No idea really, I guess there are some copies on Amazon.
Is there a reason for:
- All difficulty settings must be set to default
- The run must be done in a world created using Basic options.
Seems a little restrictive to me for a speedrun.
Also, wouldn't it make more sense to begin timer when actually embarking on the map? Since waiting for world generation is very hardware dependent, and at that point you haven't yet chosen whether to 'start dwarf fortress' or 'start adventure mode', etc, so technically no game has really begun.
To clarify my earlier comment, I am very much in favour of the settings being shown explicitly at the start of the video, worldgen included. My question only pertains to the timer; I'm asking why the timer itself would start before worldgen, and not when you actually launch Fortress Mode.
It just surprised me because normally in speedrunning, timer starts when you start the relevant campaign etc, not when configuring settings before starting a game.
On a slightly related note, I'm surprised to learn that timing rules start before world gen. I hadn't realised this before. Is there a reason for this? Since the buttons to choose 'Start Fortress Mode' or 'Start Adventure Mode' appear after world has been generated, so technically you haven't even initiated a 'game' as such until you have elected to start Fortress Mode.
The main issue of course being that World Gen is very hardware-dependent. For instance in Factorio and Rimworld speedrunning timing starts after map generation, the moment your colonists are actually on the map.
