This helps, thanks for the insight. I've brushed up on the laws in my state, which aren't as generous as yours. I'll do a little more reading before I decide, but it appears that all the benefits/drawbacks revolve around getting sued.

A year ago I researched this topic for a static website of my own. All providers I looked at were $5 and I want to say the cheapest I found was slightly lower. By comparison, I am still within free tier limits of AWS S3 and cloudfront (CDN) since I am not getting much traffic. So my website is on edge locations all over the world as part of their CDN for free, but if I host on a single server in Ohio it costs $5/month.

Did you check NearlyFreeSpeech.net? If you are getting little traffic it costs practically nothing for a static site.

An idle site that receives no hits still costs around $1.50/month with NearlyFreeSpeech.net since the change that limits the number of "non-production" sites that was instituted from around the time when Cloudflare decided to kick out the white supremacists.

Thank you! That did not come up in my search, but it looks great and is reasonably priced. I may use that for another project.

Very cool! What engine/tech stack did you use to write the games themselves?

The frontend is written in Typescript/React (Vite) and the backend is Java + Spring Boot + Redis + Postgres. I'm using WebSockets for interactivity.

I will try this out at work this week. I guess I don't know what I've been missing since I never seriously dove into react or vue. I rely on having my breakpoints hit for debugging, which works pretty well, but when I hear that something could make me a faster developer, I am all ears! It's also great to see more devs investing in Blazor.

I have some bugs to report:

The marker-injection broke on a foreach loop because it began with @ directly under the @inject. I added an html element between them to fix this.

```

@inject IJSRuntime JSRuntime;

@foreach(var item in MyCollection)

@* Injected by BlazorDeveloperTools (Dev-only) - Open *@

<span ... ></span>

{

    // Code and markers look correct here

}

```

I also get the error: "MyComponent.razor.js was defined but no associated razor component was found for it" when trying to build, so I had to temporarily delete that js file.

I used BdtSkipComponents a few times to get it to build, so - probably as a cascading effect - some components that show up on the tree do not have the correct name when using the hover tool. Instead it's the name of the root component.

When the page loads I see "} else {" and other curly braces that aren't supposed to be on my page.

When I open the extension and click on the component tree, the purple boxes never disappear, so I have to reload the page.

Now onto the good news: The render tree is correct and I'm able to hover over most components and see what their name is - nicely done! I'm interested to watch as your project develops. Thanks again for helping out the blazor community.

To answer your question in OP, what I most struggle to debug is the Blazor lifecycle. For example, sometimes OnParametersSetAsync gets triggered an awful lot when I don't expect it to, and that takes quite a bit of my time to find the trigger and sort it out.