PJSleaze

You completely missed the point of my comment. The "unscathed" have turned out to be just as violent as the zombies in my experience.

Yeah, but if you collect them all, you can feed everyone on the server with one can of tuna and a box of Crunchin Crisps.

If we assume Chernarus follows sunset times for Czech Republic, based on the map we've seen- Sunsets in October shift from around 17:50 to 16:50 once daylight savings ends. I'm assuming it's fall based on foliage, so this seems reasonable enough.

I know, right? I thought it was spam at first. I'm fighting the compulsion to tell the OP that his title is referring to his mom. Yup. Fighting it.

Maybe it's trying to tell you something?

It's been a month and 11 days, not 2 months. Use facts. Enlighten me as to how this is a simple patch?

Otherwise known as "Florida"

You eat very loudly and without stopping until you've eaten 25% of your meal. You do this until you are done.

Here's the thing. Shit breaks when you add new code. Things that no one expects to break, too, no matter how hard you try to vet it out and prevent it from happening. It happens all the time, even with large software companies. Then it takes time to figure out why. Then it takes time to re-write code to fix it. Then it takes time to test that you didn't break something else by fixing that one thing. And then you find out that you probably did break something else and then you're figuring out why that broke, and on and on you go. It's not rocket science, but it's complex enough and time consuming enough to work through this stuff, especially in early stage development when you're constantly adding new features. It's been, what? A month and a bit since the last stable release? I wish the devs I worked with were that quick. So, call me an apologist, but I've seen this process and know how ugly it can be. I also see comments about "They got their money and now they don't care". This is ludicrous to me. Most of the guys working on this aren't going to make millions. They have to find another job when this is done. It's a lot easier to do that when you're associated with a successful project than a shitty one where everyone gave up and wasted a ton of money. Especially if it's a very public project like this one. People are motivated to put out a good product, because their next job is riding on it.

You're overstating our role in the process if you think the posts here have an impact on their schedule. "An excuse to drag things out". What, you don't think these guys want this to be done? Actually making things stable before moving them to stable can take time, but is worth the effort. But there's nothing our words can do about that.

I want to run with scissors! But seriously, the extra speed would make pistols more valuable to me.

Avoid if possible when in dangerous areas. Killing them can make noise and draw attention. Leaving them standing there creates false sense of security in other players. If they go aggro, use an axe only- gunfire near bases and big cities is bad news. Run of the mill towns? Axe to face. Empty server, no one around? Target practice.

200+ people isn't a mistake, but it's a very different approach. It's also a shit ton of overhead. How many of them are coders and how many are PMs? Nothing against PMs (I do my share of it) but we cost money without adding a ton of direct value, but you need a lot of them when the team gets large to keep things moving, and it's still not going to guarantee success. $30m won't go far at all with a team like that. 1 year or so?As for approach, It is very, very hard to be responsive to changes with a huge team. Requirements need to be nailed down very early so that everyone is aligned. One change in one group can impact another, slowing them down or creating bugs; changes are frowned upon in this type of development environment and flexibility is lost, even with good management. I've seen this happen. These are complex problems. The Taj Mahal crew had a singular goal that probably didn't change much from initial plans. And they had unlimited funds. Large crew was appropriate, and it's not a good comp to a software project that is getting community input as they code. If you're trying to be flexible, which seems to be the case here, it's easier with a smaller team. Trust me.

You can find laxatives in some of the houses and in the jail cell. You can store them in the first aid lot too.

I've worked for large companies and small companies. Managing a project with a large team can be great, but you can't be very agile. You have to have pretty rigid plans to keep everything productive. You can't adapt easily to change. Small teams can. If They're serious about adapting the game as they go, 30 people sounds about right. 200 would make that impossible.