I figured an semi-obscure category would be fun, so I went for the VGA version's 100% mage run. Checked out Puri's runs on the EGA, goofed around a bunch, and so on. Then after playing through 8 or 9 times over the last couple of days and optimizing the route, I timed a couple play-throughs. Much to my surprise, the best one was 41m59s, which looks to be faster than the current record.

I have no idea how to do more, though. Like, how would I submit that? How would I record it right? How do you set up splits? I realize these are a lot of basic questions, but is there some sort of "So You Want to Be a Speedrunner" guide sitting around here somewhere?

It's been a fun test run, and the idea of progressing into a 100% mage run for each segment and possibly even the full collection sounds very fun. But I could use some guidance. Any help is much appreciated.

Alrighty, I will attempt to answer them here.

First, WELCOME~! I'm always excited to see new QFG speedrunners, and consider any resources I may have at your disposal. 41m59s is a GREAT time, so I'd love to see it.

First, for recording, I'm not too picky. I don't want to go over anything that you might already know, but OBS (Open Broadcaster System) is great for recording and free. There are tutorials that can go over the basics for setting that up, as well. The nice thing about QFG is that even older laptops run the games well, so it doesn't take up tons of system resources that can be used for recording nicer.

Each of the categories has the system settings for the games under the "Rules" button, which for DOSBox really just involves making sure the cycles for the game are set to 10,000. For Quest for Glory 1 VGA, disable EMS (EMS=false) at the bottom of the DOSBox settings. This will prevent your game crashing from the dreaded "Out of Handles" error that plagues QFG1VGA speedrunners.

I also have taken the time to give specifics on when timing starts, when it ends in the rules section for each game. For QFG1VGA, it happens when the Sheriff is finished saying "Good luck" and ends upon completing the final action, per SpeedDemoArchive timing. Also, the well known stat-glitch in QFG1VGA that allowed you pretty much infinite points is NOT allowed. Any glitches that happen once the timer starts, however, are totally legit and encouraged.

I don't use splits, so I'm not sure, but there are guides out there for games. Since these games don't have an official set route, however, there are no official splits to even reference unless you're mirroring Puri or davidtki and their routes. David uses the splits pretty much to keep a running of idea of where he needs to go next, and even then it's a guideline if RNG isn't kind.

To submit, you'd record either through a Twitch recording or YouTube or something like it. I recommend YouTube because they don't limit you anymore and there isn't a time-limit on saving the recording.

I'm in the process of exactly such a guide on Steam right now for the series, but it's not going to be done for a while. In the mean time, ASK QUESTIONS. You can email me directly with questions at my screen name @gmail.com.

Hope this helps. Let me know if you'd like more help, and I can't wait to see this 41m run.

