@xvapx, thanks for your PR! By analyzing the history of the files in this pull request, we identified @edolstra, @rycee and @abbradar to be potential reviewers.

Looks good to me, merging

Thank you very much for this documentation!

Several nitpicks (nothing major which prevents merging this):

1. What did you mean by "game cannot be started because it cannot be patched"? FHS environments don't patch the games, instead they try to emulate the surroundings;
2. Java can be enabled by steam.override { withJava = true; }; probably we want to just add it to the environment unconditionally, like Mono already...

1. I think it's mostly the content that was on the wiki. I suppose it meant usage of patchelf.

Yes, it is the info that was on the wiki, it means that binaries cannot be patched to not depend on a FHS environment because they are checked, i can update the doc to make it clearer and add the java override.
Thank you!

No problem; if you don't have enough time I can update the documentation by myself (I have been postponing it for far too long already).

Maybe we want to just drop the section about running the games with patchelf completely? This most likely won't get anyone better results than FHS. BTW, I also plan to document steam.run as a way to run stand-alone games.

Well, i have time today and i don't mind one way or the other, so as you prefer.

I won't have any till the mid-week, so if you want to go forward please! ~_^

Ok, i'm on it.

Is there any doc anywhere about the steam.run way? i'm finding nothing about it.

I didn't know steam-run. I wanted to run a stand-alone game recently and used buildFHSUserEnv directly. In this case just three packages were required...

@xvapx Nope, and that's the problem.

Quick informal introduction: steam-run lets you run applications as if they were run inside of Steam, in FHS and with its runtime (that's what games usually expect). You can install steam.run and then do steam-run ./foo.

In my personal experience, it works way better when runtime is composed of native NixOS libraries (unlike Steam, which works way better with vanilla Runtime). You get it like this:

        (steam.override {
          nativeOnly = true;
          newStdcpp = true;
        }).run

@vcunat PoE runs nicely with it ^_^.

Ok, thanks a lot!

Looking back, the only my mention of steam-run that I can find is the original pull request. I should be ashamed for not documenting that earlier D:

Well, it was clear enough in the PR, but i have been unable to find it until you pointed me. I just finished adding it, will PR in a moment.
Tell me if there is any other info you want there or any other change.
Thanks!

#21059

PoE runs nicely with it ^_^.

I used to have problems with direct usage of steam* stuff, due to my unusual mounting setup of $HOME, but now I see it does work again with the current code :-)