It has been brought to our attention that the start timing of OSRS categories, specifically, Tutorial Island, seem off and should be changed.

Let's go into detail.

With a competitive category such as Tutorial Island, frames and tenths of seconds matter. As you may know, Old School Runescape operates in ticks, which equates to 0.6 seconds per tick. With our current start placement for runs (i.e clicking the accept button), there is a possibility where the moment you click accept, a tick had already started and you're waiting for the next game tick to occur while you already started the counter. This is a problem as you may lose time just by not starting on the right tick.

To combat this issue, the moderators were suggested that the start time for Tutorial Island be moved from clicking accept to starting the timer after the accept screen (character creation screen), disappears. Upon hearing this idea, the moderators agreed that such change is understandable and should be implemented. Also from a moderation perspective, it would be easier to time the exact moment a run "starts" compared to the way it is now. With the way it is now, it can be hard to tell when a runner exactly clicks accept if their mouse shows no click action, whereas it is easier to tell exactly when the accept screen disappears.

EDIT: We are now interested in applying this new timing change to all categories. This would mean all runs would be re-timed to incorporate this new start timing.

What's the point of this thread then? Well, we as moderators like to be transparent and community-involved, hence this thread. Mainly, we were interested in if there would be any reason NOT to implement this change of start time. If there is any reason we missed or any reason you think is notable feel free to list below.

TL;DR (EDIT : 11/18/2017) New start time for ALL RTA CATEGORIES. New start time changed from clicking accept to accept screen (character creation) disappearing. If you have any opinion to why this change should not take place, feel free to post below.

What is multilogging you may ask?

By simple definition for general Runescape terminology, multilogging is when you use and play on multiple accounts at the same time and use that to benefit your accounts in some way, shape, or form.

Now, your question may be "What does this have to do with OSRS speedruns?"

To give you some backstory, there was once runner who goes by Phantasem, who actively pushed for the use of multilogging strats (killing off multiple alternate accounts throughout the run) in order to get bones and ashes quicker when doing F2P Ironman Champions' Guild. It was a hot internal debate within the community at the time, because some runners argued that it faulted the nature of the category (why bother having it be an ironman speedrun if other accounts are just going to have the same influence) vs logistical time improving strat (it's a strat within the categories ruleset, and should theoretically be allowed). In order to compromise, F2P Ironman Champions' Guild added an option to declare if a run used multilog strats or not, just so people could separate them if they wanted. (Thread for the internal debate: https://www.speedrun.com/2007scape/thread/t245s )

Now Phantasem has been the only one to use such strats, but if potential runners are interested in F2P Champions' Guild, I think it's to their benefit to understand what multilogging can bring.

Anyway, backstory over.

TL;DR WHAT IS MULTILOGGING AND WHAT QUALIFIES YOUR RUN AS "MULTILOG":

• Using any personal account of yours to benefit yourself in anyway during the speedrun.

• Repeated use of other people (could be your friends or even random people) to benefit you during the speedrun.

• Picking up another person's ashes or bones (if they had died) and using them to your benefit during the speedrun.

• Using an alternate account to pre-damage the rats on tutorial island.

• Using an someone else's fire to cook shrimp on tutorial island.

¤ Runs are reviewed on a case by case basis ¤ aeiou's guide within the guide section is a non-multilogging guide if you're using that.