I'm having an issue running this game on linux, every time I click play in Steam I get the following popup:

Clicking "yes" takes me to download a Windows .exe which of course can't run on linux. I manually installed the .NET runtime following linux instructions here: https://learn.microsoft.com/en-us/dotnet/core/install/linux-debian but the game still gives me this error.

Other things I've tried:

• Reinstalling BG3
• Completely deleting every file from steamapps/common for BG3 & reinstalling
• Reinstalling Proton

On protondb everybody else seems to be running the game fine, but I don't understand how to get past this error.

Designers can create stunning designs, interactive prototypes, and design systems at scale, while developers enjoy ready-to-use code and make their workflow easy and fast.

Designed for developers

Penpot was built to serve both designers and developers and create a fluid design-code process. You have the choice to enjoy real-time collaboration or play "solo".

Inspect mode

Work with ready-to-use code and make your workflow easy and fast. The inspect tab gives instant access to SVG, CSS and HTML code.

Self host your own instance

Provide your team or organization with a completely owned collaborative design tool. Use Penpot's cloud service or deploy your own Penpot server.

Integrations

Penpot offers integration into the development toolchain, thanks to its support for webhooks and an API accessible through access tokens.

Self hosting instructions (via docker) can be found here: https://help.penpot.app/technical-guide/getting-started/#install-with-docker

The goal of Fireshare is to provide a very simple and easy way for you to share any videos you have through a unique link.

Demo website: https://v.fireshare.net

Spacebar is a free, opensource selfhostable discord-compatible chat, voice and video platform.

• Discord-compatible (Use all your custom clients/bots with minimal changes)
• Selfhostable (Server)
• Open Source (GitHub Organization)
• Configurable (Configure every aspect and limits to your needs)
• Decentralized (no abuse of power and doesn't have a single point of failure)
• Extendable (secure and cross-platform plugin system)
• Themeable (cross-platform theme system with design editor)
• Secure (publicly audited and hosted FOSS software for transparent foundation in terms of security)

On June 29, 2024, at 6:30 P.M. Pacific Time, Roll20 learned that an administrative account was compromised. By 7:30 P.M. Pacific Time, we acted to ensure that all unauthorized access was blocked, and we began the process of investigating the incident to determine the scope.

Following our investigation, we learned that the unauthorized third-party had access to administrative tools, which may have resulted in the exposure of personal information, such as your: first and last name, email address, last known IP address, and the last 4 digits of your credit card (solely if you had a stored payment with us).

Notably, the compromised administrative tooling did not expose your password or your full payment information, such as your address or credit card number.

While we have no reason to believe that your personal information has been misused, we are notifying you out of an abundance of caution.

We take your privacy and security very seriously, and we deeply regret that this incident occurred. We will be implementing an action plan to further enhance the security of our administrative tools going forward.

If you have questions, or if you would like to view a copy of your account data that the third party may have had access to, please reach out to us at https://help.roll20.net and create a support ticket with the subject line “Incident Data Request” and we will be happy to assist you.

Here are some resources containing good best practices for protecting your information online which we recommend: https://consumer.ftc.gov/online-security

Wanted some opinions on ways to set up triggering "on-kill" effects. In short: The player can have abilities that trigger effects whenever they shoot and kill an enemy. I'm also looking to extend abilities to enemies as well, so can't just hardcode a player reference.

Currently I'm doing it like this:

• Enemy signals that it died -> the bullet receives this and signals that it killed Enemy -> the player's weapon receives this and signals that it's bullet killed Enemy -> the player receives this and triggers it's on-kill abilities.

It simultaneously feels like a good way to go about it but also a long mess. The other option I've considered is:

• Each bullet has a reference to it's owner (eg. player). When an enemy dies to a bullet, it looks to the bullet's owner reference and tells it to trigger it's on-kill effects.

This way is a lot simpler to write, but is error prone eg. In cases where the bullet's owner is killed while their attack is mid-air.

Thank you all!

Figured I'd share this project as I don't see many that know about it! (Only available for Windows)

For those that have never heard of it, PlanarAlly is an open-source self-hosted virtual tabletop (VTT) for TTRPG games. Here I've compiled the most important features/changes from their blog post. The full release notes are available on their GitHub: https://github.com/Kruptein/PlanarAlly/releases/tag/2024.1

Vision Blocking Update

A new vision blocking mode is introduced, called behind. It will accompany the existing vision mode which will be renamed to complete.

When behind mode is active, the shape marked as vision blocking will be rendered as if it’s not a vision blocking shape, but everything behind it will be fully obscured. This will for example allow you to have a tree trunk that is vision blocking, but still show the players what they are looking at (i.e. a tree trunk).

Notes Overhaul

There is no longer a difference between shape notes and campaign notes. Notes are now a single concept, can be attached to shapes and managed through a new UI element called the Note Manager.

It’s now possible to share certain notes to other users with granular access rights, eg. you can give view access to all players when they retrieve an item, or give a particular player a private note that only they can view and edit.

For a full overview of the new note system, check the notes documentation.

Asset Drop Ratio

Defines how assets should be scaled when dropped on the map. A drop ratio of 1 is the default, it means the asset will resize purely on it’s specified dimensions, eg. goblin_1x1 will take up 1 grid cell even if it represents 10ft, whereas a drop ratio of 0.5 will resize basilisk_2x2 to 1x1.

Context: Previously, assets would auto scale when dropped onto the grid if they have a dimension in their name, eg. goblin_1x1 would fit exactly 1 grid cell, dragon_3x3 would be resized to 3 by 3 grid cells. This was using a method based on the 5ft-system to automatically adjust this when a location had a bigger size (eg. 10ft maps would automatically make goblin_2x2 fit in 1 cell). This however would break anything that wasn't using the 5ft-system.

Dice History Improvements

The dice history will now show who rolled the dice (it was previously only shown on hover) and contains more details on the specific roll instead of only showing the final result.

I accidentally summoned my freighter at a weird angle, so from the ground it looked like it was crashing down to the planet. I thought it made a pretty cool shot though! Here's some other angles: