Or would you like to register?

Author: | Dilvish, Fat Controller, necros, Tronyn, Tim Elek |
Title: | The Coagula Contest |
Download: | coagulacontest.zip (cbcdcb4e6d806d6682f9a2c36ae4c10f) |
Filesize: | 4487 Kilobytes |
Release date: | 22.01.2002 |
Homepage: | http://tronyn.planetquake.gamespy.com/cogcontest/ |
Additional Links: | erc's Excellence • Ethereal Hell • TEAMShambler • Underworldfan's • |
Type: | Partial conversion |
BSP: ![]() ![]() ![]() ![]() |
Files in the ZIP archive
File | Size | Date |
---|---|---|
coagula_readme.txt | 13 KB | 05.01.2002 |
pak0.pak | 13397 KB | 22.01.2002 |
coagulacontest.zip
The Coagula Contest
"This contest was run mid-September to mid-November of 2001, with the goal of creating maps in the tradition of Tim Elek's 'Coagula' series of maps - a series of structures floating in the void. The contest was run by Tronyn and the judges were Fern, Grindspire, and Xenon. The contest also includes a bit of custom QuakeC code, which was done by Necros.There were 5 entries: Tronyn(2), Fat Controller, Dilvish, and Necros. In addition, a start map created by Tronyn is included, as well as the original Coagula series by Tim Elek."
Tags: space map, contest, small, void, coagula
Editor's Rating: Excellent
User Rating:
3.9/5 with 18 ratings
You can NOT add ratings
if you are not logged in.
You can NOT add ratings
if you are not logged in.
The winner of the contest had a sort of frustrating layout with regards to sequence buttons.
Necros entry (shared third place, to the left) had a really good atmosphere and some good puzzly part, but did suffer from a little confusion at times (which ended up being alright once you "got" the map).
I'm a bit surprised at the choice of winner--I would've personally vouched for necros's map (which has a standalone release) although I suppose it's not really a "true" coagula map. Nice to see that Tim Elek's original Coagula trilogy was included.
Post a Comment
Your comment will be parsed with Markdown!Keep the comments on topic and do not post nonsense.
Did you read the file's readme?