Kingfish

Group 1 / Section 3, Has anyone heard from or exchanged files with Overkill (martinoc@adelphia.net)? Did he respond to the comm check prior to the start of the tourney?

Group 1 / Section 3, Has anyone heard from or exchanged files with Overkill (martinoc@adelphia.net)? Did he respond to the comm check prior to the start of the tourney?

Hit shift-C (or Mac equivalent) a few times to scale up your units. Once done toggle the command to bring your units back down to realistic size. Edit: [ February 19, 2004, 02:07 PM: Message edited by: Kingfish ]

Hit shift-C (or Mac equivalent) a few times to scale up your units. Once done toggle the command to bring your units back down to realistic size. Edit: [ February 19, 2004, 02:07 PM: Message edited by: Kingfish ]

Hit shift-C (or Mac equivalent) a few times to scale up your units. Once done toggle the command to bring your units back down to realistic size. Edit: [ February 19, 2004, 02:07 PM: Message edited by: Kingfish ]

Kanonier Reichmann - troppo@internode.on.net

Kanonier Reichmann - troppo@internode.on.net

Kanonier Reichmann - troppo@internode.on.net

I'm sorry Ace, but this is not allowed. Although it is not outlined in the tourney manual, there exists an unwritten rule within every ROW. That rule states that every player in the tournament is expected, at all times, to make sure that his opponent's experience in the tournament is a living Hell. In fact, I would go so far as to say they are duty bound to ensure that is the case, with every opponent in every turn of every game. Furthermore, it is not enough that the players follow this unwritten rule, but they must also describe the process in clearly written documents, with optional screenshots of course. The only place for Chivalry in ROW is in the crosshairs of a Pak43, so I would strongly recommend that you get off your begging knee and start handing people their heads on a silver platter. Any questions?

I'm sorry Ace, but this is not allowed. Although it is not outlined in the tourney manual, there exists an unwritten rule within every ROW. That rule states that every player in the tournament is expected, at all times, to make sure that his opponent's experience in the tournament is a living Hell. In fact, I would go so far as to say they are duty bound to ensure that is the case, with every opponent in every turn of every game. Furthermore, it is not enough that the players follow this unwritten rule, but they must also describe the process in clearly written documents, with optional screenshots of course. The only place for Chivalry in ROW is in the crosshairs of a Pak43, so I would strongly recommend that you get off your begging knee and start handing people their heads on a silver platter. Any questions?

I'm sorry Ace, but this is not allowed. Although it is not outlined in the tourney manual, there exists an unwritten rule within every ROW. That rule states that every player in the tournament is expected, at all times, to make sure that his opponent's experience in the tournament is a living Hell. In fact, I would go so far as to say they are duty bound to ensure that is the case, with every opponent in every turn of every game. Furthermore, it is not enough that the players follow this unwritten rule, but they must also describe the process in clearly written documents, with optional screenshots of course. The only place for Chivalry in ROW is in the crosshairs of a Pak43, so I would strongly recommend that you get off your begging knee and start handing people their heads on a silver platter. Any questions?

Also keep in mind that getting the crew killed will prevent the vehicle from ever entering the game again, regardless of how high the vehicle repair setting is set at. Make it a habit of withdrawing your crew to a safe area in the rear.

Vadr, I've just sent you two more e-mails, one for each of the addresses you listed. Let me know if they arrive.

Vadr, I've just sent you two more e-mails, one for each of the addresses you listed. Let me know if they arrive.

Vadr, I've just sent you two more e-mails, one for each of the addresses you listed. Let me know if they arrive.

John, Try zipping the file, or whatever file compression program you use on a mac. That should prevent the body text gibberish.

John, Try zipping the file, or whatever file compression program you use on a mac. That should prevent the body text gibberish.

John, Try zipping the file, or whatever file compression program you use on a mac. That should prevent the body text gibberish.

Yes, all 5 scenarios have been sent out. Let me know which ones you have and I'll send you the one you are missing. My address is sc112265@bellsouth.net

