DISTRIBUTING A LINK TO THESE TIPS YOU WILL EASIER THE WORK OF MODERATORS AND VERIFICATORS (WE WILL NOT HAVE TO WASTE TIME CORRECTING NEWBIES)

This material will be updated. Therefore, add it to your bookmarks and follow new tips.

The first post contains an abridged version of the tips. Details in the second post.

If I didn’t point you to a specific tip by sending only one link, then I just want you to read the entire content. This link is sent to many. You may not need to fix anything, but it would be great if you are aware of the problems of the verifiers when checking the races and help them by spreading this information. Thank you in advance for your assistance.

I check the races and often have some inconvenience to check. I'm tired of sending comments to players in private messages. Therefore, I will collect here a list of my recommendations and send only a link, hoping that players will read and make corrections.

T I P S

1. Show Start Screen
2. Show the selected difficulty of the game
3. Please use two timers (more details later). For example a LiveSplit timer with RA and IGT settings. Also, the timers should be clearly visible. Or at the end of the race, you can open the statistics and show the game time there.
4. Do not block anything on the left side of the "F3" data and game chat. 5.IGT time you can specify the same as usual. If you do not specify IGT time at all, then your place in the leaderboard will be incorrect.
5. Choose your version of the game carefully. Errors are very common where version 1.4 is indicated instead of 1.14.4
6. If your race does not start from the beginning of the video, then indicate the start time of your race in the comments.
7. There should be a seed in the commentary.
8. Do not forget to enter the command "time set 0" in the co-op and only then allow others to join. Your confirmation video or your partner video should show the beginning of the game poem. Otherwise, the result is not considered.
9. Do not use prohibited mods and mods modifications. Get rid of lags with OptiFine or Fabric + Sodium. "Mod menu" and "Fabric api" don't forget to remove them from the Mods directory.
10. Don't use a texture pack. Careful with Vanilla Tweaks. Much is not permitted in this package.
11. Recommended gamma 3
12. It is recommended to post videos on YouTube. Twitch may delete your videos after a while.
13. Specify the most accurate time yourself, if you like. We are not fixing a time that is slightly longer than it is.
14. Don't spam each PB. Know how to wait a little and break your record, saving our time. 16.Publishing a seed at the start of the game is not allowed, except in some cases.
15. If your IGT is too different from RTA, for a minute or more, explain the reason to the verifiers in the comment. It's just that IGT usually differs by 10-20 seconds. 18.Explanation of timers: You can use two timers

1. Usually LiveSplit timer https://livesplit.org/downloads/
2. IGT timer here https://www.speedrun.com/mc/resources

19. Show F3, seed and basic settings for a clean speedrun at the end of the run
20. Download your videos from PB and duplicate them to restore them if they are unavailable or damaged.
21. Collect a playlist with your previous attempts and old PB by posting it in the comments. This is additional evidence in controversial points.
22. Here you can find tips on which category to start participating in competitions if you have doubts or failures. https://www.speedrun.com/mc/thread/u0c5c
23. Do not correct an already accepted race.

Sorry for google translation. If something is not clear, write in the comments. I will try to answer.

Here you can read about moderators and verifiers and leave a thank you for their work for you: https://www.speedrun.com/mc/thread/ttvxa/1#nwn9n 24. If there are large lags and freezes, use the allowed mods and set fewer drawing chunks. 25. Too much difference between RTA and IGT, if there are no pauses, is a known bug for the timer, caused by changing the auto-save settings in the game to non-standard ones. 26. To prevent your videos from being blocked on YouTube because of music, you can upload your videos without sound. Otherwise, verifiers may not be able to access it. 27. Specify the milliseconds correctly. If the timer shows 35 milliseconds, it means 350 milliseconds. In versions Pre 1.9, milliseconds are not needed. Considering that this is a very common mistake, I don't want to fix everyone's time. I'm just deleting milliseconds altogether.

-Why is the race not checked for a long time? -Your race may be in the queue waiting for verification, which can even take 2-3 weeks. Verifiers may just get tired. Try to maintain a friendly attitude towards them to encourage them to do more checks than they can.

