Rules Update

• Future submissions (as of September 20, 2021) must have game audio audible in the background, due to concerns of splicing and/ or slowing down the game and speeding up recording later
• Future individual level submissions (as of September 20, 2021) must be a continuous video without recording skips or splices. Submissions with any kind of recording skip will require a backup recording without skips, whether that be through Twitch/ Youtube livestream, or even pointing an external camera (like phone camera) at your TV/ PC screen.
• Minor recording skips are allowed on console full game runs (at moderator discretion), while PC full game runs will need a seamless recording to be verified.

Rules Update

• Future submissions (as of September 20, 2021) must have game audio audible in the background, due to concerns of splicing and/ or slowing down the game and speeding up recording later
• Future individual level submissions (as of September 20, 2021) must be a continuous video without recording skips or splices. Submissions with any kind of recording skip will require a backup recording without skips, whether that be through Twitch/ Youtube livestream, or even pointing an external camera (like phone camera) at your TV/ PC screen.
• Minor recording skips are allowed on console full game runs (at moderator discretion), while PC full game runs will need a seamless recording to be verified.

Updated rules:

• Future submissions (as of September 2, 2021) must have game audio audible in the background, due to concerns of splicing and/ or slowing down the game and speeding up recording later
• Future individual level submissions (as of September 20, 2021) must be a continuous video without recording skips or splices. Submissions with any kind of recording skip will require a backup recording without skips, whether that be through Twitch/ Youtube livestream, or even pointing an external camera (like phone camera) at your TV/ PC screen.
• Minor recording skips are allowed on console full game runs (at moderator discretion), while PC full game runs will need a seamless recording to be verified.

It's been more than a day, and I think very few new votes are coming in.

It was relatively close, but more voted to remove the 10 second minimum reset rule for non-Bangkok maps.

Going forwards, the 10 second reset floor will only apply to Bangkok, and I will thus retime the (checks notes) 1 run affected by this rule change. I hope it will be a while before more rule debates.

I won't be persuaded that it's a good idea to remove the 10 second penalty from Bangkok too; while there is a lot of lenience around in game timing method, unlimited cutscene resetting for gameplay advantage to zero in game time penalty is not something I want to encourage going forwards.

Another poll on full game reset policy, please vote.

https://strawpoll.com/52kz8su5d

Poll on potential "No major Glitches" variable for H3 leaderboard

https://www.questionpro.com/a/TakeSurvey?tt=T8o3yL6DI2U%3D

In a recent patch (not noted anywhere on the site), resources descriptions have been broken.

Any time that a game resource has a description that extends more than one line, words at the end of each line are cut off in the middle and start again at the next line, so that descriptions are borderline unreadable. It didn't used to be like this, words used to not be cut off between lines, but recently this was changed for no reason.

Already made a bug report via support hub but also posting here for more visiblity.

Examples: https://www.speedrun.com/hitman_2016/resources

Update to rules regarding rating screens.

All SA and SASO runs will still require rating screens due to possible discrepancy between SA Indicator HUD and rating screen's SA rank.

If no rating screen is available (for any% runs), submit the time on the timer HUD for Freeform Training, Final Test, Paris Helicopter Exit (as exits work different for these levels).

For every other level/ exit, if no rating screen is available (for any% runs), submit the time on the timer HUD +1 second (to account for possible discrepancies in timing).

Update to rules regarding rating screens.

All SA and SASO runs will still require rating screens due to possible discrepancy between SA Indicator HUD and rating screen's SA rank.

If no rating screen is available (for any% runs), submit the time on the timer HUD for Freeform Training, Final Test, Paris Helicopter Exit (as exits work different for these levels).

For every other level/ exit, if no rating screen is available (for any% runs), submit the time on the timer HUD +1 second (to account for possible discrepancies in timing).

Adjustment to rules regarding rating screens.

All SA and SASO runs will require a rating screen due to possible discrepancies between SA tracker and rating screen. Peacock -1:59 rating screen is acceptable for this, assuming the rating screen shows "Silent Assassin".

No rating screen shown (for any% runs) or negative score Peacock run, will result in a second added to the last seen time on the timer HUD for most levels/ exits (to prevent possible cases where the rating screen would have been one second later, if the rating screen worked properly).

Exceptions/ Clarifications to the above rule

