I submitted our entry for the #db2018 game jam with 11 minutes left to go. It's nowhere near as fleshed out as I was hoping it would be, but it's *functional*. Now I'm going to chill for the rest of the night and party in the DB chat. Maybe I'll come back to it this weekend to do more polish.

I kind of worry that the next Star Wars is going to capitulate to the tiny but extremely loud minority of people who think The Last Jedi is an "SJW wankfest garbage fire", and undo all of the (extremely good) work that Rian did trying to push the series outside of its comfort zone.

Especially since JJ is back in the director's chair. He knows how to make a good Star Wars movie, but TLJ was also basically a series of subversions to every mystery box that JJ set up in TFA. So.

Well, I've got a character controller started, and a camera that tracks the player as they move. Still a TON of stuff left to do, but I feel like some of the trickiest stuff is at least on the way to being dealt with. #db2018#gamedev#DesertBus#db2018gamejam

Now I just have to figure out what is causing this absurd connection-devouring retry logic. It's not in my code, and StatHat's c# class library just uses a raw WebRequest, which *shouldn't* do any kind of crazy eternal retry activity. Is it an Azure App Service quirk?

Well, in today's edition of bug-hunting rabbit holes, it turns out my intermittent webapp crashes aren't being *caused* by a failure to connect to SQL Azure. Failing to connect to SQL Azure is a symptom of an underlying issue. Namely, the app is exhausting available TCP/socket connections. For some reason, if a call to StatHat's API ever happens to fail, it gets stuck in a loop trying to talk to the endpoint until it consumes every available socket & gets blackholed by Azure's resource manager.

Follow friends and discover new ones. Publish anything you want: links, pictures, text, video. This server is run by the main developers of the Mastodon project. Everyone is welcome as long as you follow our code of conduct!