Due to the optimization of the Any% category turning into a frame war at the top of the leaderboards, it's been determined that a standardization is needed to accurately compare times that are merely frames off.

Thus, the following rule change for Any% is in effect immediately:

All runs submitted from December 3rd, 2022 onwards, faster than 2m 25s 000ms will now REQUIRE you, both before and after the run, to show your stats .json file and show the value for "stat.playOneMinute".

To find this .json file, navigate to "C:\Users\YOUR_NAME\AppData\Roaming.minecraft\saves" (or wherever your saves folder is located, if different). Find the Diversity world (should be called "Diversity (v1.3.4)"), then open the "stats" folder, and then open the .json file inside (you can use any basic notepad program to open this).

Runs slower than this benchmark will not require this, and instead a simple timer can be used, HOWEVER if the milliseconds cannot be determined from the video, then the milliseconds will be set to 999ms. If the milliseconds are shown, they will be rounded up to the nearest multiple of 050ms.

Runs faster than this benchmark that do not show the stats .json file WILL BE REJECTED (or have their time set to the benchmark).

The value shown in the stats .json file is in in-game ticks. There are 20 minecraft ticks per second, so take the number after the run, subtract it from the number before the run, and then divide by 20, which gives you your time in seconds. For example, the current WR run goes as follows: 2767 - 1 = 2766 2766 / 20 = 138.3 138.3 is 2m, 18s, 300ms.

Your milliseconds will always be either X50 or X00, with X being any integer (number) from 0-9.

Current leaderboard runs have had their milliseconds already updated to reflect the new changes, with runs faster than the any% benchmark being adjusted as if they were slower than the benchmark, to avoid having to remove old runs. This is a one-time grace that was only granted to old runs. New runs are subject to the new rules.

If other categories ever become as competitive or have top level times within seconds of each other, than these rules will apply to those categories as well, with appropriate benchmarks being decided if needed. However, regardless of category, showing the stats .json file is still preferred, in addition to showing on-screen timers.

Regarding on-screen timers, Any% currently will not require an on-screen timer if one shows the stats .json file, as the presence of Save + Quit and the shortness of the category would invalidate the precision of most timers.

ALL OTHER CATEGORIES will currently only require an on-screen timer for WR runs regardless of if the stats .json file is shown or not (however, also showing the .json file will help with insuring a precise and verifiable IGT). For non WR runs, only one of these timing methods will be required. Again, this is subject to change should other categories become more competitive.

It is important to also note that: For the stats .json folder to count as a valid timing method, IT MUST BE SHOWN VISIBLY in the video. The ideal order of things would go like this:

1. Start the recording and open the stats folder
2. Enter the Diversity map world
3. Immediately pause and show the "stat.playOneMinute" in the .json file (it should be pretty much the only stat there)
4. Do the run
5. Immediately pause and show the "stat.playOneMinute" again in the .json file. Now there should be several stats from the course of the run. Make sure that "stat.playOneMinute" is visible. If you want further verification for safety, scroll through the rest of the file on the recording, and in a dispute, the mods can compare the stats with the recorded run (although this is not required in any category currently).

I hope these rule changes are not strenuous for the community, and I thank you for your patience in this.

I figured we should have a thread saying what the rules of Diversity 1 are and how they apply to us runners.

1. No breaking or placing items unless instructed or implied.
2. No changing difficulty or gamemode.
3. No typing game commands.
4. Single Player: Select Easy now and avoid Options Screen (see DOWNLOAD FOLDER for details).

What these mean:

1. This is the most restrictive rule, it means that we can't break any blocks unless we are in the survival branch and place any blocks unless we are told to by the map. We can't break blocks in the lobby, alter redstone, escape out of bounds by pillaring, etc.
2. We can't change our gamemode or difficulty essentially via any means. No command blocks, no commands, no options screen, nothing. Only the map can do it for us.
3. We can not type any commands, simply as that.
4. This rule doesn't really apply.

Additionally, in the Survival branch is this rule:

5. You may not place or break blocks within this bedrock chamber.

Placing blocks on the outside of the bedrock chamber is perfectly fine, and that does mean you can activate certain command blocks to preserve wool etc.

So, a while ago, there was quite a lot of Debate about certain rules. At the time, I dictated the rules were one way and one way only, and this was not proper modding.

I wish to apologize, at the time, I was a new mod, I was thrust into this mod position without even asking or being told about it, I just opened up speedrun.com one day to find im suddenly a mod for this catagory, and to this date, I still don't know why or how or when. Because of this, I was unprepared and inexperienced at handling this situations.

A while has passed, and I also had the chance to talk to CrafterDark for a little, and I'd also realized something. Rules are decided by the community as a whole, not the mods alone.

Because of this, the old debate about preserving items is moot as of this point. The rules specifically state that placing items inside the bedrock chamber is forbidden, and when you start up the Survival Branch, you are told you are in pure survival mode. Because of this, I hereby decree that altering the command blocks by placing blocks/levers/whatever on the outside of the bedrock chamber, is in fact NOT in violation of the rules.

