Challenges
April 23, 2024, 11:00 AM

TCB12: Fight for the Water Tower

Challenge #208, Viewed 8066 Time(s)

Basic Information
Rate challenge
5 / 5
Total Members Voted: 3
Name: TCB12: Fight for the Water Tower
Type: Misc
Moderator: Netherlands DarkOne

Started: March 14, 2013, 12:39 AM
Expire time: April 04, 2013, 01:30 AM

EXPIRED
You can still submit your time. But you won't recieve the 4 points as it is not the current challenge anymore.

Challenge maps:
Scheme File(s): scheme TCB12

Description:
Your troops are thirsty! Oh look, doesn't this water tower seem rather suitable for your needs? Hmm... it's guarded. Time to claim what is rightfully yours. We paradropped your troops at night, so thank us that your presence hasn't been noticed yet.

Rules and objectives:

- Start the game with 7 worms for your team and 4 worms for your opponent (CPU 1).
- You need to have the first turn of the match. If the CPU does, draw the round and restart.
- Eliminate all opposing worms.
- You're allowed to use rope/bungee knocking.

Ranking method:

- Your score is determined by the amount of HP you have left, subtracting points for each weapon used.

Point value for the weaponry:
bazooka: 45
homing missile: 46
sheep launcher: 63
grenade: 47
shotgun: 50
uzi: 45
longbow: 30
mine: 48
firepunch: 30
dragon ball: 30
blowtorch: 22
drill: 15
dynamite: 75
mole: 35
flame thrower: 75
Triggering sudden death will cost you 150 points.
Name: Fight for the Water Tower by Wyvern
Best Record: 678 by Statik
Pending times: 0
Number of members participated: 13
Number of Records: 26

Download Map:
Downloaded 412 time(s)
Recorded Country Player Recorded Groups Record Replay Map Points Posted Overall Points Overall Rate Info
1st Russian Federation Statik dt sm fp 678pts 20 March 21, 2013, 12:25 PM 5,908 Elite
2nd Bulgaria Worm_gamer che dS pd 670pts 15 March 21, 2013, 07:18 PM 3,906 Elite
3rd Italy OrangE 69 FoS WAR 670pts 10 March 20, 2013, 03:32 PM 1,095 Beginner
4th Russian Federation Uzurpator che pH tS 667pts 5 March 21, 2013, 06:55 PM 1,801 Competent
5th Serbia Ramone b2b 637pts 4 March 17, 2013, 02:04 PM 1,093 Beginner
6th Netherlands DarkOne WQDB TdC NfBX 625pts 3 March 16, 2013, 01:15 PM 1,343 Novice
7th Hungary Balee WAR UT 613pts 2 March 20, 2013, 11:49 AM 1,058 Absolute Beginner
8th Russian Federation _ssm_ che 612pts 1 March 14, 2013, 02:00 PM 7,842 Elite
9th France LeTotalKiller WoSC 546pts 0 March 14, 2013, 06:40 PM 1,976 Distinguished
10th Finland Husk TdC b2b ea 532pts 0 March 14, 2013, 04:47 PM 5,233 Elite
11th Russian Federation Dmitry che tS WAR 480pts 0 March 14, 2013, 04:38 PM 1,043 Absolute Beginner
12th Russian Federation Korydex che 211pts 0 March 18, 2014, 06:38 PM 1,854 Highly Competent
13th United States Ytrojan DMont Clade RH 20pts 0 January 13, 2015, 01:58 AM 1,095 Beginner

Statistics of this challenge

Points Overall Points Overall Rate
Russian Federation Statik 25 5,908
Italy OrangE 20 1,095
Bulgaria Worm_gamer 20 3,906
Russian Federation Uzurpator 15 1,801
Serbia Ramone 10 1,093
Netherlands DarkOne 9 1,343
Hungary Balee 8 1,058
Russian Federation _ssm_ 7 7,842
France LeTotalKiller 6 1,976
Russian Federation Dmitry 5 1,043
Finland Husk 5 5,233

Author Topic: Challenge #211, TCB 39: The Banana Blaster  (Read 2854 times)

0 Members and 1 Guest are viewing this topic.

Offline skOrpuz

Challenge #211, TCB 39: The Banana Blaster
« on: March 21, 2013, 03:23 PM »
I'd like to play it but i have a dumb stupid doubt...how to count my total time? :D

Re: Challenge #211, TCB 39: The Banana Blaster
« Reply #1 on: March 22, 2013, 10:38 PM »
Your score is the turn time you've had to use up before you land on the platform below the finish line. Added that to the challenge description 8)

Offline skOrpuz

Re: Challenge #211, TCB 39: The Banana Blaster
« Reply #2 on: March 24, 2013, 05:32 PM »
so i have to watch the replay and counting or just extract game log? x)


Re: Challenge #211, TCB 39: The Banana Blaster
« Reply #3 on: March 24, 2013, 06:14 PM »
either way works :) But keep in mind that if you surrender/skip after landing, that means the time in the log overestimates your time by a couple of seconds.