Valve deleted the Minecraft Dungeons II workarounds, then allowed one back 28 hours later

Valve deleted the Minecraft Dungeons II workarounds, then allowed one back 28 hours later

Valve spent two days deleting the community workarounds that owners were posting under Minecraft Dungeons II on its own Proton issue tracker, calling them "legally problematic", and then reversed itself on one of them 28 hours after the first removal. The reversal, posted at 17:39 UTC on September 30, reads: "it is no longer taboo to use here in discussion."

A Steam Deck showing the SteamOS library screen

A Steam Deck on a dark background showing the SteamOS home screen, with Cocoon featured above a What's New row. Image: Valve

Both sets of words come from the same thread and from the same account, kisak-valve, which GitHub marks with the author association MEMBER on Valve's repositories. That is what makes the comments quotable as Valve's own moderation of its own tracker rather than one user telling another off.

Five interventions in two days

The first came at 13:34 UTC on September 29, hours after the game launched and the compatibility report was opened. It set out the rule plainly: "third party redistribution of copywritten libraries is legally problematic and can not be tolerated", and said links posted by three named accounts had been removed along with the reposts.

A second followed at 17:58 UTC the same day, this time about a third-party build of Proton: "Unfortunately, I have to be the bad guy here. A third party build of Proton which was mentioned many times here is legally problematic and needed to be removed. I tried to preserve as much of the prior discussion as possible, but some comments unavoidably got removed."

Two more removals followed, at 21:05 UTC on September 29 and 12:31 UTC on September 30, each with the same short formula about a workaround being "legally problematic" and removed. A fifth comment, at 13:52 UTC on September 30, warned one contributor that the material "can not be posted here (directly or indirectly)" and that continuing would force action.

Then one of them came back

The turn came three hours and 46 minutes after that warning. Valve's member wrote that a contributor had "made an important change to your workaround scripting and because of that, as of right now, it is no longer taboo to use here in discussion", and immediately narrowed it: "I can't endorse or encourage the use of any specific workarounds, but in this specific case, it can be mentioned from this point forward."

So the objection was never to workarounds as a category. The reason Valve gave every time was third-party redistribution of copyrighted libraries, and a change to one contributor's scripting was enough for that workaround to become discussable again. Twenty-eight hours and five minutes separate the first removal from the line that allowed it.

What this does not establish

The MEMBER label places the account inside Valve's GitHub organisation. It does not give a job title, and the comments should be read as Valve moderating its tracker, not as a Valve developer describing engineering work. Neither the removed build nor any of the workarounds is named here, and neither is any of the contributors whose comments went.

Nothing in the thread commits Valve to anything either. Owners asked whether Proton would learn to satisfy Microsoft's Gaming Services requirement, and no reply from Valve answers that, which leaves the compatibility report open. It is also not the first SteamOS block the site has covered: For Honor stopped running on Steam Deck and Steam Machine in late September, for unrelated reasons.

What owners are left with is a tracker that now permits a conversation it deleted a day earlier, and a game that still does not start.

Leave a Comment

Your email address will not be published. Required fields are marked *