I'm reposting this comment because the original thread has disappeared. Since this is relevant to runs I have done and things I want to try eventually I have given some thought to whether longer categories should allow for timer-pauses for breaks. The tl;dr: is probably, because we shouldn't encourage doing unhealthy things.

My current stance is to at the minimum record in-game-time (either the literal time the game reads or just subtract time when the in-game-timer is not running) with the idea that people may save&quit in longer categories to take a break. The limits on breaks I'm not sure of yet--though my gut feel is that an RTA run generally should permit the minimal amount reasonable. I welcome other perspectives.

This was originally responding to a question about the logistics of the category labeled as "All Difficulties Glitchless".

To my knowledge, all leaderboards are real-time-attack by default or at least as they stand.

This category has been sitting in the back of my mind, but even before that, the topic of pausing has been raised for Three Class Relay (6-8 hour gauntlet). That run can be done in one sitting, but with the game offering no downtime longer than 30 seconds (even the intermission credits can be skipped), it's definitely on the borderline of what is a good idea health wise. As far as I know, no one wants to to encourage people to be self-destructive by writing leaderboard rules that reward running an extreme/unhealthy amount continuously.

My approach to that category was to just go as fast as possible and get it done because I'm used to doing one-sitting runs of about that long if I prepare for it. One alternative idea was to prohibit skipping the credits to force a ~5 minute break twice during the run. For what it takes to get through Ultimate Falz, that idea wouldn't be enough.

My personal preference is the least amount of arbitrary rules is the best amount, or "less is more", because there exists some limit on how long of a break is reasonable/necessary, not that there is anything wrong with doing challenges over a longer period. Baten Kaitos 100% just goes with RTA even though it's 14 days minimum, although that idea makes sense for that game with its unique requirements and not necessarily this one.

There are real world analogues to handle this kind of challenge, such as road bicycle races which sometimes take place over the course of days/stages. Perhaps that kind of format makes sense, combined with the force break idea. For example, the run could be RTA timed, but expect people to save&quit at certain points to take a break of at least X minutes/hours, such as after each difficulty and maybe each area in Ultimate.

One approach would be just to also record in-game-time in addition to RTA, which would remove time sitting on character-select. The in-game-time could be used as a primary time with the expectation that RTA doesn't exceed it by some amount, for example if it takes 36 hours IGT (12 hours * 3), perhaps the expectation is that RTA does not exceed 72 hours (3 full days). Or maybe a 3x multiplier is reasonable. This type of system gives plenty of opportunities for healthy breaks while keeping a simple rule to keep it closer to RTA speedrunning. It also scales to shorter categories so it's interesting to me.

Logistically, the simplest solution is to approach the category as segmented instead of RTA, which avoids having to implement arbitrary timing rules, but that may not appeal.

Since there is no competition in the category yet, it's sort of a moot issue that I don't think needs to be resolved to just try the run. I encourage just running what you want to run and how you want to run it, especially if you are pioneering a new category--what makes sense will be more apparent once it is known how long things really take and whether certain ideas worked out or not, or whether other ideas seem really good in hindsight. Nothing has to be set in stone.

Regarding VODs, like any other run, I would strongly recommend making a local recording, to avoid any problems with dropped frames or disconnects from Twitch causing pieces of the run to be missed. With this, there are tools to cut up local recordings even you make one continuous recording.

Besides YT limits, Twitch I believe enforces a 48 hour maximum on one broadcast, something to keep in mind.

One last idea for RTA: without a continuous VOD available and breaks involved, it may be a good idea to additionally capture the current date/time of day in addition to the RTA timer.

(apologies, it looks like the quote function doesn't format well on this forum)