Edit 1: Seeing as I am quite late in setting up, I'll be exercising a few creative liberties. Namely, all maps up to my post on page 3 have been added. Normally it's first come first server, regardless. This time however, I have moved stovepipe and tributary to the back so that we can give the new maps a chance. This is my fault for not updating on time, and my apologies to the authors. Your map(s) were moved b/c they have had the most playtime over the last few weeks.
1200-1600 at 72.233.93.233:27015 Just post your request here, at least 1 week in advance. Times are based on U.S. Central Standard. The Steam group automatically adjusts to your timezone, so be sure to check that if you are unsure. http://www.timetemperature.com/tzus/time_zone.shtml
Map | Time | Author | Download | Discussion
ctf_meleefort_b1 | 1200 | taotd | http://forums.tf2maps.net/downloads.php?do=file&id=721 | http://forums.tf2maps.net/showthread.php?t=4083
ctf_malice | 1230 | Bonafide | http://forums.tf2maps.net/downloads.php?do=file&id=691 | http://forums.tf2maps.net/showthread.php?t=3919
pl_haywood_beta5 | 1300 | Laz | http://forums.tf2maps.net/downloads.php?do=file&id=730 | http://forums.tf2maps.net/showthread.php?t=4116
pl_halfacre_a3 | 1330 | Youme | http://youme.coltsplayground.net/pl_halfacre_a3.zip | http://forums.tf2maps.net/showthread.php?t=3745
cp_hillside_a1 | 1400 | Zipok | http://forums.tf2maps.net/downloads.php?do=file&id=735 | http://forums.tf2maps.net/showthread.php?t=4134
pl_silo_a3 | 1430 | Altaco | http://forums.tf2maps.net/downloads.php?do=file&id=733 | http://forums.tf2maps.net/showthread.php?p=38689
arena_mountain | 1500 | Pocok | http://forums.tf2maps.net/downloads.php?do=file&id=760 | http://forums.tf2maps.net/showthread.php?t=4191
cp_vital_link_a2 | 1530 | zpgrei | http://forums.tf2maps.net/downloads.php?do=file&id=746 | http://forums.tf2maps.net/showthread.php?p=39152 |
1fort_a3 | 1600 | Vicenti | http://forums.tf2maps.net/downloads.php?do=file&id=606 | http://forums.tf2maps.net/showthread.php?t=3525
cp_tributary_a5 | 1630 | ChronoTriggerFan | http://tek-spec.net/tf/cp_tributary/cp_tributary_a5.zip | http://forums.tf2maps.net/showthread.php?t=3668&highlight=tributary
pl_stovepipe_a7 | 1700 | Nineaxis | http://forums.tf2maps.net/downloads.php?do=file&id=686 | http://forums.tf2maps.net/showthread.php?t=3891
Guidelines For Testing: Due to issues past and present, I am laying down a few rules. Map testing should be a fun experience to talk seriously w/ your fellow mappers and gamers. That said, please don't be discouraged or scared while reading the first and most important rule.
1. Absolutely no bitching! The people who show up for testing do so because of their appreciation for custom TF2. Most of these individuals are also looking to get some feedback on their map. It is very much a group effort. When we first began the testing events, there was a lot of disrespect and jerkiness if things were not perfect. Example: It's one thing to say 'I think we need more than 5 peeps per team for this part of the map.' As opposed to 'How can I get good feedback like this? The admins/testers/whoever really need to pay more attention. Why bother like this?' Should I hear anything from the latter category, I won't think twice about banning your ass.
2. In order for things to run smoothly, testing requests must be made 1 week prior. This seems pretty harsh I know, but there really is no better way. The big problem we always have is planning. Maps requested for testing will be added to the server as soon as possible. This has to be done manually by an admin b/c of the aforementioned abuse of the direct upload service. Though I have an idea to get around it, for now you'll just have to tough it out.
3. You may not get sufficient testing on the day you request; don't freak out. Whether b/c of a low turnout or everyone gets tired after a couple hours. Simply post a request for the following week, saying only a couple peeps were available, or you only got like 5min. Such incidents will take priority during the next testing day. If there happen to be a dozen people looking for feedback that day, you'll have to be accommodating.
4. When requesting your test, the download must be available. Asking for some testing time and submitting your map a day before the event kinda defeats the purpose. In regards to multiple maps per author; this will be allowed if time permits. Should the testing schedule be rather large on that day, you'll have to settle for just one map.
5. Reread #1.
1200-1600 at 72.233.93.233:27015 Just post your request here, at least 1 week in advance. Times are based on U.S. Central Standard. The Steam group automatically adjusts to your timezone, so be sure to check that if you are unsure. http://www.timetemperature.com/tzus/time_zone.shtml
ctf_meleefort_b1 | 1200 | taotd | http://forums.tf2maps.net/downloads.php?do=file&id=721 | http://forums.tf2maps.net/showthread.php?t=4083
ctf_malice | 1230 | Bonafide | http://forums.tf2maps.net/downloads.php?do=file&id=691 | http://forums.tf2maps.net/showthread.php?t=3919
pl_haywood_beta5 | 1300 | Laz | http://forums.tf2maps.net/downloads.php?do=file&id=730 | http://forums.tf2maps.net/showthread.php?t=4116
pl_halfacre_a3 | 1330 | Youme | http://youme.coltsplayground.net/pl_halfacre_a3.zip | http://forums.tf2maps.net/showthread.php?t=3745
cp_hillside_a1 | 1400 | Zipok | http://forums.tf2maps.net/downloads.php?do=file&id=735 | http://forums.tf2maps.net/showthread.php?t=4134
pl_silo_a3 | 1430 | Altaco | http://forums.tf2maps.net/downloads.php?do=file&id=733 | http://forums.tf2maps.net/showthread.php?p=38689
arena_mountain | 1500 | Pocok | http://forums.tf2maps.net/downloads.php?do=file&id=760 | http://forums.tf2maps.net/showthread.php?t=4191
cp_vital_link_a2 | 1530 | zpgrei | http://forums.tf2maps.net/downloads.php?do=file&id=746 | http://forums.tf2maps.net/showthread.php?p=39152 |
1fort_a3 | 1600 | Vicenti | http://forums.tf2maps.net/downloads.php?do=file&id=606 | http://forums.tf2maps.net/showthread.php?t=3525
cp_tributary_a5 | 1630 | ChronoTriggerFan | http://tek-spec.net/tf/cp_tributary/cp_tributary_a5.zip | http://forums.tf2maps.net/showthread.php?t=3668&highlight=tributary
pl_stovepipe_a7 | 1700 | Nineaxis | http://forums.tf2maps.net/downloads.php?do=file&id=686 | http://forums.tf2maps.net/showthread.php?t=3891
Guidelines For Testing: Due to issues past and present, I am laying down a few rules. Map testing should be a fun experience to talk seriously w/ your fellow mappers and gamers. That said, please don't be discouraged or scared while reading the first and most important rule.
1. Absolutely no bitching! The people who show up for testing do so because of their appreciation for custom TF2. Most of these individuals are also looking to get some feedback on their map. It is very much a group effort. When we first began the testing events, there was a lot of disrespect and jerkiness if things were not perfect. Example: It's one thing to say 'I think we need more than 5 peeps per team for this part of the map.' As opposed to 'How can I get good feedback like this? The admins/testers/whoever really need to pay more attention. Why bother like this?' Should I hear anything from the latter category, I won't think twice about banning your ass.
2. In order for things to run smoothly, testing requests must be made 1 week prior. This seems pretty harsh I know, but there really is no better way. The big problem we always have is planning. Maps requested for testing will be added to the server as soon as possible. This has to be done manually by an admin b/c of the aforementioned abuse of the direct upload service. Though I have an idea to get around it, for now you'll just have to tough it out.
3. You may not get sufficient testing on the day you request; don't freak out. Whether b/c of a low turnout or everyone gets tired after a couple hours. Simply post a request for the following week, saying only a couple peeps were available, or you only got like 5min. Such incidents will take priority during the next testing day. If there happen to be a dozen people looking for feedback that day, you'll have to be accommodating.
4. When requesting your test, the download must be available. Asking for some testing time and submitting your map a day before the event kinda defeats the purpose. In regards to multiple maps per author; this will be allowed if time permits. Should the testing schedule be rather large on that day, you'll have to settle for just one map.
5. Reread #1.