It seems the autobot category has been deleted without any announcement. Bummer.

I am inclined to judge that resizing the game window is an operation that is performed outside the game, not inside the game, and as such it is not allowed. The game itself does not provide tools for resizing the window; it is your operating system that provides this facility. Therefore it falls into the same category as would e.g. changing the game temporary file folder read-only or similar shenanigans.

There is an additional concern: In some cases this glitch is difficult to distinguish from having two instances of the game open simultaneously and just clicking outside in the other window. To verify that this is not the case, the runner would need to have some sort of task manager visible for validation. However, this adds an extra layer of complexity for judging. Now you not only have to judge that the game footage is valid; you also have to judge that the desktop footage is valid. This is a slippery slope I would rather avoid.

However, rather than force my decision on the matter, I will await for further input from the other moderators.

Timing criteria for all categories is this (at least how I have done it):

• Run begins exactly when the highlight on the "NEW” button, on the game-load screen, disappears for the last time.
• Run ends exactly when the highlight on the last “NEXT” button disappears for the last time, on the screen that precedes the screen that shows the ingame timer and stamp counts etc.

Both events need to be judged frame-by-frame from the vod, and the time difference of these two events forms the official run time.

These rules ensure fair and accurate timing for runs of all categories regardless of the type of the ending.

If there is a timer visible on the video, the judge may utilize this timer to verify that the footage does not have discrepancies, but it is not used for timing the runs.

If these events are impossible to discern from the video, or the game has glitched in such manner that the highlight of the button fails to appear or to disappear, it is up to the moderator’s discretion whether the time can be deduced by some other means, such as from microphone sounds indicating mouse/keyboard actions. If the moderator is unable to judge the exact time, the run will be rejected.

The closer that the run is towards the leaderboard top or the closer the time is to other leaderboard entries, the more accurate the timing must be. For runs where the exact timing is not relevant for its position on the leaderboard, we may settle for less accurate timing (whole-second accuracy), if frame-timing turns out too difficult to determine.

Therefore, all players are instructed to make sure that your footage is good quality and that all parts of the game screen are visible at all times and that the game audio is audible at all times.

I agree with this evidence and I have now rejected Caisang’s run(s). Sorry for taking so long. These accusations have already lingered for several months, at least since August.

Over the years there have been several submissions from people who have submitted an otherwise good run, but which have been rejected for failing to satisfy some particular criteria in the category rules. It is always sad when that happens, so please make sure you read the rules carefully.

This is the list of all reasons that submissions have been rejected so far:

• Failed to prove that no mods were used. Solution: Go to main menu, open the mods tab, show that no mod is enabled, and then start your run.
• Game audio is not present in the video.
• Video is not viewable (copyright torpedo or privacy setting).
• Run has been submitted twice.
• Neutralize Ancient Danger: Didn’t open cryptocaskets.
• 99 Bottles of Beer: The bottles are never selected and the message “Beer x 99” never shows on screen.

All of above have occurred more than once, except the cryptocasket one.

Some runs have been given mercy despite breaking rules:

• Escape: Ending demo was not shown or player didn’t let the text start scrolling on its own (something it does only in an actual ending,)
• NAD: Didn’t prove that no threats remain.
• Didn’t prove that devmode was not used.
• Didn’t prove that mods were not used.
• Game audio is missing.

Mercy may be given, if the runner is reputable and/or the infraction has negligible impact to the run’s verifiability, and it is clearly an accidental lapse. However, when the infraction is about failing to perform certain actions that the category mandates, or failing to perform an action that signals the moment when the timer should be stopped, the run has to be rejected for fairness reasons. And it is terribly sad whenever that has to be done. So please do read the rules carefully before you begin your run!

I am not the person to reject a run just because there is no category for yet. If you submit such a run, chances are there will be a category made for it. But as usual, it needs fair and clear rules. In a "all of the planet" run that "pirate all pirates" would fall to, the world size is definitely a factor, for instance.

Thanks for the submission. It will be judged within a few days. However, I notice that the mouse cursor is not visible. Any reason why?

Also you were being barraged by Discord notifications…

Question: Currently all “Naked Brutality” runs that are faster than existing “regular” runs are published as dual WRs, in both categories. Should “Naked Brutality” runs be exempted from the regular category?

The same also applies to Ice Sheet / Extreme Desert runs that are faster than the “regular” WR.

Autoclickers are not permitted for any run.

It does not particularly add value compared to an escape (ending 3) run, as the difference in the number of days is very small.

To make it fair, you would need to post both the video that produces the save file, and the video that uses the save file, and present, on screen, a cryptographic checksum of the file in both videos to ensure that the save file is the same as what was used in the first place.

But even then it leaves open the possibility that one creates the landing with a modded mod that does more than is advertised, such as modifications into the world tile. It is impossible to judge whether this has happened from the save file alone, even if the file was shared.

There are certainly many issues concerning the saves. No modifying the saves is just the tip of it. What if you used a mod that modifies the tile generation, and gives you a starting tile that has all mountains made of uranium and an ancient danger zone that conveniently happens to hide twenty techprof subpersona cores and five resurrection mech serums? You could then save the game, remove the mod, and load the save, but these changes would still be in the game. Also, Prepare Carefully allows you to create colonists that would never appear in real game, such as someone with 20 and double flames in all skills. You could consider this a NewGame+ style branch perhaps.

This needs more work before this kind of rule change can be accepted.

Discourage breaking open an ancient danger and recruiting all people is not at all what I had in mind. By all means, do that! The purpose is “escape and leave nobody behind”, i.e. a happy ending. The extra stipulations are there to discourage from banishing everyone before launching the rocket, effectively turning it into a regular build%.

Each ship cryptosleep casket requires 200 steel, 20 uranium, 10 components, and 5 advanced components — or 300 steel, 50 plasteel, 20 uranium, 15 components, and 15 gold, if you count the a.c. crafting cost. Sure, they are the second cheapest parts of the ship, but they are still quite expensive, compared to, say, coolers. If you need six or eight of them, it becomes quite a significant factor for resource acquisition.

I like the idea about original colonists, but then everyone will just start with rich explorer, get a free pawn as soon as a colonist or mib joins (reset if the newcomer is bad at research), and there is hardly any difference to regular build%, except more dependence on RNG. And the replacement pawns completely negates the point. Yay, we launched a starship. A random prisoner that we recruited earlier flew to the skies. Yay. Meanwhile, the rest of us are still stuck here. Yay.

I acknowledge the notion of RNG with colonist death prohibited (outside the 15-second exception), but that’s the best I could come up with, that is unambiguous, and does not let the player rules-lawyer this into a regular build% by having everyone commit suicide by tortoise. If you’ve got better ideas, I’m all ears.

I also acknowledge the fact that we don’t get many submissions to a single category, let alone multiple ones. That is something that I expect to sort itself out with time, as the game continually gains new audience.

I added a new subcategory today. It is similar to build%. In 100%, all colonists must escape.

Getting rid of colonists intentionally or accidentally is prohibited, to make the category meaningful (otherwise, you could just banish all colonists at the last moment and complete it like build%).

It is up to you to decide how many colonists you want. Choose wisely. With more colonists, you may get a ship built much faster, but you also need a new vacuum cryopod for each new colonist. This is an expert category!

You can leave animals and foreign prisoners behind, but you cannot leave colonists behind.

今日、新しいサブカテゴリを追加しました。build％と斉しいです。 この100％では、すべての植民者は宇宙船に乗る必要があります。人が残ることはダメです。 動物や外国人捕虜を後にしておくことができますが、植民者を後にしておくことは禁じられています。植民者を故意にまたは偶然に取り除くことは、カテゴリを意味のあるものにするために禁止されています。 取得する植民者の数は自由に選ぶことができます。 賢明に選びょう。 植民者の数が増えると、宇宙船がはるかに速く建設されるかもしれませんが、新しい植民者のたびに新しい真空クライオポッドが必要です。 これは専門家のカテゴリです！

For details, read the rules at: https://www.speedrun.com/RimWorld/full_game#Escape (Click 100%, click “Read rules”)