• For Mendoza tango exit, add 42 in game seconds to the last time seen on timer HUD if the player did not interrupt the tango, and the rating screen is missing or glitched. If the player used a bomb etc to kill/ stun Diana to end dance early, then the run will be invalid if the rating screen is glitched or missing.
• For Chongqing camera exits, the run will be invalid if the rating screen is glitched or missing (as mis-aiming the camera can delay the exit, and the timer HUD is not visible while camera is being used).
• For Romania, if the player does not show the rating screen or syringe glitch happens, go by the last seen time on the timer HUD and add 1 second. (to prevent possible cases where the rating screen would have been one second later, without syringe glitch).
• For Freeform Training and Final Test, go by the last seen time on timer HUD (as these two level exits occur when hitting prompt).

@Pear It seems that OP is asking for a super mod to be removed, which does have to go through site staff.

This may not be fully up to date, and some mechanics may have changed between games, use your best judgement. Following times are for SA or SASO category, and no ephone for H2 runs or fire extinguisher kills for H2016 runs, unless noted otherwise.

Revolutionary- 8s by Dariux 13s by punkstarfunk

Black Hat- 19s by punkstarfunk

Chameleon- 43s by punkstarfunk

Entertainer- 60s by punkstarfunk

Badboy- 1m2s by Frote (H2016 run, no ephone but obviously stuff will be a bit different)

Bookkeeper- 38s by Frote (h2016 run)

Undying Returns- 26s by punkstarfunk

Gunrunner- 42s by Dariux, no ephone

Prince- 29s by Dariux

Serial Killer- 32s by Dariux

Guru and Congressman- See lk0906's run of Deceivers, as Deceivers is just Guru+Congressman

Entertainer- 1m35s by SpeedsterRunner (no ephone)

Blackmailer- 26s by Frote

Sensation- 36s by Frote, H2016

1m11s by Andy Wong

Ex-Dictator 36s by Frote

Surgeons 1m43s by Frote

14s by Pagan

47s by Alex Niedt (no FE)

36s by Mendie 37s by fkgfw 41s by Frote

Fixer 8m38s by RoussJ

Elusive Targets are otherwise time limited missions in Hitman 3, that can only be played at certain times of year on vanilla servers.

However with The Peacock Project, PC players can play the elusive targets at any time and replay as much as you like. There is a guide to installing Peacock with elusive targets here: https://www.speedrun.com/hitman_3_et/guide/jeka9

Although vanilla server elusive target runs are not the focus of these leaderboards, runs will still be accepted from official servers, especially if they are currently records. If you are submitting a console run just leave a comment about it in the run description, if it matters to you.

Poll has concluded. Although there is a decent majority voting "Yes" in each poll choice, for question number 3 I think I will lean towards keeping the H3 main leaderboard to having 3 columns. It's a lot of work to move runs, so I wouldn't do it without like an 80%+ majority voting for it. For questions 1 and 2, I will be making a separate ET Peacock leaderboard and allowing side mission master mode submissions to main leaderboard

Poll about further Peacock content and also master mode.

https://www.esurveyspro.com/Survey.aspx?id=8c2e5419-7724-44de-975f-996e47320066

Simply deleting the variable for mouse/ controller (I believe it is "hyperclick" in your leaderboard) will merge the subcategories.

The "Runs at Risk" does not appear to filter for unlisted Youtube videos, showing all runs submitted before a certain date, public videos or not. I appreciate it may be difficult to code the tool to filter for unlisted videos, but as is the tool is not very useful to be honest, have to go through a lot of videos that aren't actually at risk. Also, it seems to show rejected runs as well?

By all accounts @1 is no longer submitting runs to Minecraft Legacy Console Edition, so it shouldn't be that that is breaking IL's.

The IL glitch has at least something to do with number of IL's; Hitman 2 Category Extensions IL page does not crash, but Hitman 3 Category Extensions IL page does crash, with 6 more levels.

I hope this is not an intentional change, putting a hard limit on the number of IL's that can be shown on a profile/ game for "performance" reasons...

This idea was specifically proposed and struck down because of a general consensus this made the leaderboards too bloated; there was little interest from active runners in the community.

EDIT: Got a faster run very easily. It's very boring concept- use normal strat to kill first 5 with accident kills/ no bodies found, then wait for the next 5 agents to show up.

This tends to happen whenever the site is under high server load. It can take a few hours or even a day for rule changes or leaderboard category changes to show.

However there is a bit of a workaround. Go to the leaderboard in question, use a filter like Filter-> Obsoleted Runs -> Shown, or Filter -> Videos -> With Only, or Filter -> Platform -> (Pick a platform).

Now click on "View Rules", and they should be updated. Note that as soon as you reload the page or turn off the filters, you will be unable to see the rule changes. Note also that if you make an initial rule change, use a filter, then change the rules again, you will have to use a different filter to see the second rule change. Anyways hope this at least helps a bit, it should allow you to see if new rules are formatted correctly right away, if nothing else.