Foxhole Dev Tracker

While there will likely be tweaks to those (e.g. we want to review the current Bunker meta at some point in the foreseeable future), I wouldn't expect a major overhaul anytime soon. We know the community has been patiently waiting for changes in other areas of the game like infantry gameplay so there's a good chance we'll see some movement there.

I'd answer this but I'd rather it be a surprise when you guys test this in the dev branch :)

No but that is a neat idea.

It wasn't necessarily deemed more important right now. Development is scheduled such that there are larger features like refreshing weather, shared Facilities, etc that need to be planned out far in advance. So it's not so much that we feel like right now is the most important time to work on weather, but its more that a weather refresh was in the queue for development for some time and we've finally reached the point now that it can be completed and released.

Now sometimes we do disrupt that queue of planned features to work on something more important, but we have to be careful to not be constantly doing this, otherwise no big feature will ever get completed. To put things into perspective, if we didn't have the capability to execute on longer term plans, Foxhole would still be a game made up of 3 hour matches in a single region with a hundred players rather than a persistent world with thousands.

However, in tandem to that queue of longer term planned out featur...

We'll be answering questions here for the next few hours. Update 57 specific questions will be prioritized. Thanks!

This update is fairly conservative and definitely smaller than 56. It's mostly what we said in the recent Devblog so I wouldn't expect any big surprises either way.

The next Devstream is on Tuesday, June 25th at 1PM ET. Join us on Twitch for a live preview of what's coming to Foxhole in Update 57 https://www.twitch.tv/foxholegame

In terms of what to expect, please see our recent devblog: ...

No worries! I mostly wanted to confirm so the correct information could be relayed to the dev team.

The dev branch environment was just never designed to handle this amount of traffic or this scale of battle. A few days ago we updated the configuration of the server to address an obvious issue that would cause this sort of problem under load on dev branch. However, today's test battle caused further problems with that configuration.

For context, the dev branch environment has about 5% the amount of server hardware as the Live shard and is made for 100-200 players spread out among lots of regions (which is the average amount of players usually in dev branch). When these sort of dense test battles occur, the dev branch shard gets stretched way beyond the capacity they are designed for which results in several problems including this one.

In the future, if these test battles are going to be done more regularly, we're just going to have to factor that into our dev branch setup.

Is this on the dev branch?