DenmarkIn case the Youtube upload is not working, you can view the run on BiliBili here:
Currently there's no auto-start or auto-split functionality for Mortal Journey, however Inside Edit Splits -> Settings there's a setting for Mortal Journey that makes the timer start from 0, if you manually start the timer during the loadscreen after starting the gauntlet. Sorry, this should have been made more clear in the rules. I'll look into updating the information on the site.
All game modifications are banned for leaderboard submissions.
What third party app do you have in mind?
Hey Simon, I'll try to answer without getting into personal opinion.
It's hard to make individual level runs in a game that is NOT linear. A memory boss will have different approaches depending on the context of the entire speedrun route. For example, Genichiro in Shura Glitchless is fought with 2 Attack Power and 1 Ako, where as in Shura Unrestricted he is fought with 3 Attack Power, Yash and Confetti. Someone would have to decide what exact parameters it would be best to fight the boss within. There's no straightforward answer to that question, so it definitely wouldn't be easy to create them like that.
If you mean fights through reflections of strength, a few people already do those and you can find some times on Youtube by Ongbal and Joe x0f. But it isn't very popular in the grand scheme of things. Less popular than all beads and memories, which was moved to misc, because no one plays it anymore.
That being said it has not been seriously considered, mainly because there's been basically no demand. I remember one other guy on the Discord asking about it. Generally speaking, categories are created to keep track of an already ongoing competition, they are not created in hopes that some people might try it. There shouldn't be anything stopping you from running it though. I play categories that aren't on the leaderboards too, like Shura NG+7 Glitchless.
I hope that clears up why they don't already exist.
I wouldn't completely rule out them potentially getting added in the future, but it doesn't seem like that many people are interested in it. We won't add a category that only a few people would like to run, because on the other end of the spectrum there are people who do not wish for it to be added(last time ILs were discussed those in favour were outnumbered by those against). Maybe there will be support for it in the future.
Hope you have a good day as well
You can find your submissions by clicking the hourglass at the top of the page, next to the searchbar. Then pressing "view all". There you will see your run awaiting verification, if you press it and then press the 3 dots, you can edit the submission info or delete it entirely.
You don't have to do anything though, we'll fix it for you. The item UI thing is such a small issue that I will just verify it for you again (assuming everything else is in order, have not yet gotten to your run on the verification queue). Try to get the layout right next time though.
Feel free to add the video to this submission, or resubmit. Then we will have a look at it.
Here's an update on things: I retimed a few runs to see what effect it would have. The time that would be removed from a run is around 0.7-1.5s (obviously depending on the load time). Don't take these numbers as any sort of accusation or conclusion, this is very preliminary testing.
MoustacheBleue and I have the longest loading times at around 1.5s in the runs I checked (I will release a document with all the timings once I get a bit more measurements of older runs for better accuracy) MonitoLol has the shortest loads with around 0.7s in total and 18ologic is in the middle with 1.1s. Again not robust numbers.
The difference in loading time is large enough that it plays a role for a world record level, but I think that it is not totally hardware related. I think that there are some in-game factors that could potentially effect loads and that we should test different settings and game versions, before we consider changing timing method, it's possible there's an ingame solution. First of all, because we don't re-time atm, fabricMC Sodium needs to stay banned, because it lets you move earlier when exiting portals. I think optifine would be better than vanilla purely because it's that bit more optimized and I also think that a lower render distance is likely better. In my run I ran on vanilla 1.7.10 with maxed out render distance. I have the game installed on an NVME drive, which is fast enough that I would not expect anyone to have a large advantage over me if the main constraint was PC loading speed. EDIT: Another thing is texture packs. I completely forgot. It seems that using the map's texture pack might be correlated with worse loads, which is kinda sad.
Yea I think it would make sense that all categories follow the same timing method. I want to try it out for Any% Unrestricted first though, because there is a world where it makes no difference and it would just kind of be a waste of time and overly complicated.
MonitoLol proposed to exclude loads for Any% Unrestricted runs. I would therefore like to gauge the interest and receive feedback in regards to changing the timing method for Any% Unrestricted to exclude the time spent in dimension loading sequences.
First let me outline how runs have been timed so far.
Time starts on first input and ends the first frame blocks are visible after exiting the Nether portal at the end of the map.
I got the inspiration for that timing method from this pdf made by the Minecraft Java Edition Mod Team: https://drive.google.com/file/d/1EkbgSrFERH7udaPi94_RN0Mq-Xnfq1uA/view?usp=sharing
I imagine that the new load removed time would run from first input to the loading screen on the first Nether portal. Then run again from when blocks first appear after loading in until entering the Nether portal at the end, on which timing would officially end.
I would like to know if runners are interested in this change and hear suggestions. Please respond to this thread if you have something to say.
Wow the epic embed fail. Here's the link to the run:
