Battle 55505 detail

sort
corgator 13 years ago I was crashing - voted for exit, and they abused my fault for the sake of elo. +0 / -0
Antelope 13 years ago Sorry, but bugs aren't really a good reason to exit a game, especially a game that lasts 23 minutes. Everyone crashes, lags out, or has weird UI behavior at some point. http://zero-k.info/Battles/Detail/54981 Take a look at that battle! I crashed halfway through a FFA game and had to reconnect. I could have asked for an !exit or whatever, but honestly if I had lost I would have lost a couple Elo and I wouldn't care. It happens. +0 / -0
jseah 13 years ago The polite thing to do when your opponents have a crashed player is to pause and wait for them to rejoin. This doesn't happen often enough. Also, I don't think crashing should warrant an !exit. That's there to get out of ninja starts and general disagreements. +0 / -0
Antelope 13 years ago >The polite thing to do when your opponents have a crashed player is to pause and wait for them to rejoin. I strongly disagree with this statement. I most certainly do not ask, want, or expect my team, or opponents, to wait for me to reconnect. The whole reason Lag Monitor was added to ZK is to prevent everyone from waiting for reconnects. One of the things ZK does so well is maximize uptime. In almost any other online game I play, or have played, crashes were just considered part of the game and not worth pausing for. Why should ZK be any different? +0 / -0
corgator 13 years ago because it is an EARLY crash. I didn't even had one LLT or defender when I got attacked. My whole team only lost, because 1. I had nothing against a sea scout. 2. My enemy sent a corvete as I had only 1 hover scout - not even 2 or a scalpel 3. I would have choosen ships or made 2 scalpels early - my ally didn't because of he wanted to save metal. +0 / -0
Antelope 13 years ago >because it is an EARLY crash. Don't care. Just take the allied units and play the game. +0 / -0
corgator 13 years ago just let someone die, because you don't make a single unit at his factory +0 / -0
Saktoth 13 years ago Waiting times were really ramping up with rejoin. This is why we added lag monitor. You do not need to pause anymore, simply control the units of the dropped player until they return. If its very early on, a quick pause simply to wait for the drop or to queue up some orders is okay but shouldn't be mandatory. Anyway this kind of thing happens. +0 / -0
corgator 13 years ago If someone drops out, the game should auto-pause for 1 minute. You need to check the other ones units. It would be nice if each unit - and only YOUR new units - which you got, get outlined untill you selected them once ( exclude CTRL+A from outline uncheck? ) +0 / -0
Antelope 13 years ago >It would be nice if each unit - and only YOUR new units - which you got, get outlined untill you selected them once ( exclude CTRL+A from outline uncheck? ) Uh, when you get someone's units you get a tons of map markers saying "Units received from so-and-so". If you're not aware after those markers, I doubt that anything else could alert you. Perhaps an audio message, "Units received". >If someone drops out, the game should auto-pause for 1 minute. No. Despite what you personally think, the community overwhelmingly prefers the new system that reduces pause time. No matter what you argue on this subject, it's not going to be enough to overturn a feature that 90% of the community prefers. You were LUCKY enough to start playing after lag monitor was put into effect. I'm not exagerating when I say that there were games where we literally spent more time paused than player. THAT is why I don't wait for crashing players. There are so many bugs/crashes/lags/UI issues in ZK/Spring that when we DO pause for each issue, the game length doubles from all the pausing. No one liked it. Everyone likes new system. Trust me when I say it's MUCH better than the old one. +0 / -0
Antelope 13 years ago Jesus. Christ. I actually watched the game, and here's exactly what happened: Game start - nubtron crashes 1:00 Begins reconnect 1:10 Caught up, engages hover scout. Does not kill. 1:15 Begins long walk across the freaking map! http://imgur.com/a/762VW#yhMvp 2:10 Still walking, types "Silly crash" 2:23 FINALLY turns around and starts heading back to base. 2:45 Asks "why did nobody pause" despite the fact he was missing for only 1 minute and game still has tons of time left. 3:25 finally made it back to base. Starts a mex (doesn't finish it) and plops a lab. 3:40 Starts reclaiming rock while morphing com 4:20 Has not even started making a unit. Com has been idle since it started morphing. Says something about trying to rez ships. 4:20-16:00 Nothing. Then resigns, and types "fucking abusers". http://imgur.com/a/762VW#yhMvp I don't see ANYTHING that was abused. His team didn't pause, he never asked anyone to pause. If anything, his team is more at blame than enemy for not asking for a pause. On top of that, even after he returns he does NOTHING to help team. He literally doesn't make a single unit in 16 minutes. nubtron, this was simply poor gaming and getting upset over nothing. Deal with it. I took a bunch of screenshots of this happening. Album: http://imgur.com/a/762VW +0 / -0
Antelope 13 years ago http://zero-k.info/Battles/Detail/56710 That game is a pretty good example of practicing what I preach. Despite being left with 4 (maybe 5?) coms, while drunk, I still try harder than nubtron does in this entire game. Heck, I made U N I T S. Units are OP, for sure. +0 / -0
corgator 13 years ago I expected that my opponent has about my own level of advancement. My team was low on metal extractors ( all players ) and didn't made units during my crash. I underestimated the game time. My com was walking, because my mouse jumped in to top left corner of the minimap and I didn't found my com in my base as I cought up after a "/reload". After a time I have seen my com was missing and selected my com with hotkeys to move it back to base. I was a bit tired, but every thing I tried got countered very rapidly, that is noting I am used to. +0 / -0
Antelope 13 years ago See? Those are all reasons that YOU failed. That game was 100% playable, even after you crashed. The only thing that kept you from winning was you. Don't try and get a bunch of people to change a feature because YOU failed in a single game. Next time give it your best shot. You'd be surprised at how many games you can win even when you crash. Don +0 / -0
Antelope 13 years ago And... edit button rarely works for me now. My name is not Don, I was trying to type "Don't" and accidentally submitted. +0 / -0
Saktoth 13 years ago It doesn't work on game comments yet. +0 / -0

Title:	BIG TEAMS: Newbies welcome!
Host:	Springie
Game version:	Zero-K v0.9.9.5
Engine version:	85.0
Battle ID:	55505
Started:	13 years ago
Duration:	23 minutes
Players:	8
Bots:	False
Mission:	False
Rating:	Casual