Ever since about the time of the "Unified Battle List" game performance has been sub-par. The ping and data rates are good to excellent - but the game performance has been glitchy. The past couple days the performance has been really bad - and today it was HORRIBLE. The game repeatedly misreports the positions of other units... that is, an enemy tank will appear to go left, then over a hill, then back to the top of the hill, then run in a circle then "teleport" to another location completely. It's almost as if someone cut up a movie of tanki and spliced the pieces of the movie back together in the wrong order and played it. And it's not just one tank. It's all of them. Damage displays are also significantly delayed. About the time you decide you missed and fix on a different target, the numbers pop up and the other tank explodes. Most of the time the games the past couple days have been like low-quality clay-mation. Like https://www.youtube.com/watch?v=LlpSPOWcyeM I've also noticed more incidents of the "gun doesn't work" bug. You know - you go into a battle, you keep hitting enemy tanks - no damage reported. The only way to "fix" the problem is to leave the game and re-enter. Of course, you lose crystals doing that. The buggy-ness and poor system response has reached the point of the games being basically unplayable. I suspect this is due to trying to cram too much onto a small number of servers - the servers can't handle the load. As for the bugs themselves... *sigh* I know it's against Tanki policy to actually TEST anything.

After about the 40th time that the devs screw up something that even a TINY bit of testing would have revealed, some might doubt your sincerity. In recent weeks, there was first the gold box mass drop where Tanki advertised we wouldn't believe how many golds would drop - containers started to pour out of the sky and people got all kinds of cools stuff - then Tanki took it all back. Then there was the "special site" that was supposed to count kills - that was poor design to begin with I mean, come ON! It didn't report kills under 400. It didn't update any faster than once per hour. And in the final analysis, it DIDN'T WORK! Now we've got another bug that wiped out mission results and the response is "So sorry. You're hosed. But we're really sorry"? Is it really too much to ask Tanki to at least consider TESTING software before putting it on line? Please, tell us all what changes you've made to your testing regimen to ensure that fewer bugs will make it on line. Really. I'm sure we'd all like to know how sincere Tanki is for dumping so many bugs on us. Oh, and in case no one's mentioned it yet - the servers are dead. Might want to check that.

Seriously, Tanki - do you guys ever test anything before it goes on line?

NIVES, Do Tanki devs ever test ANYTHING before they put it on line? If so, how could they mess up such a simple, basic function as COUNTING? That strikes me as a "Programming 101 for Music Majors" type of problem. You learn how to do it right after you learn how to code, "Hello World".

You should always worry. It's the Tanki way!

That would be the EASY way and the PROPER way to do it. Which is why Tanki doesn't do it that way. There's a harder way to do it which does not work. That's what they like! Seriously, why doesn't the web page show the current kill count? The current implementation is harder AND it's less useful. Is there some reason it was chose instead of just reporting the count?

Here's an idea: Why doesn't Tanki TEST software before releasing it? In the civilized world, software is tested by the developers. There's alpha-test, beta-test. And there's this really cool idea called QUALITY ASSURANCE, where an independent guy looks at the buggy code and tells the devs all the things they did wrong but are blind about. After all the bugs are worked out (to the best of their ability) the software is released! In the Tanki world, it's READY! FIRE! AIM! Apparently no testing - just shove it out and if it doesn't work - well, you don't mind having people quit, do you? And what's with half-hourly updates and only showing the number of kills after 400? Is it really so hard to update the database when a player leaves a game (whether in the middle of the game or at the end)? How would that work? Just make it a hook on tank reinitialization. You know "Save experience points. SAVE KILL COUNT. Finish initialization." In fact, you could display total kills for the weekend right on the person's main page - without needing a different "site". Am I going too fast for you? Good job! Agreed. I think the Tanki devs must not have been very interested in what they were doing. The Holiday map is just a two-tier wedding cake with trees around the edges and lots of drug drops. BOOOORRRRR-INNNNNNNG! But it does express the new Tanki philosophy quite well. See, with all the new maps, the common theme is Less Skill More Kill!! Just point your turret in a random direction, drug like hell and blast away. Can't drive? No problem! We'll make all the roads so wide you can't get stuck! Can't hit anyone? No problem!! We'll just cram so many people into every map, no matter where you shoot, you'll hit something! Now all you have to do is charge stuff on mommy's credit card and push the space bar. If you have TWIINS, you can put a brick on the space bar and leave for the day. The game will play itself!

