It worked great for me years ago, but all the US-based banks I use have since killed off their OFX Direct Connect programs.
It worked great for me years ago, but all the US-based banks I use have since killed off their OFX Direct Connect programs.
I love how distinctive the art style is, but also how the gameplay rewards you for paying attention to the world and design.
Personally my peak VR experience has been playing the Outer Wilds with a PC VR mod, but very hardware dependent to get decent framerates.
Wanderer might be a good option for you if you’re looking for a puzzle game with a bit more story meat to it.
I think a lot of VR games end up short and sweet not just for technical & cost limitations but because the extra effort and intensity of the VR experience means players can get burnt out on longer story focused games. I remember Valve talking about how they had to really change up the pacing of their standard formula when they were developing Half Life: Alyx.


So obviously this is a very confrontational post, but tone aside, I kind of get it. I think it’s good that the author is up front and has made an explicit decision that they don’t want to put in the effort to build a public community around their software. They’re providing it as-is as a service to the public and they even indicate that they are open to other groups forking and putting the work into building a community. And crucially I’m not seeing an expectation that the community contributes back. I don’t think there is anything wrong in deciding where your interests and limits are, and I’ve seen other open-source projects die or rot when the maintainer runs out of time or loses interest, but without this being clearly communicated.
I agree with you that I personally wouldn’t try to contribute to a project like this since I also have no interest in building a community myself, but at least the project is up-front and clear about all this.
Feels like everyone I know has eventually ended up with their own copy. Hands down my favorite coop board game - it does a good job of minimizing the problem where one person effectively ends up playing for the whole table. Plus as you said the flavor is great.
Luckily you can turn it off and use the standard ‘add’ workflow. I did that almost reflexively when I started trying to use jj. (snapshot.auto-track)
However, over time, and once I got the .gitignore fully set up for bigger projects, I’ve come around on re-enabling autocommit for more of my repos. It does flow pretty naturally once you have an established process. I find it enables both better ‘undo’, and more seamless context-switching.
You can also set a more specific snapshot.auto-track on a repo or user basis for personal tooling conventions that don’t make sense to gitignore.