More details:

V E R I F I C A T I O N: V E R I F I C A T I O N:// Fixed milliseconds. Read paragraph 27 https://www.speedrun.com/mc/thread/2xb4s/1#d5l39 V E R I F I C A T I O N:// Fixed In Game Time. IGT was missing or was it a mistake. Added by timer or recalculated by video. V E R I F I C A T I O N:// IGT is fixed according to RTA because there is no time to count manually. You didn't show statistics to prove your IGT. V E R I F I C A T I O N:// Fixed Time. RTA was missing or was it a mistake. Added by duration of the race. V E R I F I C A T I O N:// Fixed parameter F3 V E R I F I C A T I O N:// Fixed version V E R I F I C A T I O N:// Fixed Version Range V E R I F I C A T I O N:// Fixed mods V E R I F I C A T I O N:// Fixed category

Please be careful not to force the verifier to make corrections.

R E J E C T I also want to publish a single list of the main reasons for rejecting the race:

// There is no video or there are copyright issues. Remove the sound and add the race again. // World creation not shown. Please add a delay to your macro so it shows each screen of world creation for at least one frame. The macro does not fully display the launch of the world. // Calculators are not allowed // Fabric api not allowed. Remove this mod from the "mods" directory // The same video sent twice. // Add this entry where you start from the title screen of the game. There is no confirmation that this is an RSG. // Suspicion of using a macro or script. Restore the display of the mouse cursor. // Modified fabric, and the resource pack download link must be provided

// No seed. (You must include the seeds of peace in the submission comments. Please add the seed and repeat.) // The F3 data cannot be verified. At the end, you need to remove your timer, chat or webcam from the left side // The link is confusing. (Great video where it's hard to find the start time of a player. Please add the time you want to check and repeat.) // Seed published at start. (This is strictly allowed only in the pre 1.9 version for co-op games where "Co-op Spawn Finder" is used)

// Snapshot. (The use of an incomplete version does not participate in normal competitions) // Forbidden modification. (Permitted strictly only OptiFine up to version 1.15 and Sodium, Lithium, Phosphor for version 1.15 and higher)

// The texture pack does not follow the guidelines in the rules // Using shaders is not allowed

// A forbidden glitch was found. (In this category, the use of special glitches and bugs of the game is prohibited) // Clear water. (It is forbidden to use this advantage) // Used zoom (It is forbidden to use this advantage)

// The cooperative start is not correct. (The second player entered the server before the time set 0 command) // Theoretical proof of the completion of the cooperative race. (There is no video evidence of other players entering the portal. Please add a confirmation link in the comment and repeat.)

Thank you for paying attention to this. I hope you will make the necessary adjustments to your races yourself before submitting them for review.

Now I want to give detailed advice. Some of them are captured in the rules, and some are advisory in nature. However, following these guidelines would be enjoyable for verifiers.

T I P S

1. Show Start Screen

2. Show the selected difficulty of the game The complexity can be confirmed in another way, in the F3 parameters, but not in all versions, but after version 1.8.x: Local Dificulty: 0.00 - Peaceful Local Dificulty: 0.75 - Easy Local Dificulty: 1.50 - Normal Local Dificulty: 2.25 - Hard Local Dificulty: 2.25 - Hardcore

3. Please use two timers (more details later) Timers must be clearly visible. The timer should only be started after entering the command time set 0 in co-op, starting to move in the game. Some start the timer and start generating the world. It is not right. Often players use only one timer, less often without any timers at all, which forces the verifier to count the time manually. This complicates verification. Two timers are the best standard.

Trust me, having two timers is a tribute to our work in checking your races. It is sometimes difficult to count IGT manually, especially when players are paused. It seems like a trifle to you, but we spend a lot of time to verify your data later. Timers help us a lot. Do not be lazy to help the verifiers by showing two timers in your races, RTA and IGT.

