Weekly 5-map Tournament - Highest Mountains - Closing 7-31-2011

[mopa42]

All Tournaments
Code Map Scoreboard
Tournament Score Tool

This week's theme is Highest Mountains in the World, chosen by mopa42.

Map Name:	Size:	Complexity:	Height:
Mount Everest	Medium	Medium	8,848 m / 29,029 ft
K2	Small	High	8,611 m / 28,251 ft
Kangchenjunga	Large	High	8,586 m / 28,169 ft
Lhotse	Small	Medium	8,516 m / 27,940 ft
Makalu	Large	Low	8,485 m / 27,838 ft

Let's go thrash some creeper!

[Measure]

K2 is going to be the death of me.

[mopa42]

K2 is going to be the death of me.

I considered not including it, since the field combined with the drones looked really tough. But I was feeling evil (cackles).
However, the map is entirely doable. If you get too stuck I can upload a hint.

[Measure]

K2 is going to be the death of me.

I considered not including it, since the field combined with the drones looked really tough. But I was feeling evil (cackles).
However, the map is entirely doable. If you get too stuck I can upload a hint.

I think I have a handle on it now, have a saved game at work that I should be able to finish without a problem. Will have to try a couple of different strategies to see if I can figure out how to get a halfway decent score on it.

[florrat]

Okay, this is the first tournament where I can do a serious attempt (last two weeks I was busy with other stuff). These are my scores after trying each map once (with a few restarts/loading save files of course). I will try K2 again later.
I'm currently #1  ;D :o. In the case I would win this tournament: I do not have acces to internet sometime near the deadline, so the runner-up should pick the next theme.

Scores for florrat

Map Name:	Size:	Complexity:	Score:	Time:
Mount Everest	Medium	Medium	11448	7:26
K2	Small	High	11514	9:15
Kangchenjunga	Large	High	10394	13:13
Lhotse	Small	Medium	12212	4:47
Makalu	Large	Low	12688	3:55
Total:			58256	38:35

PS: Great program, mopa42!
PPS: I'm strongly in favour of Measures suggestion that the winner should pick the theme of the tournament which starts a week later. Then the winner has some time to think of a theme, and is not forced to do this on Monday. Also, the participants do not have to wait on Mondays until the theme is known.

I think this is a good idea. However we would have to think about a solution for the one-week gap that would exist when this gets implemented

We can do it the following way: There is one tournament where the winner decides the theme of the next tournament (in the one-week gap), and the runner-up decides the tournament which is one week later.

The rules for these tournaments have already been addressed
and readdressed when we used to do them for CW1, see here.

According to these rules, Fisherck will choose the maps, and
if he wins again? 2nd place and so forth.

Also, if we 'know' which maps will be featured in the next
tournament, what stops us from getting ahead? This is why
it is kept secret until it is publicly released then everyone
has an equal amount of time to complete the maps.

In my opinion, you can just make the theme public, and already start a thread of that tournament on, say, Saturday. Then there are two tournaments open at that time, but that's not a problem, in my opinion.

[UpperKEES]

the winner should pick the theme of the tournament which starts a week later. Then the winner has some time to think of a theme, and is not forced to do this on Monday. Also, the participants do not have to wait on Mondays until the theme is known.

Just think of your theme in advance when you're at the #1 spot or close to it. If you don't make it, save it for the next opportunity. If you're not available on Monday just PM your choice to ThePenguin.

[florrat]

Just think of your theme in advance when you're at the #1 spot or close to it. If you don't make it, save it for the next opportunity. If you're not available on Monday just PM your choice to ThePenguin.

That's also possible. I will do that for this week, but I'm still in favour of picking the tournament one week later.
If I win, I'll post some screenies Thursday or Friday next week.

[Evil Roc]

Got far from brilliant results this time, made a number of misplays and miscalculations around, but no time to replay it properly. Anyway

Map Name:	Size:	Complexity:	Score:	Time:
Mount Everest	Medium	Medium	11597	6:19
K2	Small	High	11692	8:37
Kangchenjunga	Large	High	10273	14:19
Lhotse	Small	Medium	12068	5:05
Makalu	Large	Low	12593	4:33
Total:			58223	38:53

Maps were quite interesting (and these 2 on high complexity not very easy).

[thepenguin]

Tournament Results

Rank	Player	Total Score
1.	florrat	58881
2.	Evil Roc	58223
3.	jlog	57826
4.	Lord_Farin	56804
5.	Katra	56500
6.	Measure	55152
7.	BrYK	54282
8.	Koker93	54277
9.	Xing	49256
10.	Simon	44107*
11.	bmaw323	40779*
12.	RichieRich	35435*
13.	Colin	21069*
14.	Nate Dog	20761*
15.	BoostBreed75	10454*
16.	HvA	9372*

* Did not finish all maps.

[florrat]

Here are a few screenshots. I didn't make screenshots on the first try, and I didn't try every map more than once, so I don't have screenshots for every map.

First four screenshots are of "Mount Everest". Since the complexity was just medium, I also used makers to attack the creeper, and didn't use that much launchers. After the fourth screenshot I attacked the creeper at the right side of the map, and after nullifying the emitter in the left I moved these units to the bottom-left to attack there.
I don't have screenshots of K2, but I digged first at the left of the map, taking some crystals, and then pushed the creeper to the right, using blasters, launchers and repulsors.
I don't have screenshots of Kangchenjunga either, but I nullified the surface emitter quickly, before the creeper at the left broke free. Then I pushed the creeper on the left down. When I reached the creeper field, I also made shields when the field pointed downward, so that I didn't have to retreat when the field pointed up.
The last screenshot is of Makalu. I used blasters and makers to move down as fast as possible. I could probably improve my time when I made some tech domes to improve packet speed.