Piatro

Hopefully the title is self-explanatory but some more details:

• game is in isometric perspective with the camera locked to the player but from a significant distance away, creating high likelihood of obstructions by the level and decorations occuring
• I want the player to see their character's vision and not have these obstructions block the player's view.

One way to achieve this might be to use raycasts from the character to hide objects (like walls or buildings) if they collide with an object on the opposite side to the camera. A slight problem there is if buildings have interiors then the rays wouldn't necessarily hit all relevant objects. Sometimes both the interior and exterior of the building would need to visible.

I've seen a few videos on stencil buffers but my understanding is that this might not apply, but I will admit to not understanding them well. Any help appreciated for this newbie to game dev.

Hi all, my trusty (but honestly always pretty terrible) Amazon basics tripod finally died, does anyone have a tripod they'd recommend or brands they'd avoid?

Typical usage for me would be travelling/hiking and landscape photography so ideally small and light without breaking the bank (which I know is pretty tough). Budget is variable but call it £100-£200 for now.

It's being rolled out in stages so you, like me, may not have it yet.

Title. Friend group and I play regularly but most of us are bad at the role playing part of it to the point where it's hard to tell when the player or the character are speaking in some scenes. Conversations are stiff. We can't use too heavily modified voices because we're playing remotely. My character is about to die (probably!) so help me pick a character or trait of my new character that someone not comfortable roleplaying can stick to without feeling weird about it!

What do you have, what do you recommend, and why?

Asking as I've got a lot of spare components lying around that I'm planning on turning into a NAS. If it doesn't work out I'll buy a pre-built enclosure and reuse the drives.

EDIT: Issue now resolved. Turns out that having an A record point to a DNS server probably wasn't the best idea. My best theory here is that A records pointing to DNS servers means "Find the authority on this domain at this other DNS server", which could never resolve. By pointing it to my VPS, the DNS could resolve to a definitive IP, and the certs were successfully generated.

Hi all, hope someone can help as I'm just confused now!

Long story short I want to host local services (like ntfy) using trusted certificates. I hoped to do this with Caddy and a wildcard domain (I don't want to expose the DNS records of the services I'm running if not necessary).

In my DNS I have an A record for *.local.example.com pointing at a semi-random IP. I have other services on a VPS on other subdomains so I can't just use a wildcard. This looks like:

blog  A  <VPS IP>
*.local  A  1.1.1.1

On the server in my home network (which I do not want to expose) I have dnsmasq running that is handling local DNS records for services on the LAN but carefully not the remote services on the same domain. Using dig I can see that the local and remote DNS are working as expected. Seeing the error on DNS-01 challenged "could not determine zone for domain "_acme-challenge.local.example.com" I have also added an exception in my local DNS for _acme-challenge.local to point to cloudflare's DNS at 1.1.1.1. The dig command confirms this works as expected after restarting dnsmasq.

With the following Caddyfile:

*.local.example.com {
        tls {
                dns <dns provider plugin> <API token>
        }

        @ntfy host ntfy.local.example.com
        handle @ntfy {
                reverse_proxy ntfy
        }
}

Every DNS-01 challenge fails with "...solving challenges: presenting for challenge: could not determine zone for domain "_acme-challenge.local.example.com"...".

I think this should be possible, but I'm not clear what I'm missing so any help greatly appreciated. I'm just dipping my toes into self-hosting and actually getting practical use out of my Raspberry Pi that's been collecting dust for years.

Not affiliated I just find this useful and it exposed me to a few of the new features of Ruby 3.2 like not having to specify the value in kwargs if the variable is defined in scope, eg:

foo = 'bar'; call(foo:) is equivalent to foo = 'bar'; call(foo: foo)