Yes, all 5 scenarios have been sent out. Let me know which ones you have and I'll send you the one you are missing. My address is sc112265@bellsouth.net

Yes, all 5 scenarios have been sent out. Let me know which ones you have and I'll send you the one you are missing. My address is sc112265@bellsouth.net

I find it appropriate that we close out the first ROW IV thread with some kind words and a little pep talk from Winecape, whom we can never thank enough for his continued support and generosity. OK guys, This one is getting a bit top heavy. What say we all head on over here

OK, Here is our new home. In keeping with tradition we start it off with the general tournament rules *** ROW Tournament Rules The deadline for submitting scores is June 14th *** Followed by Holien's rules for AARs *** AAR’s and their role in ROW ROW stands above other tournaments as a tourney where we want to get all strands of the CM community playing (as yet) unreleased top quality scenarios. It offers a great reward for those who win the finals. For this opportunity to win wine and play scenarios not yet released to the general public the production of AAR’s is the price of your admission. If you fail to produce AAR’s for your games you will be excluded from playing in the finals. This simple change is designed to ensure that other players and scenario designers get some constructive feed back from your experience. To help you write an AAR here are some suggested headings or areas to cover. The Plan. What did you intend to do with your forces? How did you read the map? Explain your views on what you might be fighting against. How did you plan the game before starting to play it? The Reality. What happened? How did the plan survive the initial contact? What changes did you make to it? What went well what went poorly? Lessons Learned. What would you do differently? What worked well and badly for your opponent? Designer Notes Provide feedback to the designer. What did you like about the design? What would you change with the map or forces? The Effect on Final Scores Bonus points will be added to your final Tourney Score if you submit AAR's. Remember no AAR means no progression to the finals. Each full credit AAR will be worth 4% of the highest player's tourney score (before adding his AAR's). If you write five full credit AAR's you will receive additional tourney points equal to 20% of the highest player's tourney score. AAR's will receive either full credit or half credit. You must write more than just a few short paragraphs for full credit. We will let you know if an AAR is too short soon after you send it to me. You don't have to write a book either. Just cover the areas listed above and you will have it cracked. You could choose to write a piece on a scenario that is more of a Scenario review than an AAR if you want. The main thing we're looking for is constructive feedback. IMPORTANT How to Submit an AAR 1) AAR’s should never be sent in with game results. Send them in a separate email. 2) AAR’s can be .txt, .doc, or .pdf files. Do not write them in the body of an email. 3) AAR’s should not be more than 4 MB Uncompressed. Screenshots can cause you to go over this limit easily. We would recommend the .pdf format if you want to include several screenshots. 4) In the subject line of emails containing attached AAR’s, write your Username and the scenario name. For example: Madmatt, The Ambush Further Explanation The primary purpose of the AAR's is to provide the scenario designers with feedback on their work. If you've ever designed a scenario for the community, you know how rare it is to get this feedback. Writing AAR's is one way to express your thanks to the designers. Even negative feedback is welcome as long as it's constructive and not mean spirited. Another thing AAR’s do is help people learn to improve their tactics. Every scenario is played 36 times in a tourney such as this. There are 36 other people who had to deal with the same tactical situations you did. It can be very instructive to learn how others handled things, especially if you did worse than most. (BTW, all the AAR’s will be sent to you upon request once you have completed your games.) Lastly, by writing an AAR (or review) you are doing the community a small favour. This is because the designer can tweak the scenario based on feedback before releasing it to the community. Having a scenario played 36 times by 72 different people is a great test of a scenario. We think it's safe to say that very few, if any, scenarios get that degree of testing before they are put out to the public. Those of us who enjoy these tournaments need new scenarios (security). In return for these scenarios the designers should get the feedback they like. The Prize To help encourage AAR’s this year there will be a prize for the best AAR as judged by the players and organisers of the tourney. Not a big prize but something that will be worth winning. Your choice of any issue (still in print) of the magazine After the Battle. Check this site for details of this publication: - http://www.afterthebattle.com/ab-con1.html AAR UPDATE PLEASE READ ---> IMPORTANT INFORMATION Great news people are starting to send in their AAR's. Bad news is that I need you to provide a set header as explained below: - Please right at the start of the AAR very clearly do the following: - 1. Your Player Name (this is what you signed upto the tourney as.) 2. Your opponents Player Name. 3. Your Group and Section. 4. The name of the Scenario. 5. Your E-mail Address for responses about the AAR. IF YOU DO NOT DO THIS I will e-mail you and ask you to re submit it. I do not have the time to try and find out who you are. I need to file it as it arrives quickly and with the minimum of bother. There are far too many of you and games to add this potential burden! Please also send the AAR's direct to me. Do not send it to Kingfish or Spanish Bombs and expect them to send it on. We are trying to keep the flow of work to a minimum. All AAR's can be sent here: - Holien(at)9woodford(dot)Clara(Dot)Co.uk N.B. The AAR prize is open to all players who play the scenarios during the timeframe of ROW and write an AAR and submit it to me using the guidelines above. (It is not eligable to staff). We will be judging them on style, content and message. It does not have to be perfect English but you need to convey the message and we will try our best to understand you if English is not your first language. If in doubt please ask friends or native English speakers to check it for Typo's and use of language. We will not be judging it on spelling but on what it is saying and we need to understand what the author has typed! UK / US English differences will be tolerated. Any questions e-mail me. *** And last but not least Spanish Bomb's current list of replacements *** Replacement List: ON DECK: Platonov In the hole: RegSlaw Next in order: Nestor Levitacus John Osborne MG42 Vorishilov herrbixx Enqvist sandy AC BigMik1 [ March 23, 2004, 06:06 PM: Message edited by: Kingfish ]

