Loading...
  OR  Zero-K Name:    Password:   
Back to List

ZeroWars v2.0.5 Supported

By petturtle
Rating:

made for zero-k
Size: 16 x 6

PLAY ON THIS MAP


Downloads: 298
Manual downloads:
http://zero-k.info/content/maps/ZeroWars_v2.0.5.sd7


Preview
Filter:    Player:  
sort
2 months ago
Sometimes the big constructor doesn't spawn, which results in the waves not spawning.
See top right in this replay
zero-k.info/Battles/Detail/934255?
+1 / -0

2 months ago
DErankLaserzwei

This is caused by spawning extremely close to the right edge of the Startbox.
Apparently the builder itself spawns a little bit to the right, which avoids the check for builders on a platform -> no wave spawn for that platform.

This is hopefully fixed in the next version and can be avoided by not spawning at the right edge of the startbox or !exit when you notice a small builder spawns.
+0 / -0


2 months ago
Was the OP strategy of spawning everyone on the same platform fixed?
+0 / -0

2 months ago
Maybe this was outlined earlier, but can someone explain the eco regarding ZW now?
+0 / -0
You make units, and each unit generates a different amount of energy, which it says on the unit. Cheaper units give more energy relative to their metal cost, so cheaper units can be used to build economy. When your wave spawns, you get metal equal to your energy income. Also, your hero gets metal by killing stuff.

The solution to the multiple-people-on-one-platform problem is to make it so the total income of all people on a platform combined, is the same for all platforms (if everyone makes the same units). This ensures that when a platform spawns, the wave is the same size regardless of which platform it is.

To do this it is first necessary to alter the initial metal amounts at the start of the game depending on how many people are on the platform. If there are 3 people on the platform, each should get 1/3 the normal starting amount, so the total metal for each platform at the start is the same.

After that, if each person gets the full metal income for their units at the same intervals - such as each player getting it with every wave - that should work out, if you don't consider the heroes. Due to the initial amounts being lower, each player on a crowded platform will have a fraction of the units, so their later income from those units will also be proportionately lower without the need for another adjustment.

Considering the heroes, hero income should be divided by the number of people on your platform.


Alternatively: give each player the same amount of income (if they make the same units), and spawn one player at a time instead of one platform.
+0 / -0

2 months ago
quote:
Also, your hero gets metal by killing stuff.

That got removed. You only get eco by building units atm.
+1 / -0
2 months ago
http://zero-k.info/Battles/Detail/936024

It seems thunderbirds do not attack, even if set to fire at will
+0 / -0

2 months ago
Ive seen TBs work but not work sometimes, temperamental. Thyre actually quite good with a few to counter shield spam which is the long game win tactic imo
+0 / -0

2 months ago
Some comments:

-Drone spam is too powerful at start, you can counter but only just and needs to be perfect.

-annoying waiting for hero to unlock after death, like its stuck, then gets enabled, needs indicator or something to say its not available yet.

-energy resource is irrelevant?
+0 / -0
2 months ago
http://zero-k.info/Battles/Detail/945506?

map dies if u resign
+0 / -0
I have a suggestion to make the game more hero centered. Whenever a hero orders an ult on a section of the map, all nearby units you own that have a manual fire in range should fire there too. This makes your hero much more important in the late game. Does that sound reasonable?

Maybe we can do it where units you own will ult if your hero's ult is available and their ult is available. Or we could have it so your hero's ult doesn't even have to be up, just the in range unit's ult.
+3 / -0


51 days ago
Some planes still make errors on this map due to MoveCtrl.

https://github.com/ZeroK-RTS/CrashReports/issues/33710
+0 / -0
Back to List