Last time this came up, I was being extremely dogmatic about it, and now I think it's time to fix that. Of course, all other rules still apply, but from now on, I'll try to be a better mod lest this game die.

Hello!

Just a quick thread to inform everyone that the leaderboards have been changed from RTA time to IGT time. This is because of any%. The current any% route involves a S+Q to clip through the wall. This, of course, could prevent a WR time simply because of the loading times of minecraft if we used RTA time. This change should not affect anything now or in the future.

So, trying some All Advancements speedruns when I find out that CBenni's timer doesn't work for 1.12. I've also never gotten the Cubitect timer to work, which means I've got no IGT timer for 1.12.

Are there other, accurate, methods for tracking IGT time? And how does installing the Cubitext timer work anyway (even though chances are that it won't work in 1.12)?

Hello! As some of you have pointed out, this forum and leaderboard has been rather inactive as of late. I recently became a moderator of this game, and have made the following changes:

1. Removed redundant leaderboards The original leaderboards were just cloned from Diversity 2, a completely separate game that is not compatible with Diversity 1. We had impossible categories, poorly defined rules, and general confusion among runners. The new leaderboards have been changed to reflect what is possible and what isn't possible within Diversity 1. Our knowledge of the game does continue to increase, so if you find something new that you think warrants a new category, post it in the forums and I'll look at it.

2. Verified runs There was a large pile up of runs for several months that nobody was dealing with. The other two moderators for this game appear to be inactive, so I'll be handling future verifications too.

3. General moderation in the forums The forums will be cleaned up, and questions will be answered. Additional rule clarification will be posted below:

Any% is now defined as:

Timing starts on movement and ends upon respawning on top of the wall facing the Diversity logo.

Glitchless is now defined as:

Timing starts on movement and ends upon respawning on top of the wall facing the Diversity logo. You may not use any glitches in Minecraft.

These do NOT qualify as glitches, and are allowed according to the rules of the map: -- Jumping through the walls in the third section of the Labyrinth Branch. -- Jumping into the redstone below the Boss Battle Branch and altering the contents of the hopper to skip fighting the Witherboss.

4. Added new misc. leaderboards

No Exploits: This category is one for people who don't want to use exploits in the map that otherwise don't violate the rules of the map or are glitches in Minecraft.

No Freebie: Self explanatory, complete this without getting the freebie wool. All Branches must be completed.

5. Clarifying the rules for Level Leaderboards All Level Leaderboards work as follows: Complete the Branch, timing starts on first input after teleporting, timing ends upon teleporting out when you get the wool. You may NOT use commands, go into creative, or bring anything with you.

Just wondering what "Best Ending" qualifies as. is it getting the "Happy Rancher" ending scene, getting all the ending scenes (that you can get with Happy Rancher), or is it getting a 999 Ranch Master score?

Just wanted to point out that when Speedrun.com updated their format, the minecraft leaderboards got reorginzed prioritizing RTA time, rather than IGT, changing a few things around.

I was just wondering, the rules for glitchless say that "no infinite bullets at Wiley, Gradius, and The Guy", but it doesn't mention anywhere else as being expressly forbidden. Is it just because those are the only three places where it is possible? Or it is allowed everywhere else? Because I was watching the WR run of glitchless, and when he was fighting Mother Brain at 6:07 to 6:10, he very clearly did not have 4 or less bullets on screen. I paused to count it, and he had at 6-7 on screen at a time. Is this not the infinite bullet glitch? Just wondering...

So, I was trying some any% set seed runs when I couldn't help but notice the large about of lag when loading the world after every dupe. Now, after that initial lag is gone, there is usually a second slight burst of lag, and this comes from your skin. On some poorer computers, loading the player skin causes a large amount of devastating lag, so I thought, why not just not HAVE a skin? After a little bit of experimentation, I believe now that we can save a little bit of time and a fair bit of lag, depending on your computer, by simply resetting our Minecraft skins to the default (Steve or Alex), so that Minecraft doesn't have to do any external loading of the skin. This won't make that much of a difference for most people, but for some people with bad computers, it should help a fair bit with lag.

Well, hello. To be brief, all the in game timers recommended on this site don't work in any capacity. I'm trying to run in 1.8.X, however I've tried all the timers and non of them work. First of all, LiveSplit only works for 1.6.4, which not many runs do anymore. Secondly, MinecraftTimer2.exe is only the .exe file, and running that always give an error. This is the same error message that this thread of this very message board talks about. http://www.speedrun.com/mc/thread/c2byx Thirdly, the one by cubitect doesn't work for several reasons. First of all, the links on this forum don't even HAVE all the files. I looked at the downloads that the creator himself gave, as well as watched his installation video, and nothing I did ever worked. The .config file never even showed.

I've tried all 4 download links on this site, tried several other download links, and nothing ever works. The closest I ever got was with livesplit, which was the only program that actually ran in the first place, however LiveSplt can only measure game time in 1.6.4 (I tested it).

It looks like lots of other people, from looking at this forum, have had the exact same issue, and there hasn't been a clear, concise answer that works at all.

Just asking for some help here, I have literally done everything that this site, and the programs this site offers, has said to do.

And yes, before you ask, I DID delete the stats folder.