Does it give any good to wait before start the run in Random Glitchless? I see their runs and find they usually use a long time to get pearls, with a lot of time waiting for the dark

you aren't allowed to

"Timing starts on first input..." I would take advantage of what sunlight there is if you really need it.

it doesn't actually, the rules are just badly written

April is correct on this I believe. Any time not playing is supposed to be used in the pause menu to load the map etc, change options.

You may wait for about 1 second of IGT after loading the world before starting your timer. During this time you may not move, but you may pause so that the world may load. You also can not look around or change hotbar slots (f5 is allowed). For IGT you can load the world, then S&Q and reset your timer before you start.¤¤ It is to the moderator's discretion how strongly to enforce this rule. 2-3 seconds to f5 may be OK depending on the run, but if a mod says you waited too long and you did wait more than the 1 second allowed then they can reject your run.

It's clearly not defined.

The run I posted on RSG, I waited for the world to load, but a mod added the pre-loading time to the actual time because it is forbidden, due to the importance of the day/night cycle in this category.

So you can wait for the world to load but it's completly useless, because the time starts when you're in the world. If you want to load the map anyway, just press ESC so the world can load without affecting the day/night cycle.

Allowing waiting and not counted as gametime, as well as using the end played time, both make sense. The first one requires you to fastly do the preparation to get good timing, and the latter just let you hang out. The latter shows how long time you need.

That waiting counted as ingame time is clear only when glitching data to a new world.

The only reason to REQUIRE changing rule is that the rule doesn't make sense. Izraill changed "Timing starts from first input" to "First move" when pointed some requirements don't need input.

It is to the moderator's discretion how strongly to enforce this rule. 2-3 seconds to f5 may be OK depending on the run, but if a mod says you waited too long and you did wait more than the 1 second allowed then they can reject your run.

The rule is too difficult to clarify and too annoying to enforce, therefore it's defined in a case by case basis because it's just not that big of an issue. If you disagree with what the moderator who reviewed the run has said, you are free to appeal.

The rule does make sense, the rule is just a more expanded version of "don't abuse the waiting time", if you read it carefully.

I know the 1s rule, but the express doesn't show more detail, so can't know the exact meaning ( If a run waited for more than 1s and some mod rejected it, can it be treated as a start from 1s?

It does show detail. If a run waited for more than one second and a mod determines that it was unfair, the moderator can choose to either reject or retime the run. If the moderator determined that it was trivial, then it's ok. If you disagree with a run in specific you are welcome to try contacting another moderator to get a second opinion on it and maybe change its accepted/rejected status.

A rough paraphrasing that is less specific but maybe a good summary would be: you should only wait more than one second if you think the moderators will not mind it. If they do, though, they can and will reject it.

I meant, if the runner waited for more than one second, but when the mod reject the run, he start the timing when 1s pass, is it allowed?

I don't understand your question sorry. Please word it better ot explain it further, because I feel like I can almost understand what you say but your english is just broken enough that I can't get it.

the moderator can choose to either reject or retime the run. Can the player choose to retime?

yes. If a run is rejected, a retimed video could be resubmitted.