Loading...
  OR  Zero-K Name:    Password:   
Map: DeltaSiegeDry Deluxe V3
 DeltaSiegeDry Deluxe V3
Title: [A] Teams All Welcome
Host: Nobody
Game version: Zero-K v1.8.12.1
Engine version: 104.0.1-1544-ge1f249f
Battle ID: 1012954
Started: 5 years ago
Duration: 56 minutes
Players: 26
Bots: False
Mission: False
Rating: Casual
Watch Replay Now
Manual download

Team 1
Chance of victory: 43.2%

CNrankcn_wptr
FIrankKapy
LVrankSenaven
DErankzini
ROrankJoeDoe
USrankgohanblanco4009
GBrankTechAUmNu
RUrankCelestialCerberus
GBrankDoggystylus
NLrankKwaszati
IRrankShno
NLrankheadlessslayer
NLrankWhezel
Team 2
Chance of victory: 56.8%

USrankSab
PLrankizirayd
TWrankKitty116065
USrankwildemind
USrankICUPEEE
USrankFantasyZero
ZArankPlayerOne
USrankstrikeshadow
USrankKryptman
UArankDILINO
NLrankper
RUrankCMDR
FRrankSlare
Spectators
CZrankAdminLicho
USrankTiberia
BErankNicoss
FRrankdedelepd69
SErankRavaen
RUrankscorpion25
CArankA_Zen
GBrankMoonDestroyer
SOrankMikeMike34
CArankHughsy
DErankHoppili
IRrankENTERWAR

Show winners



Preview
Filter:    Player:  
sort
GBrankTechAUmNu
5 years ago
Seriously cursed game.

ADMINS PLEASE CAN YOU LOOK AT THIS AND FIGURE OUR WHAT WAS HAPPENING.
was as slideshow for 50% of game.

Someone on my team was spamming a queue over the whole map with lotus.
+0 / -0

LVrankSenaven
5 years ago
(edited 5 years ago)
+1 / -0
FIrankKapy
5 years ago
(edited 5 years ago)
Hint: who has the big cpu usage(or whatever that is)

And no, not mr D.
+0 / -0

LVrankSenaven
5 years ago
Initially i blamed Kapy because he had similar colour (i played with him in frontline). Only when he complained that he have no con (and he even didn't ask for one) i started look at player list to find that there is three players with similar colour.
I would not be against that player who did this would get ban. It is even worse then team killing or griefing because everybody lagged and there was numerous pauses. And still he continue to do it many times.
+1 / -0



unknownrankShaman
5 years ago
(edited 5 years ago)
IRrankShno is innocent and (unfortunately) the auto llt script was not to blame for this. (Note the real culprit is likely to have been @wptr_007 who issued large amounts of orders and im sure the infolog has some complaints about it)

Auto LLT continues to be a pain though. Its happy to spam commands even *while 30 minutes behind*. I hate to be a broken record player but I think its time to use the widget disabler to disable it. The cost of the widget existing seems to far outweigh any user benefits it has existing.

This seems to put us as developers in a bad position. We can continue allowing it to exist at the risk of it proliferating and thus entering a degenerative state. It also is risking running into bad reputation here and risks social stigmatization. However using the widget disabler risks infringing on user choice and being seen as bad guys trying to take away people's widgets. (And we very well know some people would be glad to)
+0 / -0
FRrankmalric
5 years ago
Would some-kind of command rate limiter work? Plus something to display user a message like "more commands are coming from your computer than allowed, will be limited, disable widgets to issue less commands". And if the user wants no to click to have auto LLT but not be able to issue commands, it's his choice...
+0 / -0
NZrankesainane
5 years ago
(edited 5 years ago)
For the curious, here's a quick (logarithmic!) breakdown of command volume over the course of the battle by player:
+3 / -0

GBrankAdminDeinFreund
5 years ago
I thought it was impressive, then I noticed the log scale..
+1 / -0
FIrankKapy
5 years ago
"(26) Astran"?
+2 / -0
NZrankesainane
5 years ago
Derp, well spotted. That's what I get for manually grabbing names out of the startscript definitions in the demofile, I suppose.

[Spoiler]
Fixed.
+0 / -0

LVrankSenaven
5 years ago
quote:
"(26) Astran"?


Seems ZArankAstran is true ninja. :P
+0 / -0