The speedrunning subreddit has a starting page that you might reference (https://www.reddit.com/r/speedrun/wiki/faq), though could be out-of-date. Really the important points are:

1. Correct dosbox settings (cycles=10000 is the rule, EMS=false makes your life easy)
2. Have a tool to stream/record your runs (OBS is great for this)
3. While not strictly necessary, a timing program helps a lot (I use LiveSplit, but there are others).

I'll comment some more about splits - they're hard to keep consistent if you're still routing. Don't worry too much about them until you're positive that time improvement comes from better execution or luck on the path you're already going to take, or maybe just use them to remind yourself what your route is. My splits have largely gone unused in fighter 100% due to the inconsistency of random encounters (I could be 2 minutes behind because I got additional encounters early, and then suddenly be 2 minutes ahead because my kobold fight was faster as a result and I finished training earlier).

Awesome! Thanks so much for your replies.

I'll check out those specific programs and see about starting to record attempts. Also very glad to hear there's something that will prevent crashing. I'm not sure if the crash you mentioned is associated with the wonky colors (which usually turn into a crash) or the game freezing while loading Mage's Maze, but those are issues I've run into consistently. I actually got 25 minutes into the run with the only things to do left being Mage's Maze, the interactions at the Hero's Tale Inn, and the final sequence with the brigands. It was very frustrating, to be sure. (If the fix you mentioned doesn't solve those and you happen to know other ways to fix them, I'd be more than appreciative.)

I think I have the route pretty laid out, so I think I'll give LiveSplit a go. (In theory, if played optimally, I should be able to do about 33 minutes.)

One other question: I was looking at rules on Speed Demos Archive, and it mentioned not quitting and re-loading the game. (The segmented vs single segment rules, specifically.) Does this mean that, if the game crashes or I get killed, my run is over? Or is this meant to refer only to situations where you run bits separately and can re-do them for lower times?

I'm glad to be here. I've been a spectator for a while, and this seems like a great way to get my feet wet.

About quitting/crashing/killed and the run being over: Don't know if there are any specific rules for or against it. My first fighter 100% run contained a couple of crashes and possibly a death. My mindset is that you can keep going, but only load saves that you created during the run, though at a certain level of optimization a game-crash or death would be a dead run anyways.

I haven't done magic-user in a while, so don't know how well the ems fix applies to Mage's Maze (I imagine it would help). But the wonky color things, we don't have any real fix for it.

"One other question: I was looking at rules on Speed Demos Archive, and it mentioned not quitting and re-loading the game. (The segmented vs single segment rules, specifically.) Does this mean that, if the game crashes or I get killed, my run is over? Or is this meant to refer only to situations where you run bits separately and can re-do them for lower times?"

While I love SDA's timing, we're not indebted to their rules. I'm not going to be a stickler either on saving and loading because this game has some heavy RNG, but we won't stop the timer for saving/reloading. hehe

Cool. That definitely helps clarify.

I got the recording stuff you recommended and have been playing around. I may send in an initial version before long.

Hello everybody!

It's nice to see that there are quite a few people running this game! : )

But first things first, thank you mr. Reverend for starting the hype, I really admire what you're doing : )

While speaking of running the game itself.. I'd like to ask a question about one thing that troubled me greatly. Precisely, this: "Also, the well known stat-glitch in QFG1VGA that allowed you pretty much infinite points is NOT allowed.".

Thing is.. There was no mention of it in the rules, or precisely, there was this big "ALL GLITCHES AND EXPLOITS ARE WELCOMED!" sign hanging around ; p I've noticed (alas after recording and uploading my run...) that you, mr. Reverend recorded a separate category with using lots of points, and that was the only thing that stopped me from actually submitting my run...

And the problem is, I've taken a different, sensible approach, too. None of the skills points went below 1 (ie, no 0 or minus value), so I practically redistributed the points (rather then spammed the minus value into oblivion to get pretty much as many points as wanted). It still wasn't enough to skip the bear and the thieves' talk - going brute force through the valley of brigands was too hard (suffice to say, even with some magic and building up strength on the open rock, still could kill only 2 of them (and that was hard enough already)) - the troll would be probably even worse - but saved the grinding on moving the stone. So the run is stll based on the classic any% route (Zara-bear cave-password-secret tunnel-end) and stands at 3:08, but with lots of practice could potentially go below 3 minutes. There are some small new things in this run, too (three or so). I did spend quite some work and time on it too, I'm afraid.

Please let me know if redistributing the points is OK and can I submit this run/make it public on YT.

At the same I'd like to propose to add the category with the "maximum points" glitch to the speedrun.com table, since I would like to record and submit it too : )

Lots of luck! : )

Submitting fresh 3:09 that's not using the points glitch (and yes, it could be possible to go below 3 minutes even without it.. although very difficult), probably gonna work on it further, however I feel that the above mentioned "point transfer" is still a relevant topic.

I checked in with Mr. Reverend on Crow's stream, he gave thumbs up on stat abuse for any% with major skips.

First, thanks! I'm thrilled seeing new runners.

Second, I agree, Planet. I did read that the Coles had no idea that the point glitch existed, and in fact, said it was intended that 15 points would be spent. However, my intent with the rule was to ensure that nothing went negative. Davidtki was the first one I saw use the 1-point skill gain thing, and I loved it because it was a clever interpretation of the rules. In other words, as long as stats don't go negative, I'm cool with it. HOWEVER, see point four below.

Third, NICE finds on the route. Zara's shop was interesting enough, but finding an alternative to the dagger throw was utterly fastastic. Well done!

Fourth, the Any% with Major Skips is the one category that really should allow the stat-glitch. I went back and forth for a long time on that one, and landed on that answer. That's why you have the big "ANY AND ALL..." statement there; no other category says it. If I'm hearing you right, however, you feel it should be it's own category, which is an idea I'm okay with. "All-Glitches Allowed" sound good?