Per usual, Tanki never gets anything right. The "Kill Board" stopped working for about the last 6 hours leaving people with no way to tell what their kill count was. Never mind that the count was only updated once per hour (instead of on demand). That was stupid design to begin with. But to compound it, you had failure - the stupid design they announced did not work - which is a hallmark of Tanki development. ("To err is human. To QA is NOT TANKI POLICY!" Tanki motto: "We'll promise, but we won't deliver. When we make a mistake, YOU suffer. If the mistake benefits you, we'll make sure you suffer anyway." Oh yeah... "We don't give a damn what you think." Nah! You're just a sycophant. A suck up. Truth is, if they had a clue, the leader board would have worked properly, the awards would have been generated immediately, and no one would be left wondering what Tanki screwed up THIS time.

Tanki implements a kill counter (good) but it doesn't count your kills until you have more than 400 (insanely stupid). What's the point? Somewhere in software you have to count kills - why not just display the count on demand - even if it's less than 400? I'd like to know the exact number of kills I made. -_- The system knows it, but won't tell. Edit; it does tell only after 400+... Yeah... it's part of the insane stupidity that accompanies everything Tanki does.

About time Tanki fixed the hack. I'm just afraid the "cure" may be worse than the disease. I've had games where I got "airborne" coming off a hill, landing on another tank, etc., and just got a "self-destructed" message and boom! I was gone. I chalked it up to one of the many (many, many) bugs that Tanki never bothers to fix. I'm thinking this "cheat" fix might just become another "bug" if it just looks at how high you are or how fast you got there. As for the "new" maps (i.e. old maps with a coat of paint and a new marketing spiel), some are actually not bad - but they're not good REPLACEMENTS for the old maps. Does anyone like the new "Polygon" enough to lose the old Polygon? I don't. I mean, the new map is okay - but I liked the old map better. Industrial zone? The new one sucks. Massacre? Again, I liked the old map better. Don't mind the new map - but if I can have only ONE, I'd take the old one in a heartbeat. The new Brest map? Sucks. Hard. Highland is probably the ONLY map that I think is good enough to replace the original, that is, the ONLY new map that's actually better than the one it replaced. What baffles me is why Tanki couldn't come up with some actual NEW maps? Is it really that hard? Sit down, create a map from scratch... done! Not butcher an old map and call it "new". And why is it that there are only a few maps available for missions? Tanki is getting pretty freaking boring limited to just a few maps for missions.

Right on target regarding Yorkie and Brest. Also, that "wheelchair accessibility" in the pit is stupid, and what's the point of chopping off the side trenches? Highland is the only map I've played that does not seem to have gone down hill. But the original was a good map too. Why not have BOTH? Rio is FUBAR. I knw the devs are trying to force everyone to play on one map - but come on!

Well, that's a good story for NOW, but what has been the excuse for the past three years? And once implemented in HTML5 the excuse will be that they're migrating to Wintucky-5D in 2022, so why fix the HTML5 bugs? Face it - Tanki doesn't give anything about bugs - unless they benefit the players (like the gold rain). Then they can't "fix" the "problem" fast enough. And rip off the players while they're doing it. If I had a gold box for every time I got cheated by Tanki bugs, I could host a gold box rain that would bury the field. Get a clue! You have to lead more with Magnum than with Stryker! And you don't have to do any range estimation with Stryker. Like every other turret, you just aim in the direction you want to shoot and whether your target is near or far, if you line up on it, you hit it. With Magnum you have to not only line up, but get a proper range and elevation estimate. In effect, you have to do TWICE the work to hit a target. The Magnum advantages are its blast zone and its ability to shoot over obstacles. But it's further handicapped by its rate-of-fire, which is the slowest of all turrets. An M2 Magnum reloads slower than an M0 rail. So basically if you can get the bearing, and azimuth, and powder charge right, you can deliver a big whallup. But it's harder than any other turret. That's probably why the Tanki devs decided what the game needed was wheelchair accessibility. I mean, how frustrating is it for a punk kid to get through the spaces at the bottom of the pit in Brest with a Mammoth when they can't even turn their turret? Tanki solution? Let the player improve? Hell no! Let's make the paths REAL WIDE and cram more players into every game. Then call it a "new" map.

Developers didn't learn diddley squat from the "glitch". Tanki still does a lousy job of testing and finding bugs. If they had any REAL intention of fixing bugs, they'd have a bug track page that showed pending bugs, status, resolution where everyone could see what's broken and when it gets fixed (never). Instead of fixing problems like the "your turret will no longer inflict any damage" bug, they introduce CRAP that nobody wants/needs. The Unified Battle List is one example. Now instead of being able to play a game 1 on 1, or even in small groups, everyone is herded like onto maps revised for players that had to be made BIGGER to hold more victims! The one actual "new" map (of the 20 or so promised) is a rehash from an xmas map from a year or so ago. Face it. Tanki hasn't a clue. More than half of all code changes introduce "features" nobody wants plus bugs. The jump hack is well known. No fix. The battle lists still display battles of the wrong kind. Never addressed. The "can't pick up that box" has been around for years - never fixed. The "you're a ghost" bug still crops up from time to time. "An error occurred". - Who hasn't had that one. And those are just bugs I know of off the top of my head. If I really thought about it, I'd probaby think of a half dozen more - plus a dozen "improvements" that made the game a lot less fun. If they had "learned their lesson" they'd be fixing this stuff and they'd stop making changes that diminish the game. They haven't. And they aren't. All the gold box rain showed us was that when Tanki screws players, it's okay. But when Tanki screwups BENEFIT players, Tanki becomes a thief.

Little Willie has almost everything wrong. The maps are a mess. Magnum is one of the more difficult turrets to use (but more fun for that very reason). Styker is only slightly harder to use than thunder - with similar effects for one-off shots.

I didn't know that making a map "Wheelchair Accessible" counted as making a "new" map. The Tanki version of a "New" Porche would be a 1968 VW Beetle. The Tanki version of a "New" Kate Upton would be Phyllis Diller. The Tanki version of a "New" T-14 Armata would be a 1917 French Renault FT. Seriously, is this the best Tanki can do? Because if it is, it SUCKS! Instead of taking some perfectly good maps and screwing them up - how about some actual NEW maps. Provisional Definition: New: "Something we haven't seen before. Original. Not a crappy copy of something that already exists. Dumbing down the maps to the point that your blind grandmother can navigate them does NOT make a more interesting game. I get the feeling that what Tanki really wants to do is cram all players onto one map, lock them in and squeeze them until their blood, gastric juice, aqueous humor and money dribble out. Making maps bigger does not make them better. Tanki's overall grade for the new maps: F :angry: Instead of the effing "ram and cram" system, go back to letting people pick servers and battles. Stop cramming people into these nasty maps, give people a choice what battles to play - and whether they really WANT to play a game with 19 other people.

Well, I'm not surprised that Tanki did the venal, stupid, rude, irresponsible thing and took back all the proceeds from their screwup. Why did it happen? Tanki doesn't do any QA. It's the same reason there are so many bugs in the program. But when you get cheated by Tanki because of one of the bugs - do they fix that? No. So when Tanki failure cheats you - it's okay. When you get something from a Tanki failure to do their job right (by TESTING), you get cheated again. The Tanki mentality appears to be irresponsible and to cheat the players. I am not surprised.

Why would you think everyone would agree to that sort of inanity? We've suffered plenty with a whole slew of Tanki dev mistakes. This time we didn't get HURT by their mistake. And you want to undo the benefit... why exactly?

Corporal with 400 gold boxes. That's hilarious!

Sorry - if you didn't show up, you lost out. Weasels who weren't even playing are trying to cash in. Of course you're "fine" with paint removals... you didn't do diddly squat.

God knows we've surely been PUNISHED for PLENTY of dev mistakes!

Actually, I think it would be pretty funny for some noob to have some "super" paint. Can't even turn his turret, has a maxxed out tank, and he's still getting his behind shot off! ROTFLMAO!

That's baloney. It's like when Tanki had the defend the gold tournament a week or so ago and not everyone got in. If every time a person failed to get in on an event they quit, NOBODY would be left. EVERYONE would leave. This is a glitch. A transient abnormality. It's not like a hurricane - it's more like a gust of wind. Some people will be able to upgrade a little sooner. But not any sooner than someone who bought a bunch of crystals. Some people will have a spiffy new paint. But not any paint that someone couldn't just buy. Some people will have more supplies. But not any more than someone who just forked over some cash. And it's pretty clear this isn't going to be happening all the time - which is what it would actually take to "ruin" the Tanki economy. In fact, your argument amounts to saying that because you paid $5/pound for steak, you'll never eat steak again because you just found out some people, one time, for a couple of hours, got steak for free. It's what my dad would call, "Dog in the Manger" behavior. You don't care about what you have or can get - you just want to prevent other people from having it too. In short: You're selfish and mean-spirited. You don't just want what's best for you - you want to make sure other people suffer. If Tanki's smart, they'll just fix the bug and move on - and part of their NEW procedure will include REAL QA TESTING before each release... something I don't believe they've EVER done before.

Horse pucky! The people who have extra money to blow on Tanki don't work 1/10 as hard.

If it takes you an hour to read a few messages, you might want to work on your reading speed.

This is a good and thoughtful analysis... which is precisely why I wouldn't trust Tanki to follow this course of action. In case anyone missed it, the ONLY reason this happened was because of inadequate QA testing. As someone has already pointed out, if someone at Tanki had tested even ONE game, they would have seen the issue. So this is just another is a very, very, very long list of Tanki bugs. It just happens to be a bug that Tanki will actually fix. The rest of the bugs? Sorry. You just have to suffer with them because, well, you know - Tanki can't be bothered to TEST software or FIX it.