Holy carp that's too much version string right there

Basically Proton-i 4.13-3, and

• "Are You Ready for Valve Index?" patch by ryao,
• a Harry Potter fanfic e-book from Valve, or whatever the heck this thing is.

This time there's no short howto or anything because

• no

Also

• mostly fulfilling a request for a Harry Potter fanfic e-book build for someone.

Proton-i 4.13-3 OFFICIAL CHEAP KNOCK-OFF

Good Morning to You Dear Sir/Madam

Proton-i, codenamed "I Can't Believe It's Not Proton!", is here.

• This fork has been renamed to Proton-i to prevent any future name clashes with upstream releases.
• Rebased Proton 4.11-2 patches on top of Wine 4.13.
• Fixed a bug in one Proton patch where the loader lock might not be released properly. No idea if this bug actually caused trouble anywhere.
• Replaced the reverting of upstream Wine commit d54108707 with cherry-picked upstream commit ef542fc79.
• Mostly identical to Proton 4.11-2. Wine has been upgraded and some light bugfixing has been applied, but all other components are the same.
• Built with the same virtual machine setup Valve uses for its production builds (see README.md.)

Might I Interest You in Our Fine Selection of Stuffed Birds

• Exit the Steam client.
• Create a directory called compatibilitytools.d under your $STEAMDIR if it doesn't exist yet.
• Extract Proton-i-4.13-3.tar.xz inside $STEAMDIR/compatibilitytools.d/.
• Restart the Steam client.
• Select Proton-i 4.13-3 as the Steam Play compatibility tool on a per-game basis.

Proton 4.13-2 UNOFFICIAL

What

• Rebased Proton 4.11-1 patches on top of Wine 4.13.
• Reverted upstream Wine commit d541087 because it caused Squad to crash when double-clicking editable text in the in-game config menu.
• Otherwise identical to Proton 4.11-1. Only Wine has been upgraded, all other components are the same.
• Built with the same virtual machine setup Valve uses for its production builds (see README.md.)

How

• Exit the Steam client.
• Create a directory called compatibilitytools.d under your $STEAMDIR if it doesn't exist yet.
• Extract Proton-4.13-2.tar.xz inside $STEAMDIR/compatibilitytools.d/.
• Restart the Steam client.
• Select Proton-4.13-2 as the Steam Play compatibility tool on a per-game basis. I have seen claims that setting a custom compatibility tool as the global default could mess things up. I don't know if that's true, but I recommend erring on the side of caution.

Proton 4.12.1-1 UNOFFICIAL

What

• Rebased Proton 4.11-1 patches on top of Wine 4.12.1.
• Otherwise identical to Proton 4.11-1. Only Wine has been upgraded, all other components are the same.
• Built with the same virtual machine setup Valve uses for its production builds (see README.md.)

How

• Exit the Steam client.
• Create a directory called compatibilitytools.d under your $STEAMDIR if it doesn't exist yet.
• Extract Proton-4.12.1-1.tar.gz inside $STEAMDIR/compatibilitytools.d/.
• Restart the Steam client.
• Select Proton-4.12.1-1 as the Steam Play compatibility tool on a per-game basis. I have seen claims that setting a custom compatibility tool as the global default could mess things up. I don't know if that's true, but I recommend erring on the side of caution.

Why

• Yes