ZombieLawnGnome

There's definitely plenty to do. Why not sign up and update the pages yourself? So what if you don't understand wiki code. Just type it in there and one of us can clean up later.

The stated design intent is that they don't respawn. That wasn't true in previous builds - they did respawn. Haven't done any conclusive testing with the current version.

Bug report: I started a new sandbox game with no zombies because I am updating consumables information on the wiki like a madman. Because you cannot mouse over an item to get the infobox while paused, I would be constantly standing in one place and using hotkeys for unpausing for a few seconds to mouseover an item then re-pausing it. Then I might keep it paused for like an hour while I tweaked a template. When I would tab back into the game and set it to 1x time, the clock starts running like mad - about three hours a real time second. I would suddenly be ravenously hungry and suicidal and bored to death. If zombies had been on i'd likely be dead. Time seems to return to normal at about the place it would have been if I had been running the game the whole time. Will do more thorough testing tomorrow to help narrow down the criteria of the bug. Also semi related - book reading times are bugged if you accelerate the time to 3x. It nearly instantly completes but only about 20 minutes game time elapses. Seems to cause increased frequency of time warps when this happens.

We're all tryin'. It's for the love of the game.

In the end RJ and TIS can do what they want with my suggestion, it was unasked for advice and I won't be hurt if it's treated as such. Your post however labels it as a 'bad idea' but for reasons that entirely confuse me. It's so baffling that I'm not sure you read my post carefully. Or perhaps you aren't that familiar with the concepts of the programming philosophy referred to as 'agile' programming? Increasing rigidity is the exactly what it's designed to STOP. Your post seems like it you think that it would increase rigidity and thus stifle flexibility and creativity. That's why I'm baffled. Pretend that you took the time to make a long post about an idea to improve how people drive that included suggestions how to increase the fuel-efficiency of your car. Then someone came along and made a short post saying "Nice idea, but cars need to be more fuel-efficient, not use more gas." I would think you'd be a bit baffled, and maybe a bit upset that someone essentially said your idea was a bad one for a reason that didn't even make sense to you. Edit: Kirrus called me on the tone of the original version of this post, and while I feel that the core content was valid, it was packaged in a harsh way that failed TIS forum rule number one: 'Be lovely.' My apologies to Simon816.

Hey RJ, what about instead of ETAs, you borrow (and slightly adapt) a concept from agile programming methods and do this: Look at the stack of bugs/featuers/stuff to be done Decide on a short list of things you are going to work on for the next mini-release (and don't add anything to them once decided.) Post those things you plan on working on. Mark them off as you do them (or cancel them if they can't be done in this iteration) Release the mini-version when done. Start over at step one. This is just a thought. At least there would be no ETAs. There would be just a list of things to do before release, and people could see progress towards the next release without any ETAs. If features are being kept secret you don't have to share them publicly, just write 'part of a cool new surprise' or omit them from the public list. It would help with communications with us fans. If your list looked like: Things for the next release: 1. Fix a problem with the wall in building X. 2. Fix a problem with Ham not rotting like it should. 3. Add in a new kind of item. 4. Fix problem with some new moodle. And someone asked "when will the new version be released?" You can just say "I'm having problems figuring out why the wall in this building lets you see through it. When that is done, I will release. Maybe you could help me by doing X, Y, and Z to test out the problem? Then I could release faster." You'd be both giving a helpful answer to everyone who reads your post and either getting someone to help you do useful testing or shutting them up if all they're doing is whining and not helping. I wish I could write French better, because I know English is your second language and I wrote a long and technical post, but the limited French I can speak isn't enough to have a meaningful technical conversation. As a separate light and funny thought, since English isn't your first language: We are referred to as 'fans.' That term is a shortened form of the original term 'fanatic' which is defined as: 'someone filled with extreme, obsessive, or single-minded zeal' Some other words with similar meaning are 'radical,' 'extremist,' and 'maniac.' Fondamentalement, nous sommes folles.

You know what ? That's a really great idea.... But I think the guys who don't like my grammar will don't like it too... If they don't like it, "Qu'ils mangent de la brioche." http://en.wikipedia.org/wiki/Let_them_eat_cake