Sure, we can rule that out from now on. However its going to be difficult to enforce. If people find the spell before visiting the orb room, they might avoid the orb to not show that the orb would have given the spell too.

You submitted this in random seed category. I fixed it, but would be neat if you look at those details more carefully in the future. Congrats on the record.

Sorry that I haven't seen this until now, but yes people have been editing orb flags to get deercoy and stuff and this is totally fine by me. I think the current rules are only against getting extra healing from editing boss kill flags away so rules are fine on this part.

Remember to show mods in the recording next time. Congrats on your first submitted and verified run!

Yeah, that was my view too. We would iterate on the filter to make it even more narrow, and it becomes more and more like a seeded run. Which still doesn't mean its a bad thing. We are still just saving people time spent on resetting, removing some frustration. Not everyone has all those hours to spend on resetting. Should maybe just call the subcategory FSR = filtered seed run or something like that, so that people can add more than accel starts to the filter.

I could see another filter being the seeds where a chest upwarps to the start and has accel in it.

I had a good discussion about this on discord, people pointing out that Minecraft for example makes new categories out of tool assisted runs like Filtered Seed Glitchless. I think the subcategory feature would be enough, we could make a subcategory like Tools: "None/Accel start". To clarify what subcategories are, the current ones are "Major version: 1.0/Prerelease" and "Seed: Random/Seeded".

I think it would have to be its own subcategory under the existing Nightmare category. Submit a run in Nightmare and add a description of what subcategory you would like it to be in and I'll get that sorted.

Moved the run from Low% to Any%, because Circle of Displacement was used. Low% doesn't allow random teleportation. Also mod list should be shown, if mods are used. I'll trust it to just be seed changer this time.

"For all currently existing categories, the proposed new rule will be that time starts when you begin the first run that directly affects the submitted run."

So the current categories would be that.

Mod note: Fixed in-game time. You ended the livesplit timer too early. Run ends when you see the "Game Completed" screen. In-game time is the time you see on the victory screen. The time you get from livesplit would be what goes to the field "Time".

I already answered you on discord but since you made a thread here I'll answer here too for anyone else interested.

First of all, there is no official category for ng+28 33 orb speedrun, so there are no official rules for it yet either. If more interest appears for this category, it could become an official one.

To answer your questions:

1. The "quicksave" egg can save you from this. Basically it's just a crash wand inside a hollow egg. When the player is deleted, killed or polymorphed, the payload of the egg happens and crashes the game. This will take you back to the last save point the game made, the last save and quit or mod restart. I would say using a wand build like this is fair game in a run like this. There are no rules yet so we, the moderators and runners, can just agree if it's fine or not.

2. The first point already addresses the issue, I don't think backups are needed.

Beyond that, I would say have fun with your run! It's your own self imposed challenge, whatever rules you think make it fun, go by those. Like I said there's no official rules for this at the moment.

Also, I have done this speedrun myself already and no backups or quicksave eggs were needed. I just didn't teleport back to chunks I came from, I knew how to path without backtracking.

I would be fine with allowing this mod.

I've added the ghost wand restriction as a rule to the categories where I think it matters the most: All Bosses, 11 Orb and 33 Orb. I think most runners have been of the same mind on the issue for a long time, it was just never added as a rule.