There is no strict obligation to use a timer yet. You can see some of the players' races taken, however they don't have timers. This might decide that you don't need timers either. But it takes a good reason to be free from timers. Your computer slows down even without timers and you can't optimize everything. If you do not have lags and you play without timers, then you demonstrate your laziness and disrespect for the work of verifiers.

Imagine a situation where the player pauses the game many times. IGT excludes pause times. How can verifiers check this time? Sit down and write down on a piece of paper the time of one pause, the time of the second pause, etc. Then you need to add everything up. This is extra work in this age of technology ... I just feel sorry for my time. And if what we do for you is dear to you, try to do something for us. Take our simple tips and share them with your friends so we don't have to test every newbie.

If your computer is slowing down and you can't use the timer, then open the statistics at the end of your race, rewind down to the game time data. This is the IGT time.

4. Do not block anything on the left side of the "F3" data and game chat. The exception is the fairly transparent timer on the left. At the end of the run, you must enter the information, the seed command, and press F3. Information should not be covered by anything.

The correct position of the timer is on the right, but not in the corners of the screen. In corners 4 and 6, there may be YouTube or Twitch logos that sometimes close the timer, which is inconvenient when checking. The position of the timer on the left, in corners 1 and 3, is possible if it is semi-transparent and does not prevent you from seeing important chat data and F3. ((Adjust the semi-transparency of the timer on the left or remove the timer from the screen at the end, showing F3). Well suited for the timer position 8. But I recommend more to do the timer in position 5 on the right, maintaining the convenience for checking. You can place additional windows with a webcam, stream chat, donaters and subscribers in the right corners. Zone 7 is suitable for this, but place the timer in one of the places in zone 5. https://photos.app.goo.gl/rw2joePQ79LuZq6Y6

5. When filling out the form on this site, submitting the result of your race, be sure to enter two times. First, you need the time of a regular timer from the beginning of the movement to the end. Then "In Game Time" is needed, which should be less. its essence is that the time of generation of worlds and a pause is subtracted from the time of a regular timer. IGT time you can specify the same as usual. If you do not specify IGT time at all, then your place in the leaderboard will be incorrect. If you don't want to count your IGT or don't know how, then write it equal to the time of a regular timer. IGT missing https://photos.app.goo.gl/1LftfK1p4d66mcH26 https://photos.app.goo.gl/jwcf9n7DZ7XE6VuM9 https://photos.app.goo.gl/hjwWQHSaUGUUsydr7 https://photos.app.goo.gl/FKGNgVF9nr7pSNTL7 https://photos.app.goo.gl/BbksY1vFbC2hjZqo6 Even in a co-op game where a place is not ranked by IGT, if you do not write it, then your place will not be correct. In co-op, you must also write your RTA time in the IGT field

If IGT differs from RTA by about a minute, I start checking it closely. Sometimes I find that the time stated by the timer does not correspond to reality. Real IGT time is much less, which can be seen with the naked eye from Mir and Nether downloads. This happens within 10 seconds, not a minute.

If this embarrassment occurs in a cooperative game, then I understand this lag, due to server lags. But if it happened in a single player game, I consider it to be some kind of system error, a glitch. Yes, other moderators may disagree with me, but I believe that the result of the competition should be obvious from different points of view and prove visually. Otherwise, it looks like software cheating. Even if I'm wrong, I want to stick to this clear logic for everyone.

I don't care if the server counts the time slower due to lags. At this time, the player continues to move in the RTA time dimension. And I cannot forgive the server for its lags, considering this time to be accurate. Even if there are server lags in the single player game and I have to accept the lags of the official Geo IGT timer, I will not. I'll stick to the simple logic that the only thing that should be subtracted from the RTA time is the world load time and the pause time, which is visible on the screen.

In this regard, I have a request that if your IGT is somehow very different from the RTA, then write in advance in the comments why and where you pause. Otherwise your IGT will be fixed. If the video is complex, then IGT can be equated by me with RTA, so as not to dig into it. Therefore, you better point out in advance the moments where there is an excuse for your abnormal IGT.

The timer is not always a proof for the verifier because the verifier also tracks the video gluing. The start and end time of the race is controlled, especially for those who do not use timers at all. Also, timers may not always be stopped in time or simply glitch. Therefore, it is better for you to double-check your result yourself several times so as not to slow down the verification pipeline of the verifiers. An indication in the comments about the features of your race, glitches, lags, pauses, reboots is only welcome.

If the community wants to help the verifiers, they can do so by judging their race. The first judges of your race should be yourself. Try to find fault with him. Nobody needs reticence. Your victory must be clear and unconditional. Level up on those to whom it is impossible to find fault.

If you can provide me with any compelling arguments, then I'll consider. If it's important, then prove it. But make a new PB better. Try using two IGT timers next time. One from Geo and the other from Kohru in LiveSplit. If the result is strange, you must prove it, help the verifier understand your characteristics of the computer or the programs used. Better to avoid any oddities. You must have a motto - clear victory.

6. Choose your version of the game carefully. Errors are very common where version 1.4 is indicated instead of 1.14.4 Try to double-check. Basically, the verifier spends time correcting the race data.

7. If your race does not start from the beginning of the video, then indicate the start time of your race in the comments.

8. There should be a seed in the commentary. It would be great to write a few words about the traits of this seed if it has benefits. For example, it would be valuable to write that on the spawn there was a village or a desert temple nearby, that in the Nezer you immediately appeared in the fortress, that a lake of lava was easily found, that there were good caves ... Maybe someone will come in handy. Your seed can become famous. Just write that the seed is cool.

9. When playing with a friend in co-op, you must open the world to the network, allowing only yourself to cheat. Then you must enter the command "time set 0". After entering this command, a friend can join the game.

A friend's video is not required if you end the game in person. If you were killed and a friend finished the game, then his video is required. Include a link to it in the comment.

10. Do not use prohibited mods. If you have a weak computer, use "OptiFine" (if it is allowed for this version of the game). Will slow down the recording less. You can also make the chunk loading range shorter. I recommend 8-10 chunks. For version 1.15+ Optifine is banned from August 16, 2020. Fabric Loader + Sodium (+Lithium+Phosfor) is recommended instead

Do not use other mods for Fabric. A common mistake of inattentive speedrunners is to use "Mod menu" and "Fabric api". Don't forget to remove them from the Mods directory.

You can remove lags at the beginning of the game, where the first mining of blocks freezes, the blocks that have already been mined may not disappear. To do this, you need to set the following graphics settings: Performance / Fast RENDER - OFF (It's enough)

11. Don't use a texture pack. The more vanilla your Minecraft looks, the more trust and respect you have. Best quality vanilla textures are fine. Transparent menu and inventory interface is prohibited. Shortened weapons are prohibited. Brighter allocated resources are prohibited.

12. The last change in the rules gamma set to not great 5

13. It is very inconvenient at times to check videos on google drive. Create a YouTube channel. Upload the video there, allowing access via the link, if you do not want to open the video to your other subscribers. YouTube is the most convenient for reviewers and I recommend storing your PBs on such a channel. On Twitch, sometimes it is impossible to flexibly control the video, to make the speed higher and the video quality lower. Twitch is not very convenient for this. For example, Chinese speedrunners often save videos at bilibili.com. I cannot download it from there and check it carefully. After all, some categories need to be checked by frames, by milliseconds. bilibili.com is not suitable for this. It is better to post a link to download the video if there is no other choice. I can download it and check it.

14. If you are late to stop the timer, you do not have to indicate that time. You can indicate a more accurate time by looking at it carefully on the video frames. We are not obliged to clarify it to each player and fix it. If the time is a little longer, we do not correct it. This is your task.

15. It's just a dream. )) Do not submit all your PBs to the site. Try to send your best time, which you can't improve for quite some time. We call this PB spam. It really takes a lot of time to consider every outcome of your every day of progress. Try to send your best result in at least a week, and preferably two weeks or even a month. I personally do that. If I know that I can improve my time in a few days, I don't consider it important to send it to the site. I've been coaching one category for a month now, having installed a dozen PBs, but I haven't sent any of them to the site. I encourage newbies to do the same, respecting the time of the verifiers.

16.You cannot move to make sure the seed is right for you. An exception can only be in a cooperative game. You can only change the first person view to the third person view. The beginning of your movement is perceived by the verifier as starting the timer. Your time may be corrected because of this.

17. If your IGT timer shows too much lag from real time for no reason, then your IGT time can be corrected by the verifier. The time will be set equal to the RTA timer. If you want to help the verifier understand this, then explain in advance in the comments where questions and misunderstandings are possible. You can indicate where you have a special pause in the race or another reason for a large IGT gap. Otherwise, there is a chance that your video will be rejected.

18.Explanation of timers: You can use two timers

1. Usually LiveSplit timer https://livesplit.org/downloads/
2. IGT timer here https://www.speedrun.com/mc/resources

The easiest way: Minecraft IGT in LiveSplit Tutorial

IGT timer works automatically if you start it before playing. It does not automatically count the time of world generation by your computer, as well as the pause time in the game when you left the menu with the "Esc" key. This makes your IGT time the most accurate. IGT timer refreshes the time on the screen when exiting the world generation, at the end of the game, and also during pauses.

IGT time you can specify the same as usual. If you do not specify IGT time at all, then your place in the leaderboard will be incorrect.

It happens that someone indicates the time of their entire video as the RTA time (when filling in the data of the run submission form, this time is upper). We are not interested in the timing of the video. Time must be specified from timers. As a last resort, if there are no timers, we ourselves count the time from the beginning of the movement in the world to the end of the game. This would be a rough calculation and it is in your best interest to use timers and display them on the movie recording screen.

19.It is recommended to show the game settings at the end of the race.

1. Chunk drawing distance
2. Disable dynamic lighting
3. Disabled shaders
4. The presence of fog (In detail)
5. No Fast Math (Performance Settings)
6. No Lazy Chunk Loading (Performance Settings)
7. No Clear Water (in the Quality settings in version 1.9 - 1.12.2. Since version 1.13, this parameter has been removed from Optifine.) 8 ) Default autosave interval
8. Statistics can be shown to confirm some controversial achievements.
9. In the category with achievements, you need to show all achievements Example: Perhaps I will supplement this list. When referring to players, I will refer to points from this entry, wanting to draw attention to a specific tip.

20. I recommend downloading and duplicating your PB on YouTube and on your disk. Twitch sometimes rejects a recording. In addition, it is not very convenient for us to check the video on twitch. Download your PB. This way you won't lose your result if something happens. If the video is missing, we can ask you to restore it. Be sure to write about this to the verifiers or moderators.

21. in connection with deception, attempts to present other people's races as their own, we can now demand additional evidence from top players and not only. You need attempts to pass, several hours of video with failures. Need previous PB, too, not in 1 day laid out. If this is not the case, there is a high probability that the video will be rejected, especially if the player does not make contact and does not try to provide evidence. Therefore, I advise you to collect a playlist of your attempts to speedrun, so that you can provide a link if necessary.

Some people don't want to clog up their YouTube channel with non-interesting content, game walkthroughs with mistakes or failures. Some people don't see the point of trying to stream. In order to meet these circumstances, I want to offer you a compromise. You need to record your runs as you normally do. Then you can combine some of these failed attempts and post them with access via a link to YouTube. Personally, I find it even useful for the player, especially when you can review your mistakes and comment on them so that you don't repeat it. So I'm going to create a selection of my failed attempts for each category. Since I'm doing speedrun reviews on my channel, I can post it in the public domain. My subscribers are not so fastidious as to demand special editing from me. And so, do not delete your failed attempts, collect them and post them to confirm your skill.

22. Beginners should not try to go through the entire minecraft at once for a while. For starters, there are shorter and simpler categories. Read about it here https://www.speedrun.com/mc/thread/u0c5c in short, the scheme is something like this:

1. Any short category (get Items, All Wood...)
2. Partial passage or some kind of achivka (Enter Nether, Full Iron Armor 15lvl...)
3. Simplified full walkthrough (Peaceful, SSG)
4. Complete passage (RSG, Co-op...)

23. Do not correct an already accepted race. If you decide to fix your race after you accepted it, it will be sent back to the moderators for review. Make an appointment in advance with the person who accepted your race. Specify what you want to fix in the parameters so that your race is not checked a second time.
24. If there are large lags and freezes. Optifine, which is allowed before 1.16, can help. In 1.16+, you can use Sodium and Fabric. Drawing chunks in Nether in dangerous places can be done 10-8 chunks. You can also pause in the portal until the chunks are loaded.
25. The default auto-save settings are about 4 minutes. This is due to the autosave of the game's internal server, which cannot be changed. If you set autosave for 6 or 12 minutes, the difference between RTA and IGT will increase. So, the difference in 30 minutes of the game can be about 4 minutes, which certainly pleases the player, but is self-deception or an attempt to deceive the verifiers. Don't do this. If the verifier did not notice your pause in the game, send them a link to this place or specify it in the comments to the video, so that there are no misunderstandings. Otherwise, your unusual IGT will be equated to an RTA.
26. Sometimes access to YouTube videos may be blocked completely or partially in some countries. This is done by the author of the music or movie fragments used in the video. Sometimes it is impossible to check such a video. To avoid this misunderstanding, you can send your video to YouTube without sound, or edit it in the YouTube editor by deleting the sound. At the same time, do not forget that for high-rank races, you may need the original, raw video, if you are asked to provide it later.
27. Live Split does not show thousandths of a second. So 35 milliseconds in Live Split means 350 milliseconds. When adding your race, try to keep this in mind.

The most accurate auto-save time is 3 minutes. By default, the game's internal server is saved after 3.3 minutes. This can be viewed in the file optionsof.txt in the line ofAutoSaveTicks: 4000

Sorry for google translation. If something is not clear, write in the comments. I will try to answer.

1 week ago

More details:

V E R I F I C A T I O N: // Fixed In Game Time. IGT was missing or was it a mistake. Added by timer // Fixed Time. RTA was missing or was it a mistake. Added by duration of the race // Fixed parameter F3 // Fixed version // Fixed mods // Fixed category

Please be careful not to force the verifier to make corrections.

R E J E C T I also want to publish a single list of the main reasons for rejecting the race:

// No seed. (You must include the seeds of peace in the submission comments. Please add the seed and repeat.) // The rules were not followed. F3 data is required to check 1.16+. You need to show the seed of the race and press F3 // The link is confusing. (Great video where it's hard to find the start time of a player. Please add the time you want to check and repeat.) // Seed published at start. (This is strictly allowed only in the pre 1.9 version for co-op games where "Co-op Spawn Finder" is used)

// Snapshot. (The use of an incomplete version does not participate in normal competitions) // Forbidden modification. (Permitted strictly only OptiFine up to version 1.16 and Fabric API + Sodium, Lithium, Phosphor for version 1.16 and higher)

// Non-standard visuals. (To participate in competitions, it is recommended that the most vanilla Minecraft is without shaders and texture packs that knock down the verification pipeline.) // The Gamma parameter is questionable. (No shadows detected. Average 2-3 is recommended, not the brightest.)

// A forbidden glitch was found. (In this category, the use of special glitches and bugs of the game is prohibited) // Clear water. (It is forbidden to use this advantage) // Used zoom (It is forbidden to use this advantage)

// The cooperative start is not correct. (The second player entered the server before the time set 0 command) // Theoretical proof of the completion of the cooperative race. (There is no video evidence of other players entering the portal. Please add a confirmation link in the comment and repeat.)

Thank you for paying attention to this. I hope you will make the necessary adjustments to your races yourself before submitting them for review.

Now I want to give detailed advice. Some of them are captured in the rules, and some are advisory in nature. However, following these guidelines would be enjoyable for verifiers.

T I P S

1. Show Start Screen
2. Show the selected difficulty of the game

The complexity can be confirmed in another way, in the F3 parameters, but not in all versions, but after version 1.8.x: Local Dificulty: 0.00 - Peaceful Local Dificulty: 0.75 - Easy Local Dificulty: 1.50 - Normal Local Dificulty: 2.25 - Hard Local Dificulty: 2.25 - Hardcore

Im a little confused about this part, is the a benefit for using a harder difficulty?

(Please remove too large a quote, leaving the fragment with the complexity.)

Thanks for the question.

• Does it make sense to speedrun on high difficulty?

• It is more profitable to pass at an easy level. There is no dedicated topic for hardcore fans. But in hardcore masters such as Illumina, there is a distinct caste, an elite. Agree ... Let someone seem to have defeated hardcore masters such as tarokitchen and others, playing at an easy level, this is not a clear victory.

In my opinion, hardcore masters outnumber their light opponents by an order of magnitude, even if this is not reflected in the standings.

Difficulty level is not an equal playing field. Hardcore changes the game a lot:

1. Hunger occurs more often, and recovery is slower
2. Damage from lava, fire and falls is stronger
3. Damage from mobs is stronger, sometimes twice. Skeletons, Piglins and Ghasts shoot more accurately.

Hardcore players are probably more cautious, more prudent, more experienced and arouse my particular admiration. Although I also prefer hardcore, I do not recommend them to get carried away by those who are not in this passion for speedrun for long. Hardcore is time-consuming, too many failures. If you are not a big minecraft fanatic, then play at an easy level and do not worry.

The only champion in Hardcore was and remains the Japanese legend tarokitchen in the RSG Pre 1.9 category. I remember how in one of the races he could set a result of 23 minutes in version 1.7, which is considered more difficult than the now popular 1.14-1.16.

Only this summer 2020, modern champions began to approach and surpass his result achieved 2-3 years ago. However, they do it on Easy mostly. I believe they never beat him or surpassed him. They look like champions, but they are actually a black belt in combat speedrun in Japan.

EDIT TO MY VIDEO ON ICON LAG:

Fast render is what causes the very large lag spike. Setting the screenshot size to 2x only increases the quality of taking a screenshot (pressing F2).

I learned this a few days after creating my video.

My thoughts on how to properly prepare proofs of your cool PB or WR

In order to filter out real records from fake ones and ease the torment of verifiers checking disputed races, it was decided to follow 5

Reason for rejection: "Insufficient data for verification. Send all the data and repeat. Details here: "

1. Worlds. The main proof of this game

2. the Pb Set. Additional proof with a link to a playlist of videos with normal PB progress

3. a Lot of work. Additional proof is a link to a selection of videos of many hours of attempts in this category.

4. Broadcast. Additional proof with a link to this broadcast

5. Raw video. Secondary proof of the raw race video

6. the Openness of the player. Not resistance to verification.

7. Worlds. The main proof of this game

is That you need to save 3 worlds: №1 World (Previous) №2 World (WR or Cool PB) №3 World (Stop recording) Save everything in one archive immediately after recording and put a link to it in the comments.

You can't re-enter these worlds. Don't enter them. Put them separately and archive them. World No. 1 controls the probability of gluing World No. 2 is compared with the race data, confirms the time and other parameters World No. 3 additionally controls some possible deception attempts

Without #1 and #2, a high-ranked race will not be considered at all. If you are used to deleting the previous failed world, your race will be rejected because it is unverifiable.

So, you don't delete world #1. If you reset it, you continue to record how you create world # 2. Otherwise, if world # 1 was long, you can start recording from the title screen and create world # 2, where world # 1 will be visible.

After setting a record in the world No. 2, you continue to wash down the video to post a seed in it. Then you need to go out and create world # 3, from which you can immediately exit. After that, you can stop recording or continue, showing your emotions of joy. You have done everything correctly.

2. the Pb Set. Proof of a link to the video playlist where normal progress in PB will be displayed

If you installed a cool PB without intermediate ONES, this is a big minus. You don't need to send intermediate results to the site, but upload them to your YouTube playlist. Keep a timeline of your success. If you are shy or don't want to clutter your channel with this, but make these videos with access via the link. Collect enough of your PB's in a playlist with link access. It is good to have at least 5 intermediate PB. If the PB is not present or not sufficient, the race will be rejected as doubtful due to insufficient data to fully confirm it.

3. a Lot of work. The proof is a link to a selection of videos of many hours of attempts in this category.

Usually, all honest players go to a high result for many months and even years. It is important to note that your progress should take at least a few months, preferably half a year. If you set a record in a few days, a couple of weeks, or even a couple of months, we will have the right not to consider your result provable and not to understand your channel.

4. Broadcast. Proof with a link to this broadcast

If there is, add a link to the broadcast where you set this record. This will add some more weight to your race. Get addicted to broadcasting on YouTube or Twitch. With OBS-Studio, you can simultaneously broadcast and record the race on your computer. This broadcast can be an additional proof.

5. Raw video. Proof by raw video of the race

This proof may sometimes be required if the examiners ask you to do so. If you want to edit or edit a recorded video or comment on it, first archive the original video or create a copy. Some video editing programs can change important parameters that will make your race unverifiable and rejected.

If you were asked to send a raw file and you have a raw video recording of this race without changes, then send it via a file sharing service, such as Google drive, leaving us a link. YouTube videos can be transcoded. This won't do. The only exception is broadcasting in some cases.

If there is a chance that there will be extraneous sounds in the video that you don't want to publish, you can record without a microphone, but you can't change the raw video or optimize the sound quality. To avoid this, record without a microphone. Videos with cut-out audio are also not allowed. There must be either the sound of the game itself, or the sound of the microphone.

If you anticipate that the reviewers may request a raw file, then prepare it in advance and leave a link in the comments for the race. This will be a sign that you are trying.

6. the Openness of the player. Proof is not resistance to verification.

If you have to ask for a long time to send all the materials for verification, we consider it an attempt to hide the deception or shortcomings of the race. If you have included all the necessary data in the comments and they are easy to find and download for verification, it means that you have nothing to hide. However, sometimes the reviewer may ask you to answer questions, send screenshots, or show a screen with game settings, game files, video editing programs, etc. (as part of the race data).

Resisting these requests or red tape with promises to do it much later may be regarded as an attempt to hide something. If you really value your results, you will try to find a few minutes to respond to the requests of verifiers in time. There are cases when players resisted verification and created additional difficulties for themselves, showing disrespect for the hard work of verifiers and moderators. A disgusting manner of interaction, a bad reputation as a cheater can take a Central place in the verification of the race.

You can't justify the urgency of your business or moving to another city while proving the legality of your race. If you plan to be very busy in the near future (1-2 weeks), do not send your race until you are free. Otherwise, your "employment" will be seen as resistance. Just choose the right time to start your proof and bring it to the end.

To avoid blocking dishonest players and allow them to play fairly after critical errors are detected, all disputed races will now be rejected with the wording " Insufficient data for verification. Send all data and repeat. "

Warning:

1. if there are no necessary worlds to check, then the race is rejected without consideration.
2. If there are worlds but not enough PB, then the race is rejected without consideration
3. If there are worlds, there is PB, but little labor on your channel, there are no multiple attempts, then the race is rejected without consideration
4. If there are worlds, PB and a lot of attempts over a long time, but it happened outside of the broadcast, the race can be considered after some time of studying your content. Because of the record in the broadcast, this decision would have been faster.
5. If you have 1-4, but we still have concerns due to oddities in your race, we can ask for a raw video file. If it is somehow corrupted or does not match, the race will be rejected because the data is not verified.
6. If you provided all the listed data with great disrespect to the inspectors, taking them many hours or days, then your race may also be rejected, even if it is legal. It's just that in WR, we are increasingly guided by the principle where doubts outweigh evidence. If there is a slight doubt, especially in WR, the race will be rejected until the player is fully prepared to prove the validity of their run.

Thus, we are trying to make it harder to get world records and cool PB, leaving this goal only for serious players. This applies mainly to RSG categories, but may be required in other categories in some cases. Thanks for understanding.