For anyone not familiar with this game, or anyone who’s only familiarity is through the trailers (which really focus on tone and visuals), I really want to recommend the videos by YouTuber Riloe, who has been playing early builds with the devs and chatting to them extensively about the game. They’re really well produced videos, and they really help to explain the tone of the game, the interesting mechanical ideas behind it, and what exactly this company is trying to achieve. Obviously, take with a grain of salt, the guy is clearly a fan and these videos aren’t really trying to be critical, so this should all be read as basically press releases;

This antishooter game is beautiful and horrifying

The living war ecosystem where you don’t matter

The beautifully dark warscape of the antishooter

I’m really excited for this game. Not just for the visuals, but for everything they’re doing with the mechanical design. The idea of playing as scavengers trapped between two warring factions is incredibly cool, and based on early previews it sounds like there are a lot of very clever design elements, especially in the AI, all built to back up that core idea. For example enemies intelligently prioritize targets; a tank won’t focus on infantry if there’s an enemy tank present, and even when it does target the infantry it’ll use its machine guns, not the main cannon. Enemies will focus on you if you make yourself the biggest threat, but if you’re smart and follow the flow of battle you can keep their focus elsewhere.

That’s really smart stuff, and by all accounts it works very well. I also really like what the studio is doing more broadly. They’re really trying to push back on a lot of the toxic practices in the gaming industry. I’ll be getting the game day one, mostly just to reward them for trying to do something different.

The reasonable way to approach this problem would have been to ask a follow up question, rather than bitching at someone for not answer in the exact format you required. You’re the beggar here, you get zero fucking say in how much or how little people choose to help you.

Yeah, Saber basically bought themselves back from Embracer (Embracer are desperate for money after they absolutely fucked an investment deal), and in the process bought back a bunch of other companies, including New World Interactive (Insurgency devs) and 3D Realms. They also have an outstanding option to buy 4A and Zen Studios.

No microtransactions

Saber off to a good start after getting themselves out of Embracer. I hope this pays off for them. The game looks great and I’m excited to play it.

Yeah, the immediate problem with comparing gun to non-gun kills is that anything involving a gun is automatically more likely to result in someone dead. So it doesn’t really give you a picture of how Indy likes to approach problems. And once a gun does become the tool of choice in a scene, the body count is likely to rack up a lot faster. You can show five people getting gunned down much faster than you can show one Nazi getting his head propellered off. Guns tend to be how disposable mooks die, but signature enemies get the more elaborate deaths.

Super excited to try this out. Darktide has taken over from Vermintide for my normal play, but getting to play as a Skaven sounds fucking awesome.

That lack of variety would absolutely suck if you’re not super into the specific gameplay it does offer. SAO would have a very small player base, because you’d never pull in those players who like support or backline roles.

Very different to the games that came after it, and probably the actual inspiration for SAO in the show. The whole thing about players speccing into crafting or whatever and then setting up their own shop was a really big thing on UO servers. Players would literally build entire towns together, and then fill them with shops that they would run. There was a huge part of the player base that were basically civilians, kind of like Arma modern life roleplay servers.

Also, for the record… It’s still running, somehow.

Actually the closest thing in terms of the classless skill system would be pretty much the granddaddy of all MMOs, Ultima Online.

Also, only melee builds. No ranged, no magic, no healers, no support. Everyone is either tank or DPS, that’s it.

New Raycevick video? Fuck yeah!

I love Marathon. I am obsessed with Marathon. Durandal has a goddamn four story mansion, condo and summer home in my head, all rent free.

I have zero interest in this game.

There’s no backend server to do the transcoding in this case. Kodi can access raw NFS/SMB file shares the same as accessing local storage, so it’s just reading the file over the network, the same as if you were playing it in VLC on your PC.

Certain domain names are locally routed only. So if you use internal or local as a tld, you can just assign whatever names you want and your computer won’t go looking out on the internet for them. This means you and I can both have fileserver.local as an address on our respective network without conflicting. It’s the URI equivalent of 192.168.0.0/16.

I’ll see about digging up recommendations if I can, but I’m on my phone right now.

My biggest single piece of advice would be this: Understand that your reader does not share your context.

What this means is that you have to question your assumptions. Ask yourself, is this something everyone knows, or something only I know? Is this something that’s an accepted standard, or is it simply my personal default? If it is an accepted standard, how widely can I assume that accepted standard is known?

A really common example of this in self-hosting is poorly documented Docker instructions. A lot of projects suffer from either a lack of instructions for Docker deployment, because they assume that anyone deploying the project has spent 200 hours learning the specifics of chroot and namespaces and can build their own OCI runtime from scratch, or needlessly precise Docker instructions built around one hyper-specific deployment method that completely break when you try to use them in a slightly different context.

A particularly important element of this is explaining the choices you’re making as you make them. For example a lot of self-hosted projects will include a compose file, but will refuse to in any way discuss what elements are required, and what elements are customisable. Someone who knows enough about Docker, and has lots of other detailed knowledge about the Linux file system, networking, etc, can generally puzzle it out for themselves, but most people aren’t going to be coming in with that kind of knowledge. The problem is that programmers do have that knowledge, and as the Xkcd comic says, even when they try to compensate for it they still vastly overestimate how much everyone else knows.

OK, I said I’d try for examples later, but while writing this one did come to mind. Haugene’s transmission-openvpn container implementation has absolutely incredible documentation. Like, this is top tier, absolutely how to do it; https://haugene.github.io/docker-transmission-openvpn/

Starts off with a section that every doc should include; what this does and how it does it. Then goes into specific steps, with, wonder of wonders, notes on what assumptions they’ve made and what things you might want to change. And then, most importantly, detailed instructions on every single configuration option, what it does, and how to set it correctly, including a written example for every single option. Absolutely beautiful. Making docs like this is more work, for sure, but it makes your project - even something like this that’s just implementing other people’s apps in a container - a thousand times more usable.

(I’ve focused on docker in all my examples here, but all of this applies to non-containerized apps too)

I write technical documentation and training materials as part of my job, and the state of most open source documentation makes me want to stab people with an ice pick.

Xpipe has rapidly become an essential part of my day to day workflow. I wish I could get it to play nice with MobaXTerm as I prefer that to any of the supported terminals, but that’s really my only gripe. In every other regard it’s just an excellent toolkit for managing remote devices.

It’s not so much that Dockge shows more, and more that it does more. Log viewing in Dockge is actually pretty bad; it’s honestly the one thing that really needs more work. But Dockge is a full management plane; it allows you to deploy, modify, bring up and bring down entire compose stacks. Dozzle is only a log viewer, nothing else. Given that log viewing is the one thing Dockge does badly, they’re actually a perfect complement to each other, and I’d strongly recommend running both.

OK, so right now you’re mounting the remote shares as user moose, but then you tried to chown those folders to user $USER. In case you don’t know this, the $ sign indicates a variable; the command is actually subbing in the name of the user who ran the command.

Now the question here is, what user is radarr / sonarr running under? If you’re running them directly on your machine without docker, that’s probably being set by a systemd task that runs the programs in startup.

You need to make sure that that user has the ability to write to those media folders. The simplest way to do this would probably be to edit the systemd units to run the arr programs as moose, since that’s apparently an unprivileged user you created just for mounting the shares.