I threw potatoes into the back part of my yard without burying them or tending them in any way and they did quiet well. Ended up dying from a freeze, I think I will throw them more strategically next time.
True, because then it feels more intentional (+ the extra strategy). It was definitely a bit thrown together- atm I only ever use it when I need a bit of practice before playing codenames.
I made one where you play with the AI a few years back instead of AI v AI but never posted it anywhere if anyone wants to try, just updated it to gpt-4o-mini https://wordswithrobots.isotropic.us/
I more meant like now you can bot word or story type multiplayer games too e.g. if you were designing a codenames or a mafia style party game or something. 95% of the time though ya you are just doing basic AI logic, go towards objective, attack nearby enemies, avoid nearby danger, etc
>you just depend on everyone you know for play testing constantly
I had this problem, didn't figure out the solution till the end of the project- it's bots. Even bad bots are HUGELY important for multiplayer game development because now you can iterate every second instead of every week. I thought bots would be too hard to make for my game, but they really weren't as they don't even have to be good. With LLMs i'm fairly sure almost any type of game can be botted at this point too.
Wasn't aware of dnsmasq/pihole, I have a BIND9 configured to do it on my network and yeah its much nicer. I've seen people get bit by this all the time in college and still even now join projects with like weird hosts file usage. Instead of having 3 different systems for apple/ms/linux name resolution that don't interop the problem is better fixed higher up.
>Are there any good reasons to use a TLD like .internal for private-use applications, rather than just a regular gTLD like .com?
These local TLDs should IMO be used on all home routers, it fixes a lot of problems.
If you've ever plugged in e.g. a raspberry pi and been unable to "ping pi" it it's because there is no DNS mapping to it. There are cludges that Windows, Linux, and Macs use to get around this fact, but they only work in their own ecosystem, so you often can't see macs from e.g. windows, it's a total mess that leads confusing resolution behaviour, you end up having to look in the router page or hardcode the IP to reach a device which is just awful.
Home routers can simply assign pi into e.g. pi.home when doing dhcp. Then you can "ping pi" on all systems. It fixes everything- for that reason alone these reserved TLDs are, imo, useful. Unfortunately I've never seen a router do this, but here's hoping.
Mine takes 50ms, assuming wsl is hot (recorded screen and compared mouse click frame to window pop up frame). I think op should try a different wsl distro or a blank machine and compare differences. I have on access scanning off, performance on, Ubuntu wsl distro, and windows 10.