As some who has played maybe 30-50% of DOS1+2 and currently the first of three acts in BG3: If you have issues with the gameplay mechanics in DOS1/2 you’ll likely have them in BG3 too. Main difference is a vastly improved storyline, which kinda makes up for most of them.

Issues I still have with BG3 boils down to only the active character can use its abilities in conversations and sometimes (mechanically) unexpected stuff happens that can only be undone by saves.

If your issue with DOS was a boring story and lack of hidden/funny things to uncover you should give BG3 a try, if you disliked the overall experience you likely won’t enjoy BG3.

That’s what I meant, using your shell to run command line tools to solve your issue at hand. And having a powerful shell with e.g. context dependend autocomplete (and a lot more) helps to speed up that task.

You can do most things by combining simple cmdline tools. E.g. filter out some specific lines from all files in a directory, get the value after the second :, write those to another file and then sort, deduplicate and count them.

This may sound complicated, but it’s pretty easy and fast if your are familiar with a shell. To be that efficient with your shell you want it to actually be powerful and not just a plain text input. Also writing cmdline tools is rather easy compared to a usable GUI tool.

Some (larger) projects sometimes have a form of mentoring and “good first issue” to get started.

Another good way to get involved is to report any issues you face with open source projects you use (obviously search for similar reports first). This way you can help debug bugs or suggest improvements and get some feedback.

Are you sure this is not just a normal community with the instance name?

For me this post is coming from c/lemmyworld. I’m on another instance and there is no community with the same name, nor was I subscribed to any.