RimWorld 1.0 has been released by Ludeon**!** Watch the EPIC launch trailer here:

According to the release announcement at https://ludeon.com/blog/2018/10/rimworld-1-0-released/ , there are not many changes from Beta19 to version 1.0. Mostly just bugfixes.

For this reason, at Speedrun.com, this time there will not be category diversions for 1.0 and Beta19. The “Escape (Beta19)” has been renamed into just “Escape”. Remember to still mark the proper game version when submitting runs. When reading the leaderboard, you can use the Filter option if you care about version distinctions. You can also use “Show obsolete runs” filter to show runs that would be otherwise masked if the same author has submitted runs for multiple game versions.

For a short transitional period, we will still be accepting runs made on Beta19, but the window will be short (about a week or two at most); after that, all new runs must be made on version 1.0. As of now, runs made on older versions (Beta18, Alpha versions) are no longer accepted without explicit permission (you need to contact a moderator for it).

Happy speedrunning!

Any idea how to make the hops acquisition less RNG-heavy? Also how make the rule about outsourced beer/wort easier to track in case e.g. raid/ancient danger produces that stuff.

I added Mac and Linux as platforms for the game, because the game also exists for them. (I would like to rename PC to Windows, because both Linux and Windows run on PCs… But such are speedrun.com limitations.)

If your run is currently labeled as “PC” but was made on something other than Windows, please contact me.

There is also one major change:

There is also now a new category “Extreme Desert” with the following restrictions compared to “any biome”:

** Primary World definition:**

Scope

Effective new runs submitted since 2018-09-20. The current two existing runs for Sea Ice category (both are beta18) are exempt of these rules.

Suggestion: 99 bottles of beer. Rule: Brew at least 99 bottles of beer. Hops can be grown on soil, in hydroponic basins, or purchased or looted or received from sky. Outsourced wort & beer is banned. If beer or wort is dropped by incapacitated pawns or falls from sky, the runner must either take care to not bring them into colony, or have pawns consume all of them immediately, in a way that is clear enough from the video.

You need to construct both a brewery (research required) and some fermenting barrels to accomplish the task. Each barrel produces a maximum of 25 bottles, for 25 units of wort, in 10 days. The fermentation process in each barrel can be launched even by just one unit of wort, and more can be added later without restarting the 10-day timer. A less-than +30°C temperature must be maintained for the barrels at all times, or the wort becomes spoiled. In negative temperatures the fermentation process becomes paused.

The arbitrary-sounding number 99 comes from the well known folk song that begins with the name of this proposed category.

Minimum time: 10 in-game days to ferment beer + 17 work to brew wort (if perfectly parallelized); undefined time to acquire hops + 400 research for brewing + undefined time to research hydroponics (optional) + build and haul times and other delays.

Minimum ingredients: 495 hops, which becomes 99 wort. 99 wort becomes 99 beer. Plus building materials and research.

Votes? Suggested changes? Should the rules also ban outsourced hops (to make it less RNG)? Also it would be interesting to do in a more challenging environment, such as extreme desert, where day temperatures never fall below +40°C.

I changed some category rules in a minor way today. List of changes:

— “Artisan belonging to your colony” was changed into “artisan working for your colony”. This affects the sculpture & hat runs. Reason: Enabling an option for a possible future where prisoners or visitors may do labor for your colony. Loots, purchases and gifts from heaven are still banned for the category-fulfilling item, as are mods.

— “Prisoners may belong to any faction” was changed into “The affiliations of the prisoners are irrelevant (i.e. they can be from any faction or from none at all)”. This affects 20 prisoners runs. This was so that the rules are no longer ambiguous with respect to the status of unaffiliated pod people.

— Added “Battle(s) must ensue” into the summary of the ancient danger category. This is not a normative rule, but just a quick summary of the extensive rules in the category.

— “Next to a devilstrand growth zone” was changed into “following a devilstrand harvest”. This was to allow the behavior in beta19 where the harvesting person does not immediately drop the harvested item, but it is clearly observed in their hands.

— Rule “Video: [...] UI elements that are important for judging must not be cropped or obscured by split-tracking/chat/camera overlays” was added to all categories.