Hey heisters!

Just wanted to put out an announcement regarding our newest moderator - haracookie! Following his indepth testing of the IGT issues, as well as being a helping hand for new runners, we felt this appointment was justified.

Keep those helmets flying!

Hello heisters,

Thought it'd be wise to take a moment to discuss the current leaderboard layout/decisions taken regarding certain rules, as a way of being entirely transparent on the matter of possible future steps!

Rules:

The biggest rule decision, arguably, is the decision to use IGT (In-Game Time) despite the timer being broken via server related issues. The reason this decision was taken, was due to the fact that each option had pros/cons, and we felt that using IGT provided the most ease of access, whilst reducing the cons as much as possible.

The options that were available to us were as follows:

---------------------------------------------------------------------------------------------Use IGT.

Pros: Makes runs easier for runners to submit as the timer is provided "out of the box" and, mostly, works

Cons:

Is slightly inconsistent depending on the current server status/a runners internet connection to the server

---------------------------------------------------------------------------------------------Use RTA.

Pros:

Would be a more reliable time method than IGT as it'd be 100% consistent

Cons:

Would impart a larger burden on runners to add a real time clock to their run via video editing (of which console runners may not have access to)

Opens the door to runners abusing the clock by slightly speeding up their run by a small percent (1-2%) which would be nigh impossible to tell for verification purposes

---------------------------------------------------------------------------------------------Use a mod to fix IGT.

Pros:

Fixed IGT - obviously.

Cons:

Console runners wouldn't have access to this mod

Vastly complicates the barrier to entry for a new runner

Possible tampering of the mod as a cheating method

--------------------------------------------------------------------------------------------Another rule decision worth discussing, was the banning of private servers. The reason for this was due to the fact that private servers are 1) accessible only by pc players, creating a divide between console/pc runs, and 2) private servers provide an unfair advantage in some cases - such as pagers triggering upon guard death almost immediately, compared to the usual 5-7 second (or so) wait a normal server runner would experience.

The rules regarding mods were also written due to similar reasonings as the aforementioned rule decisions, creating a divide between pc/console runners as well as opening the door to risk of cheating within runs, as mods can functionally be anything - from mere asset replacements, to skill tree/skill effect modification. A mod that makes "rush" provide a 12% movement speed bonus over the base game 10% would be incredibly hard to notice from mere eye-review.

Future leaderboard steps:

As with every leaderboard, nothing is ever set in stone - and things are always subject to change depending on what the community wants or desires. We've personally seen some really good suggestions for categories, such as:

• Maskless%
• Full Stealth
• Full Loud
• All loot
• Asset-less
• Random Seed

We hear the demand for such categories, and feel that these categories would be more suited to a category extensions type of page - in an effort to maintain the simplistic choices of the main leaderboards for new runners to not be overwhelmed by too many choices. The category extension leaderboard shall be coming soon (TM).

Some of the aforementioned categories would also only be possible on some heists rather than all heists, which is complicated to do with speedrun.com's leaderboard settings. For example, "Maskless%" is impossible for 'Road Rage' as the game automatically forces you to mask up - however - speedrun.com's leaderboard settings would mean every individual level (even Road Rage) would have this category applied to them.

Another point of discussion was the decision about the seperation of PC/Console runners in order to provide each runner a leaderboard without feeling pressure from the other type of runner. Ultimately we decided against this as with co-op runs being possible cross-platform, it'd result in categories sometimes having PC/Console split, whilst others not having that split, which may be confusing for new runners. HOWEVER, runs can be filtered based on the platform it was performed on, allowing console runners to compare runs with other console runners.

Once again, leaderboards can always be changed - nothing is set in stone completely. So we can change things if the community need or desire arises. This post was meant to ensure clarity for why decisions were taken the way they were, and we hope you can appreciate our reasonings for these decisions.

If you have any questions about either the rules, or the next steps of the leaderboards, we're more than happy to answer - either here, or in the discord server: here.

Hello heisters!

The Payday 3 Leaderboard is currently planned to be locked until the 5th of October (2 weeks post-launch). This means you will not be able to submit any runs to the leaderboard until this grace period has ended.

The reasons for locking the leaderboard are rather simple:

1. Allows runners (and moderators) the chance to familiarise themselves with the game properly, and provide a stress free environment to enjoy the game for a short while post-release. 2. Allows the moderators to overcome some degree of teething pains that come with creating new categories and generalised rulesets, such as how runs should be timed.

We hope you understand, and greatly appreciate your patience!

And remember, keep those helmets popping ;)

• Pizza

I was wondering, if I had the mod "Returnable Masks, Patterns & Materials" active. Would this prevent a recording being valid? Or would I just need to show through the Beardlib tab that this is the only mod I have?

Mod: https://modworkshop.net/mydownloads.php?action=view_down&did=15940

Just food for thought, especially considering loading times can drastically vary between hardware limitations. I've noticed it myself transferring from my old laptop to my new MSI one.