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

Rapids_v1 Featured

By Beherith
Rating:

Rapids_v1 - for 1v1 all arms. All units pass shallows. Made by [teh]Beherith (mysterme[at]gmail.com)
Size: 8 x 8

PLAY ON THIS MAP


Downloads: 4696
Manual downloads:
http://spring1.admin-box.com/downloads/spring/spring-maps/Rapids_v1.sd7
http://zero-k.info/autoregistrator/maps/Rapids_v1.sd7
http://api.springfiles.com/files/maps/rapids_v1.sd7

Last battles

Bots B473122 1 on Rapids_v1
Bots B473116 1 on Rapids_v1
Bots B472384 1 on Rapids_v1
Bots B472382 1 on Rapids_v1
Multiplayer B472029 2 on Rapids_v1
Bots B470905 1 on Rapids_v1
Multiplayer B469996 2 on Rapids_v1
Multiplayer B469703 2 on Rapids_v1
Bots B469352 2 on Rapids_v1
Bots B469347 2 on Rapids_v1


Preview
Filter:    Player:  
sort

UArankBoBaH
5 years ago
Very nice map. Good work!
+0 / -0



AUrankAdminGoogleFrog
4 years ago
The image for this map fails to load in a ZKL battleroom.
+0 / -0

ATrankSkasi
2 years ago
Symmetry needs to be fixed. Southeast mex is not standardized and someone said hovers can climb one of the (hill) bases but not the other.
+0 / -0


CArankPxtl
2 years ago
For bugs like that, should the approach be "unfeature first and ask questions later"?
+0 / -1

ATrankSkasi
2 years ago
Maybe first ask if people still looove the map for all its other features. Personally I don't, but others might
+2 / -0

USrankAdminJasper
2 years ago
Hovers have a hard time getting on to the hills because its a narrow path. I will check I know they can get onto bottom hill.
+0 / -0

USrankAdminJasper
2 years ago
Tested hover can get on and off both hill however on both hills they require micro and they get stuck.
+2 / -0

USrankStuart98
2 years ago
This map is bad and whoever featured it should feel bad. Unfeature please.
+3 / -0

ATrankSkasi
2 years ago
All it needs is smoother ramps for better and more symmetric hover pathing, nu?
+0 / -0

PLrankOrfelius
2 years ago
If it is broken/uninteresting in current state then unfeature. Personally I think it is.
Saying "it could be easily fixed" is not an argument for keeping it in the current mappool. If it is going to be fixed then it might be reintroduced.
Simple as that.
+1 / -0
Back to List