OK, Here is our new home. In keeping with tradition we start it off with the general tournament rules *** ROW Tournament Rules The deadline for submitting scores is June 14th *** Followed by Holien's rules for AARs *** AAR’s and their role in ROW ROW stands above other tournaments as a tourney where we want to get all strands of the CM community playing (as yet) unreleased top quality scenarios. It offers a great reward for those who win the finals. For this opportunity to win wine and play scenarios not yet released to the general public the production of AAR’s is the price of your admission. If you fail to produce AAR’s for your games you will be excluded from playing in the finals. This simple change is designed to ensure that other players and scenario designers get some constructive feed back from your experience. To help you write an AAR here are some suggested headings or areas to cover. The Plan. What did you intend to do with your forces? How did you read the map? Explain your views on what you might be fighting against. How did you plan the game before starting to play it? The Reality. What happened? How did the plan survive the initial contact? What changes did you make to it? What went well what went poorly? Lessons Learned. What would you do differently? What worked well and badly for your opponent? Designer Notes Provide feedback to the designer. What did you like about the design? What would you change with the map or forces? The Effect on Final Scores Bonus points will be added to your final Tourney Score if you submit AAR's. Remember no AAR means no progression to the finals. Each full credit AAR will be worth 4% of the highest player's tourney score (before adding his AAR's). If you write five full credit AAR's you will receive additional tourney points equal to 20% of the highest player's tourney score. AAR's will receive either full credit or half credit. You must write more than just a few short paragraphs for full credit. We will let you know if an AAR is too short soon after you send it to me. You don't have to write a book either. Just cover the areas listed above and you will have it cracked. You could choose to write a piece on a scenario that is more of a Scenario review than an AAR if you want. The main thing we're looking for is constructive feedback. IMPORTANT How to Submit an AAR 1) AAR’s should never be sent in with game results. Send them in a separate email. 2) AAR’s can be .txt, .doc, or .pdf files. Do not write them in the body of an email. 3) AAR’s should not be more than 4 MB Uncompressed. Screenshots can cause you to go over this limit easily. We would recommend the .pdf format if you want to include several screenshots. 4) In the subject line of emails containing attached AAR’s, write your Username and the scenario name. For example: Madmatt, The Ambush Further Explanation The primary purpose of the AAR's is to provide the scenario designers with feedback on their work. If you've ever designed a scenario for the community, you know how rare it is to get this feedback. Writing AAR's is one way to express your thanks to the designers. Even negative feedback is welcome as long as it's constructive and not mean spirited. Another thing AAR’s do is help people learn to improve their tactics. Every scenario is played 36 times in a tourney such as this. There are 36 other people who had to deal with the same tactical situations you did. It can be very instructive to learn how others handled things, especially if you did worse than most. (BTW, all the AAR’s will be sent to you upon request once you have completed your games.) Lastly, by writing an AAR (or review) you are doing the community a small favour. This is because the designer can tweak the scenario based on feedback before releasing it to the community. Having a scenario played 36 times by 72 different people is a great test of a scenario. We think it's safe to say that very few, if any, scenarios get that degree of testing before they are put out to the public. Those of us who enjoy these tournaments need new scenarios (security). In return for these scenarios the designers should get the feedback they like. The Prize To help encourage AAR’s this year there will be a prize for the best AAR as judged by the players and organisers of the tourney. Not a big prize but something that will be worth winning. Your choice of any issue (still in print) of the magazine After the Battle. Check this site for details of this publication: - http://www.afterthebattle.com/ab-con1.html AAR UPDATE PLEASE READ ---> IMPORTANT INFORMATION Great news people are starting to send in their AAR's. Bad news is that I need you to provide a set header as explained below: - Please right at the start of the AAR very clearly do the following: - 1. Your Player Name (this is what you signed upto the tourney as.) 2. Your opponents Player Name. 3. Your Group and Section. 4. The name of the Scenario. 5. Your E-mail Address for responses about the AAR. IF YOU DO NOT DO THIS I will e-mail you and ask you to re submit it. I do not have the time to try and find out who you are. I need to file it as it arrives quickly and with the minimum of bother. There are far too many of you and games to add this potential burden! Please also send the AAR's direct to me. Do not send it to Kingfish or Spanish Bombs and expect them to send it on. We are trying to keep the flow of work to a minimum. All AAR's can be sent here: - Holien(at)9woodford(dot)Clara(Dot)Co.uk N.B. The AAR prize is open to all players who play the scenarios during the timeframe of ROW and write an AAR and submit it to me using the guidelines above. (It is not eligable to staff). We will be judging them on style, content and message. It does not have to be perfect English but you need to convey the message and we will try our best to understand you if English is not your first language. If in doubt please ask friends or native English speakers to check it for Typo's and use of language. We will not be judging it on spelling but on what it is saying and we need to understand what the author has typed! UK / US English differences will be tolerated. Any questions e-mail me. *** And last but not least Spanish Bomb's current list of replacements *** Replacement List: ON DECK: Platonov In the hole: RegSlaw Next in order: Nestor Levitacus John Osborne MG42 Vorishilov herrbixx Enqvist sandy AC BigMik1 [ March 23, 2004, 06:06 PM: Message edited by: Kingfish ]

