Loading...
  OR  Zero-K Name:    Password:   
Title: MM 3102: 1v1, Rank Singularity
Host: Nobody
Game version: Zero-K v1.8.9.4
Engine version: 104.0.1-1544-ge1f249f
Battle ID: 964586
Started: 3 years ago
Duration: 12 minutes
Players: 2
Bots: False
Mission: False
Rating: Competitive
Watch Replay Now
Manual download

Team 1
Chance of victory: 78.6%

SErankGodde
Team 2
Chance of victory: 21.4%

GBrankPRO_rANDY
Spectators
DErankManu12
GIrankTAG_ROCK

Show winners



Preview
Filter:    Player:  
Page of 2 (24 records)
sort


3 years ago
Can you fix drones confusing skirmishing AI pls?
+2 / -0


3 years ago
Also please fix overkill against drones. Scalpels will shot all their missiles against them.
+0 / -0


3 years ago
Okey, all their missiles was an overstatement, but they will shoot a lot of missiles against them.
+0 / -0

3 years ago
I paid for those upgrades! Working as intended!
+2 / -0


3 years ago
+1 / -0
Video is just typical Godde vs Randy, what am I meant to be seeing here?

(Edit: This was a joke)
+1 / -0
3 years ago
On the 7th minute, the scalpels fight the drone and a group of units.
Look where commander randy is, he's in three scalpel radii.



Why did the drone fly there on its own?
Why did 90% of scalpels shoot at the drone?

If they hadn't fired at the drone, when Godde could have destroyed those 3 units, weakening the bottom, instead they just left.

Another drone arriving, then inflicts several shots at different units
+1 / -0
You can't overstate my disappointment when I realized it was SErankGodde vs GBrankPRO_rANDY instead of SErankGodde vs GBrank[Fx]Drone
+2 / -0


3 years ago
Bump. This really needs to be fixed as the existence of the drone can heavily complicate attempts to skirmish. Longer the skirmisher cooldown, the worse this problem is.
+0 / -0


3 years ago
Sounds like Scalpels should have OKP vs drones, and all skirms should consider drones a non-valid skirmiee.
+0 / -0


3 years ago
Scalpels and similar units have OKP vs. drones, they just count their projectiles as having less damage to offset the low chance of them hitting.
+0 / -0


3 years ago
Does that mean that the behaviour is around to stay, despite it being generally despised?
+0 / -0


3 years ago
OKP can be disabled user-side, so i think it would be OK if it was more aggressive (withholding more shots) against drones.

Players who want to shoot the drone with everything they've got (which seems to be the default condition atm) could then disable OKP and do just that.
+1 / -0


3 years ago
Maybe the damage modifier should be tweaked for Scalpel. I really don't want to have people toggling the OKP button.
+0 / -0

3 years ago
If Guardian gets an effective shield thanks to drones drawing fire, shouldn't it be one of the weaker comms in terms of HP?
I'm not sure how effective this would be as a nerf.
+0 / -0
3 years ago
Now constructors are spamming nanoframes for themselves, which makes scalpels shoot at this, although a scalpel shot is very expensive
+0 / -0


3 years ago
It also causes other skirmishers to hurt themselves, see recluse, ronin.
+0 / -0
3 years ago
quote:
It also causes other skirmishers to hurt themselves, see recluse, ronin.


Different rate of fire and range of attack
+0 / -0

3 years ago
RUrankizirayd I'm just trying to suggest a compromise given the facts of current Guardian comm / drones, that doesn't involve a much more intelligent targeting AI. Any comm can spam nanos as fake targets, if you think that's an issue then there should probably be another thread.
+0 / -0
Ultimately, what I would LOVE to see and make use of, is a personal config file / UI that I can set behaviour over-rides within 1 time, and tweak whenever I like, to control which units fire at what targets. At first, the file is empty, but you could add a single unit at first.

Let's add lance.

Firestate 1: Fire at any target that has a metal value of >400 and is not a radar dot, prioritize Commander.
Firestate 2: Fire at any target that has a metal value of >200 and is not a radar dot, prioritize Commander, ignore Halberd/Razor.
Firestate 3: Hold fire.

Custom ignores like Halberd, solars, nanoframes, gauss, razor would be great to have. People are already tired of Felon blowing it's load on a razor or halberd.

Target prioritization: Prioritize by class / cost / unitname. I want my dominatrix to stay on that outlaw, not the 1/3HP rogue that I never asked it to capture.

Over-rides by direct fire command optional.

That way, all the heavy lifting is done before the game, to the user's specification, without the use of some confusing/expensive widget, and can be adjusted as they see fit. Until we have something like that, it's just the same old frustration game after game, spending micro to babysit your heavy payloads against deliberately, exploitatively placed false targets.

I'm guilty of taking part in using all the tricks in the book when it comes to messing with the opponent's AI. nanospam vs moderators, scalpels, puppies, occasionally artillery. Deliberately picking Guardian when predicting hover enemy. Placing razor/gauss with repair in arty's way. Using Godde's closed halberd into AoE zones. Combat terraform, when it was a thing. It's all bullshit that I wish I didn't have to do, and didn't have to play against, and it's all almost mandatory to stay super competitive. Kill it with Config.
+3 / -0
Page of 2 (24 records)