OK, Here is our new home. In keeping with tradition we start it off with the general tournament rules *** ROW Tournament Rules The deadline for submitting scores is June 14th *** Followed by Holien's rules for AARs *** AAR’s and their role in ROW ROW stands above other tournaments as a tourney where we want to get all strands of the CM community playing (as yet) unreleased top quality scenarios. It offers a great reward for those who win the finals. For this opportunity to win wine and play scenarios not yet released to the general public the production of AAR’s is the price of your admission. If you fail to produce AAR’s for your games you will be excluded from playing in the finals. This simple change is designed to ensure that other players and scenario designers get some constructive feed back from your experience. To help you write an AAR here are some suggested headings or areas to cover. The Plan. What did you intend to do with your forces? How did you read the map? Explain your views on what you might be fighting against. How did you plan the game before starting to play it? The Reality. What happened? How did the plan survive the initial contact? What changes did you make to it? What went well what went poorly? Lessons Learned. What would you do differently? What worked well and badly for your opponent? Designer Notes Provide feedback to the designer. What did you like about the design? What would you change with the map or forces? The Effect on Final Scores Bonus points will be added to your final Tourney Score if you submit AAR's. Remember no AAR means no progression to the finals. Each full credit AAR will be worth 4% of the highest player's tourney score (before adding his AAR's). If you write five full credit AAR's you will receive additional tourney points equal to 20% of the highest player's tourney score. AAR's will receive either full credit or half credit. You must write more than just a few short paragraphs for full credit. We will let you know if an AAR is too short soon after you send it to me. You don't have to write a book either. Just cover the areas listed above and you will have it cracked. You could choose to write a piece on a scenario that is more of a Scenario review than an AAR if you want. The main thing we're looking for is constructive feedback. IMPORTANT How to Submit an AAR 1) AAR’s should never be sent in with game results. Send them in a separate email. 2) AAR’s can be .txt, .doc, or .pdf files. Do not write them in the body of an email. 3) AAR’s should not be more than 4 MB Uncompressed. Screenshots can cause you to go over this limit easily. We would recommend the .pdf format if you want to include several screenshots. 4) In the subject line of emails containing attached AAR’s, write your Username and the scenario name. For example: Madmatt, The Ambush Further Explanation The primary purpose of the AAR's is to provide the scenario designers with feedback on their work. If you've ever designed a scenario for the community, you know how rare it is to get this feedback. Writing AAR's is one way to express your thanks to the designers. Even negative feedback is welcome as long as it's constructive and not mean spirited. Another thing AAR’s do is help people learn to improve their tactics. Every scenario is played 36 times in a tourney such as this. There are 36 other people who had to deal with the same tactical situations you did. It can be very instructive to learn how others handled things, especially if you did worse than most. (BTW, all the AAR’s will be sent to you upon request once you have completed your games.) Lastly, by writing an AAR (or review) you are doing the community a small favour. This is because the designer can tweak the scenario based on feedback before releasing it to the community. Having a scenario played 36 times by 72 different people is a great test of a scenario. We think it's safe to say that very few, if any, scenarios get that degree of testing before they are put out to the public. Those of us who enjoy these tournaments need new scenarios (security). In return for these scenarios the designers should get the feedback they like. The Prize To help encourage AAR’s this year there will be a prize for the best AAR as judged by the players and organisers of the tourney. Not a big prize but something that will be worth winning. Your choice of any issue (still in print) of the magazine After the Battle. Check this site for details of this publication: - http://www.afterthebattle.com/ab-con1.html AAR UPDATE PLEASE READ ---> IMPORTANT INFORMATION Great news people are starting to send in their AAR's. Bad news is that I need you to provide a set header as explained below: - Please right at the start of the AAR very clearly do the following: - 1. Your Player Name (this is what you signed upto the tourney as.) 2. Your opponents Player Name. 3. Your Group and Section. 4. The name of the Scenario. 5. Your E-mail Address for responses about the AAR. IF YOU DO NOT DO THIS I will e-mail you and ask you to re submit it. I do not have the time to try and find out who you are. I need to file it as it arrives quickly and with the minimum of bother. There are far too many of you and games to add this potential burden! Please also send the AAR's direct to me. Do not send it to Kingfish or Spanish Bombs and expect them to send it on. We are trying to keep the flow of work to a minimum. All AAR's can be sent here: - Holien(at)9woodford(dot)Clara(Dot)Co.uk N.B. The AAR prize is open to all players who play the scenarios during the timeframe of ROW and write an AAR and submit it to me using the guidelines above. (It is not eligable to staff). We will be judging them on style, content and message. It does not have to be perfect English but you need to convey the message and we will try our best to understand you if English is not your first language. If in doubt please ask friends or native English speakers to check it for Typo's and use of language. We will not be judging it on spelling but on what it is saying and we need to understand what the author has typed! UK / US English differences will be tolerated. Any questions e-mail me. *** And last but not least Spanish Bomb's current list of replacements *** Replacement List: ON DECK: Platonov In the hole: RegSlaw Next in order: Nestor Levitacus John Osborne MG42 Vorishilov herrbixx Enqvist sandy AC BigMik1 [ March 23, 2004, 06:06 PM: Message edited by: Kingfish ]