https://www.theblitz.club/message_boards/ Sat, 02 May 2026 07:47:38 +0000 MyBB https://www.theblitz.club/message_boards/showthread.php?tid=60682 Mon, 02 Jan 2012 20:57:32 +0000 Kool Kat]]> https://www.theblitz.club/message_boards/showthread.php?tid=60682

This is an archive of the 2010 and earlier CS H2H Section threads. It is searchable and viewable... but please do not post here! ]]>

This is an archive of the 2010 and earlier CS H2H Section threads. It is searchable and viewable... but please do not post here! ]]> https://www.theblitz.club/message_boards/showthread.php?tid=56715 Tue, 31 Aug 2010 23:41:54 +0000 Herr Straße Laufer]]> https://www.theblitz.club/message_boards/showthread.php?tid=56715
28 July 1941
Velikiye Luki, 220km NW of Smolensk:[Version 1.0][HISB-HYPO][EA
or not] [N V V] As the strategic push for Moscow moves forward
the Germans try to create a huge "Kessel". It was not always
about defeating the Russians that they faced locally, it was
more gobbling up pieces of ground, surrounding large formations,
and cutting them off. On the operational maps the German Army
Command saw large "kettles" that were full of Russian soldiers
waiting to be trapped. In this battle a reinforced German Regiment
tries to break through a fortress town in an effort to grasp
the handle of the larger Kessel of Smolensk. This German force
is tasked to push aside the town garrison and continue driving
Eastward. The Russians must hold onto this "fortress" to prevent
the Germans from "putting the lid on the kettle". Later in the
war this area was one where the Germans would fight a defensive
battle against overwhelming odds, in the snow, to keep the Russians
from making a kettle. As for now they must simply push aside
Russian resistance and close the lid.

  Editadel.zip (Size: 36.84 KB / Downloads: 6) ]]>
28 July 1941
Velikiye Luki, 220km NW of Smolensk:[Version 1.0][HISB-HYPO][EA
or not] [N V V] As the strategic push for Moscow moves forward
the Germans try to create a huge "Kessel". It was not always
about defeating the Russians that they faced locally, it was
more gobbling up pieces of ground, surrounding large formations,
and cutting them off. On the operational maps the German Army
Command saw large "kettles" that were full of Russian soldiers
waiting to be trapped. In this battle a reinforced German Regiment
tries to break through a fortress town in an effort to grasp
the handle of the larger Kessel of Smolensk. This German force
is tasked to push aside the town garrison and continue driving
Eastward. The Russians must hold onto this "fortress" to prevent
the Germans from "putting the lid on the kettle". Later in the
war this area was one where the Germans would fight a defensive
battle against overwhelming odds, in the snow, to keep the Russians
from making a kettle. As for now they must simply push aside
Russian resistance and close the lid.

  Editadel.zip (Size: 36.84 KB / Downloads: 6) ]]> https://www.theblitz.club/message_boards/showthread.php?tid=56714 Tue, 31 Aug 2010 23:20:39 +0000 Herr Straße Laufer]]> https://www.theblitz.club/message_boards/showthread.php?tid=56714
Novgorod, 170km SSE of Leningrad: [Version 1.0] [H2H](Hypo-HISB)[EA or no][N V V] The Russians begin Operation Iskra, "The Spark". 2nd Shock Army is tasked with gaining a bridgehead. The Spanish volunteers "Azul", those from the Spanish Blue division who remained with the German army, have been battling in this sector for quite some time. The German command knows that they can count on the Spanish. These volunteers have learned to fight as well as their German counterparts. They are tough as they come but, can they hold the line against the crush of so many Russians who desire their elimination. The "volunteers" have been shifting some assets and preparing for withdrawl to new lines when the Russians finally struck. The frantic calls of incoming tanks and Russian air attacks fill the radio net. The Spanish soon learn that this is the real thing and not a probing attack. All the "blues" wonder where this will lead.

Here is the link for any who want to try it out. Please let me know what you think of it? :chin:

**The Spark on the Blues



HSL]]>
Novgorod, 170km SSE of Leningrad: [Version 1.0] [H2H](Hypo-HISB)[EA or no][N V V] The Russians begin Operation Iskra, "The Spark". 2nd Shock Army is tasked with gaining a bridgehead. The Spanish volunteers "Azul", those from the Spanish Blue division who remained with the German army, have been battling in this sector for quite some time. The German command knows that they can count on the Spanish. These volunteers have learned to fight as well as their German counterparts. They are tough as they come but, can they hold the line against the crush of so many Russians who desire their elimination. The "volunteers" have been shifting some assets and preparing for withdrawl to new lines when the Russians finally struck. The frantic calls of incoming tanks and Russian air attacks fill the radio net. The Spanish soon learn that this is the real thing and not a probing attack. All the "blues" wonder where this will lead.

Here is the link for any who want to try it out. Please let me know what you think of it? :chin:

**The Spark on the Blues



HSL]]> https://www.theblitz.club/message_boards/showthread.php?tid=56319 Fri, 16 Jul 2010 09:56:38 +0000 Herr Straße Laufer]]> https://www.theblitz.club/message_boards/showthread.php?tid=56319 Your scenario, **Forty-Five clicks to Moscow, has been approved and now resides in the Campaign Series dBASE.

**Forty-Five clicks to Moscow

8 December, 1941
Malkovleska, Russia] [H2H/ALLIES] [FIC] [GD] [Version 2.0] On the morning of December 8th, the situation became critical as elements of the Soviet 8th Mechanized Corps moved to engage strung out elements of the LVI Panzer Corps NW of Moscow! The 7th Panzer and 14th Motorized bore the brunt of the assault while holding a line from Sabalko to Ankreska. Elements of the 14th Motorized were pushed out of Ankreska and fell back to the Forest of the same name. The Soviets not wanting to get bogged down in a forest fight positioned a blocking force in front of this region and moved the bulk of their force towards the center of the German MLR. At Malkovleska, the center of the line, 7th Panzer troops were hard pressed as repeated Soviet attacks fell upon their position. With most of their organic transport and heavy weapons destroyed surviving elements of the 7th Mot. Reg/7th Panzer were forced to fall back towards Sabalko. They continued to fight a desperate delaying action until tanks from the 25th Pz. Reg./7th Panzer arrived later that morning to check the Soviet advance!


Thanks to the designers who take the time to create new and interesting PBEM scenarios that keep CS fresh. Thanks to those testers who help the designers to achieve balance.



HSL]]> Your scenario, **Forty-Five clicks to Moscow, has been approved and now resides in the Campaign Series dBASE.

**Forty-Five clicks to Moscow

8 December, 1941
Malkovleska, Russia] [H2H/ALLIES] [FIC] [GD] [Version 2.0] On the morning of December 8th, the situation became critical as elements of the Soviet 8th Mechanized Corps moved to engage strung out elements of the LVI Panzer Corps NW of Moscow! The 7th Panzer and 14th Motorized bore the brunt of the assault while holding a line from Sabalko to Ankreska. Elements of the 14th Motorized were pushed out of Ankreska and fell back to the Forest of the same name. The Soviets not wanting to get bogged down in a forest fight positioned a blocking force in front of this region and moved the bulk of their force towards the center of the German MLR. At Malkovleska, the center of the line, 7th Panzer troops were hard pressed as repeated Soviet attacks fell upon their position. With most of their organic transport and heavy weapons destroyed surviving elements of the 7th Mot. Reg/7th Panzer were forced to fall back towards Sabalko. They continued to fight a desperate delaying action until tanks from the 25th Pz. Reg./7th Panzer arrived later that morning to check the Soviet advance!


Thanks to the designers who take the time to create new and interesting PBEM scenarios that keep CS fresh. Thanks to those testers who help the designers to achieve balance.



HSL]]> https://www.theblitz.club/message_boards/showthread.php?tid=55957 Thu, 10 Jun 2010 22:20:48 +0000 Herr Straße Laufer]]> https://www.theblitz.club/message_boards/showthread.php?tid=55957 ** Baring Their Teeth has been moved to the approved scenarios listing.

I hope that you all remain active in testing future scenarios. :thumbs_up:
I also hope that others will join in and help get scenarios through the H2H process! :smoke:

I hope others will try it out and make comments upon it. :chin:



HSL]]> ** Baring Their Teeth has been moved to the approved scenarios listing.

I hope that you all remain active in testing future scenarios. :thumbs_up:
I also hope that others will join in and help get scenarios through the H2H process! :smoke:

I hope others will try it out and make comments upon it. :chin:



HSL]]> https://www.theblitz.club/message_boards/showthread.php?tid=55651 Sun, 09 May 2010 13:45:19 +0000 Crossroads]]> https://www.theblitz.club/message_boards/showthread.php?tid=55651
Having been with you for almost a year now, I believe I can finally begin to develop a couple of new scenarios from the less known Finno-Russian front.

JTCS/EFII comes stocked by a couple of scenarios covering Winter War. There are also one historical and one hypothetical (sp?) scenario covering the attack phase of 1941 during the Continuation War as the Finns decided to join Barbarossa, after the bitter peace terms of Winter War.

I've started to put together a 10x15 km map, thanks to Huib's documents it has started better than I thought: Google Earth for proper elevations, lakes, rivers; contemporary maps for original infrastructure,...

I have just started to sketch the time line of events I am trying to represent in the scenario. Let us see how that one goes. I believe I have plenty of information already available, but knowing the guys at AHF let us see what else can be found here. http://forum.axishistory.com/viewtopic.p...9&t=165897

As a next step, I will start putting up the OOB. I've got a pretty good picture of what units participated from each side, and what were the historical results.

What I would just love to have is to have someone I can send the OOB and SCN files to have a look at times I hit the proverbial brick wall with these tools...

OOB: adding leaders to units
SCN: timing releases and arrivals, changing strenght of a large number of units to lower, ...

The final outcome should hopefully be a fun and balanced scenario from the 1944 era, when Russians had a fine mobile arsenal to use, and even Finns had something else than just their ski poles they could stick their enemies into eye with.

The first scenario would be the "Thermopylae" fighting at Kuuterselka, where instead of 300, a truly amazing number of men and equipment battled it out during the initial phases of Soviet summer offensive against Finland.

Here's the map (90% ready, I will need to add a click or two to west to have more room for maneuver there) as a teaser. Soviet right pincer to take Kuuterselka and move towards north to Liikola and Kanneljarvi, left pincer to turn to Mustamaki and advance via railroad towards Viborg. Finns counterattacking them at all places with everything including their kitchen sinks.

Should the Russians manage a breakthrough (as historically they did), the whole of the Finnish defensive VT Line running through the Karelian Isthmus would be compromised (as it was).



Edit: Map now 12km x 15.5km.]]>
Having been with you for almost a year now, I believe I can finally begin to develop a couple of new scenarios from the less known Finno-Russian front.

JTCS/EFII comes stocked by a couple of scenarios covering Winter War. There are also one historical and one hypothetical (sp?) scenario covering the attack phase of 1941 during the Continuation War as the Finns decided to join Barbarossa, after the bitter peace terms of Winter War.

I've started to put together a 10x15 km map, thanks to Huib's documents it has started better than I thought: Google Earth for proper elevations, lakes, rivers; contemporary maps for original infrastructure,...

I have just started to sketch the time line of events I am trying to represent in the scenario. Let us see how that one goes. I believe I have plenty of information already available, but knowing the guys at AHF let us see what else can be found here. http://forum.axishistory.com/viewtopic.p...9&t=165897

As a next step, I will start putting up the OOB. I've got a pretty good picture of what units participated from each side, and what were the historical results.

What I would just love to have is to have someone I can send the OOB and SCN files to have a look at times I hit the proverbial brick wall with these tools...

OOB: adding leaders to units
SCN: timing releases and arrivals, changing strenght of a large number of units to lower, ...

The final outcome should hopefully be a fun and balanced scenario from the 1944 era, when Russians had a fine mobile arsenal to use, and even Finns had something else than just their ski poles they could stick their enemies into eye with.

The first scenario would be the "Thermopylae" fighting at Kuuterselka, where instead of 300, a truly amazing number of men and equipment battled it out during the initial phases of Soviet summer offensive against Finland.

Here's the map (90% ready, I will need to add a click or two to west to have more room for maneuver there) as a teaser. Soviet right pincer to take Kuuterselka and move towards north to Liikola and Kanneljarvi, left pincer to turn to Mustamaki and advance via railroad towards Viborg. Finns counterattacking them at all places with everything including their kitchen sinks.

Should the Russians manage a breakthrough (as historically they did), the whole of the Finnish defensive VT Line running through the Karelian Isthmus would be compromised (as it was).



Edit: Map now 12km x 15.5km.]]> https://www.theblitz.club/message_boards/showthread.php?tid=55324 Sat, 10 Apr 2010 15:03:08 +0000 Herr Straße Laufer]]> https://www.theblitz.club/message_boards/showthread.php?tid=55324
** The Spark on the Blues

11 January, 1943

Novgorod, 170km SSE of Leningrad: [Version 1.0] [H2H](Hypo-HISB)[EA or no][N V V] The Russians begin Operation Iskra, The Spark. 2nd Shock Army is tasked with gaining a bridgehead. The Spanish volunteers "Azul", those from the Spanish Blue division who remained with the German army, have been battling in this sector for quite some time. The German command knows that they can count on the Spanish. These volunteers have learned to fight as well as their German counterparts. They are tough as they come but, can they hold the line against the crush of so many Russians who desire their elimination. The "volunteers" have been shifting some assets and preparing for withdraw to new lines when the Russians finally struck. The frantic calls of incoming tanks and Russian air attacks fill the radio net. The Spanish soon learn that this is the real thing and not a probing attack. All the "blues" wonder where this will lead.


** Baring Their Teeth

15 October, 1941

Butyrki, 90km N of Kursk:[Version 2.0][H2H][Hypo-HISB] [EA or not][N V V] Hitler's shift of Guderian's Panzer Group into the Ukraine caused a delay for Army Group Center's, and it's own participation, in the attack on Moscow. In order to shift out of the Ukraine and turn Northeast toward Moscow a small battle was fought on ground that was to be recognized almost a year and a half later. The small town of Butyrki was to be the site of this battle. At Butyrki the Russians collected some mixed forces to block roads and stall the German advance. Russian units decimated by earlier German victories, were cobbled together and reinforced by militia groups that were pressed into service to save the Motherland. No cheering here by local's who wished to be "liberated" by the marching German forces. The Russians settled in to delay and resist, using tactics that would slow down and stall all movement that could take Germans soldiers closer to Moscow. As the Germans moved through Butyrki the Russians bared their teeth. A grimace or the smile became a frightening symbol of Russian resistance.

____________________________
Each scenario is 20 turns long and SM 3 (club sm). Look for their posting to the testing area. I'd like to hear any and all tester feedback. These two scenarios have been played out by a varied number of personal member/friends and they should be close to balanced. But, I want non-biased eyes to give them a try. Even those who have already tested them can sign up and have an experience against other opponents. :chin:

Testers who will stick with the tests should sign up. I'd just like you to let me know what you think? :smoke:



HSL]]>
** The Spark on the Blues

11 January, 1943

Novgorod, 170km SSE of Leningrad: [Version 1.0] [H2H](Hypo-HISB)[EA or no][N V V] The Russians begin Operation Iskra, The Spark. 2nd Shock Army is tasked with gaining a bridgehead. The Spanish volunteers "Azul", those from the Spanish Blue division who remained with the German army, have been battling in this sector for quite some time. The German command knows that they can count on the Spanish. These volunteers have learned to fight as well as their German counterparts. They are tough as they come but, can they hold the line against the crush of so many Russians who desire their elimination. The "volunteers" have been shifting some assets and preparing for withdraw to new lines when the Russians finally struck. The frantic calls of incoming tanks and Russian air attacks fill the radio net. The Spanish soon learn that this is the real thing and not a probing attack. All the "blues" wonder where this will lead.


** Baring Their Teeth

15 October, 1941

Butyrki, 90km N of Kursk:[Version 2.0][H2H][Hypo-HISB] [EA or not][N V V] Hitler's shift of Guderian's Panzer Group into the Ukraine caused a delay for Army Group Center's, and it's own participation, in the attack on Moscow. In order to shift out of the Ukraine and turn Northeast toward Moscow a small battle was fought on ground that was to be recognized almost a year and a half later. The small town of Butyrki was to be the site of this battle. At Butyrki the Russians collected some mixed forces to block roads and stall the German advance. Russian units decimated by earlier German victories, were cobbled together and reinforced by militia groups that were pressed into service to save the Motherland. No cheering here by local's who wished to be "liberated" by the marching German forces. The Russians settled in to delay and resist, using tactics that would slow down and stall all movement that could take Germans soldiers closer to Moscow. As the Germans moved through Butyrki the Russians bared their teeth. A grimace or the smile became a frightening symbol of Russian resistance.

____________________________
Each scenario is 20 turns long and SM 3 (club sm). Look for their posting to the testing area. I'd like to hear any and all tester feedback. These two scenarios have been played out by a varied number of personal member/friends and they should be close to balanced. But, I want non-biased eyes to give them a try. Even those who have already tested them can sign up and have an experience against other opponents. :chin:

Testers who will stick with the tests should sign up. I'd just like you to let me know what you think? :smoke:



HSL]]> https://www.theblitz.club/message_boards/showthread.php?tid=55216 Tue, 30 Mar 2010 17:57:54 +0000 Kool Kat]]> https://www.theblitz.club/message_boards/showthread.php?tid=55216
Testing has been closed.

Game has been uploaded into Blitz game database as a "non-H2H" scenario. You may download the game files HERE.

Final Version

* Added 1x 37mm AT (Ethiopians)
* Added calvary company (Ethiopians)
* Added improved positions to the 4 objective hexes
* Ethiopian artillery starts in improved positions
* Hexes 9,13 and 8,13 are kunai to block Italian LOS to arriving Ethiopian reinforcements
* Added explanation of Ethiopian Retinue units in scenario description
* Increased "Major Victory" points by 25. It takes 225 points for a "Major Victory"

Many thanks to all play testers! ]]>
Testing has been closed.

Game has been uploaded into Blitz game database as a "non-H2H" scenario. You may download the game files HERE.

Final Version

* Added 1x 37mm AT (Ethiopians)
* Added calvary company (Ethiopians)
* Added improved positions to the 4 objective hexes
* Ethiopian artillery starts in improved positions
* Hexes 9,13 and 8,13 are kunai to block Italian LOS to arriving Ethiopian reinforcements
* Added explanation of Ethiopian Retinue units in scenario description
* Increased "Major Victory" points by 25. It takes 225 points for a "Major Victory"

Many thanks to all play testers! ]]> https://www.theblitz.club/message_boards/showthread.php?tid=55014 Thu, 11 Mar 2010 14:08:08 +0000 Kool Kat]]> https://www.theblitz.club/message_boards/showthread.php?tid=55014
IMHO, it is important that designers; prior to uploading their new designs into H2H, run intial test games against both the AI and a few regular opponents.

This will help identify and shake out any "gross abnormalities" (e.g. skewed victory conditions, strange unit starting positions, terrain that does not make sense, etc.)

Some of my earlier scenario designs, I did not follow these initial steps... and as the play testers began their test games... these "gross abnormalities" began very evident :eek1: ...and I mentally "kicked myself" for not being aware of these issues... and having to spend (at least) another test round ironing them out. :mad:

I also believe that a scenario design that goes through an initial "shake down" prior to uploading into H2H will also test "better"... and while players who test H2H designs are not playing the scenario to "play it," but looking more to review the design for a number of variables, players may get more "enjoyment" out of testing a design that plays better intially then one that does not? :chin:

Maybe one reason more players don't step forward to help play test H2H designs is the "fear" that their time will be "wasted" on a poor design? :chin:

Obviously, scenarios in H2H are "designs in progress" that will go through multiple revisions and are not the ultimate, final product. But, IMHO, a designer who takes these initial steps in the design process, will reap more rewards during the "formal" H2H phase. :smoke:]]>
IMHO, it is important that designers; prior to uploading their new designs into H2H, run intial test games against both the AI and a few regular opponents.

This will help identify and shake out any "gross abnormalities" (e.g. skewed victory conditions, strange unit starting positions, terrain that does not make sense, etc.)

Some of my earlier scenario designs, I did not follow these initial steps... and as the play testers began their test games... these "gross abnormalities" began very evident :eek1: ...and I mentally "kicked myself" for not being aware of these issues... and having to spend (at least) another test round ironing them out. :mad:

I also believe that a scenario design that goes through an initial "shake down" prior to uploading into H2H will also test "better"... and while players who test H2H designs are not playing the scenario to "play it," but looking more to review the design for a number of variables, players may get more "enjoyment" out of testing a design that plays better intially then one that does not? :chin:

Maybe one reason more players don't step forward to help play test H2H designs is the "fear" that their time will be "wasted" on a poor design? :chin:

Obviously, scenarios in H2H are "designs in progress" that will go through multiple revisions and are not the ultimate, final product. But, IMHO, a designer who takes these initial steps in the design process, will reap more rewards during the "formal" H2H phase. :smoke:]]> https://www.theblitz.club/message_boards/showthread.php?tid=54880 Wed, 24 Feb 2010 15:55:58 +0000 Kool Kat]]> https://www.theblitz.club/message_boards/showthread.php?tid=54880
I'm starting some initial research and scenario design for the "First Battle of Tembien" (January 20, 1936) depicting the Italian invasion of Ethiopia.

Need a good, topographical map of northern Ethiopia especially around the Warieu Pass region.

Looked through the WF stock maps, but did not see a ready-made map of that region. Maybe I missed it?

Any suggestions and/or pointers would be greatly appreciated! :bow:]]>
I'm starting some initial research and scenario design for the "First Battle of Tembien" (January 20, 1936) depicting the Italian invasion of Ethiopia.

Need a good, topographical map of northern Ethiopia especially around the Warieu Pass region.

Looked through the WF stock maps, but did not see a ready-made map of that region. Maybe I missed it?

Any suggestions and/or pointers would be greatly appreciated! :bow:]]> https://www.theblitz.club/message_boards/showthread.php?tid=54830 Fri, 19 Feb 2010 20:24:28 +0000 Kool Kat]]> https://www.theblitz.club/message_boards/showthread.php?tid=54830
It will be in this thread that I keep a running list of all revisions / changes that have been identified by the Terror on Tarakan play testers.

Many thanks to all play testers for your feedback!

Terror on Tarakan ver. 1.0 - Round 1 testing has closed. I will gather play tester feedback as games conclude and input feedback into Terror on Tarakan ver. 1.1 (2/20/2010)

Current game version testing (Version 1.0)

Terror on Tarakan (Version 1.1)

1. Add No Banzai to scenario description.
2. Set Japanese OP fire to zero (sniper and 1st line garrison platoons)
3. Add scenario photo
4. Replace Light Recon unit (Allied) with higher strength unit (e.g. a Wasp or Bren MG Carrier)
5. Add ** to scenario name ----> ** Terror on Tarakan]]>
It will be in this thread that I keep a running list of all revisions / changes that have been identified by the Terror on Tarakan play testers.

Many thanks to all play testers for your feedback!

Terror on Tarakan ver. 1.0 - Round 1 testing has closed. I will gather play tester feedback as games conclude and input feedback into Terror on Tarakan ver. 1.1 (2/20/2010)

Current game version testing (Version 1.0)

Terror on Tarakan (Version 1.1)

1. Add No Banzai to scenario description.
2. Set Japanese OP fire to zero (sniper and 1st line garrison platoons)
3. Add scenario photo
4. Replace Light Recon unit (Allied) with higher strength unit (e.g. a Wasp or Bren MG Carrier)
5. Add ** to scenario name ----> ** Terror on Tarakan]]> https://www.theblitz.club/message_boards/showthread.php?tid=54814 Thu, 18 Feb 2010 13:39:04 +0000 Kool Kat]]> https://www.theblitz.club/message_boards/showthread.php?tid=54814
Quality H2H scenarios can be produced ONLY if players agree to help play test game designs.

It is really that simple... and that difficult to accomplish. :chin:

It is a partnership. An agreement between the scenario designer and the CS player community.

As a scenario designer, I pledge to do the following:

* Research the historical battle
* Develop an accurate map
* Produce OOB's for both sides
* Play test scenario (both sides) against the AI
* Play test scenario (both sides) against a few regular opponents

But, here is what I need from players - especially folks who want to see new content and quality H2H scenarios...

* Need players willing to help play test new scenario designs

Do you want quality H2H scenarios... or not?

Designers certainly don't have to go through the H2H process. I can "slap" a new scenario together in a few hours and upload it into the scenario database... but is that what CS players really want? :eek1:

I think all players can point to standard CS scenarios that are "lacking" in some aspect... and I can almost guarantee those designs that fall short, did NOT go through quality play testing by multiple players.

And, yep, I bet we can all come up with excuses as to why we don't step up to help test new designs... but if CS players don't step up... where does the blame for lack of new content and scenarios fall upon?

A play tester recently confessed to me:

"One reason I do not play much RS is due to a lack of scenarios."

There are currently 15 new CS scenario designs sitting in H2H waiting for test game players. There is your new content!

Again, it is really very simple. You want new content and scenarios... then many more CS players need to step forward and make it happen.]]>
Quality H2H scenarios can be produced ONLY if players agree to help play test game designs.

It is really that simple... and that difficult to accomplish. :chin:

It is a partnership. An agreement between the scenario designer and the CS player community.

As a scenario designer, I pledge to do the following:

* Research the historical battle
* Develop an accurate map
* Produce OOB's for both sides
* Play test scenario (both sides) against the AI
* Play test scenario (both sides) against a few regular opponents

But, here is what I need from players - especially folks who want to see new content and quality H2H scenarios...

* Need players willing to help play test new scenario designs

Do you want quality H2H scenarios... or not?

Designers certainly don't have to go through the H2H process. I can "slap" a new scenario together in a few hours and upload it into the scenario database... but is that what CS players really want? :eek1:

I think all players can point to standard CS scenarios that are "lacking" in some aspect... and I can almost guarantee those designs that fall short, did NOT go through quality play testing by multiple players.

And, yep, I bet we can all come up with excuses as to why we don't step up to help test new designs... but if CS players don't step up... where does the blame for lack of new content and scenarios fall upon?

A play tester recently confessed to me:

"One reason I do not play much RS is due to a lack of scenarios."

There are currently 15 new CS scenario designs sitting in H2H waiting for test game players. There is your new content!

Again, it is really very simple. You want new content and scenarios... then many more CS players need to step forward and make it happen.]]> https://www.theblitz.club/message_boards/showthread.php?tid=54778 Sun, 14 Feb 2010 15:39:03 +0000 Herr Straße Laufer]]> https://www.theblitz.club/message_boards/showthread.php?tid=54778 What is the Designer's role?
Once the scenario is moved to the main test page it is the designer's role to arrange for players to test his scenario. This is best achieved by posting for testers on the relevant forums and ensuring the testers register any tests started (see below). You will also need to liaise with your testers to see how things are progressing, every time a test report is submitted you will be notified by email, so ensure your email address is correctly displayed on your member page. The test reports can also be accessed through the scenario listing at the testing area and through the My Scenarios page.

Note: Active designers need to get members to test the scenario.

Once you receive feedback and the current round of tests are completed, you can update the scenario file through the My Scenarios (see below) link. Taking feedback and uploading new versions of your scenario is very important to keep your scenario project moving forward.

Note: When you update the scenario let everyone know. Also put a version number in the scenario description (it can be removed later prior to being moved to the approved area). Remember to keep an open mind when viewing feedback. The testers are trying to help you.

The greatest issue the H2H Area has is designers uploading scenarios and then not fulfilling their role as set out above. Not only does this create a "log jam" of scenarios on the test page it also causes extra admin work for the H2H custodians. Any scenarios found to be abandoned on the test page by their designer will be deleted and that designer may not be allowed to upload new scenarios in the future!

*Please don't upload scenarios if you don't intend to have them tested*

Note: This is not meant to be punitive against any one designer. It is meant to keep things moving. We will be sending out e-mails shortly, to those who have designs in the testing area, to find out which designer is interested in supporting it or having it removed. As previously stated the H2H Custodians are willing to upload the scenario into the Scenario dBASE so that your work will not be lost. And, your scenario can be downloaded and rated through play.

Can a designer test his own scenarios?
This might sound unwise but it has been proved that having the designer involved in the testing can have real benefits to keeping a project moving. If you would like to test your own scenario you should contact Foul. who will discuss this further.

Note: I believe that you can also contact John and I. I usually play test my scenarios once from each side against the AI and then against Humans prior to adding them to the dBASE. I have also tested my own in the H2H area. Sometimes an opponent who is not from your regular pool can show you things that you do not often see. It helps to get as many perspectives as possible?

How does a scenario pass through testing and become Approved?
For a scenario to become approved the scenario requires four reports which rate the scenario with an average score of 8 or more, at that point the scenario can be approved provided there are no other tests registered against it, the scenario is moved to the Approved list using a link located in My Scenarios (see below).

If all the tests are finished and the scenario is still not approved the designer can make changes and upload a new version of the scenario using the My Scenarios link and a new round of testing can begin. This continues until the scenario achieves the required score to become approved.

Note: Sounds tedious but works quite nicely. Especially when the testers commit themselves to also be active.

What is the 'My Scenarios' link for?
This link is a powerful tool that all designers need to know how to use properly, the page lists all of your uploaded scenarios in the testing area and allows you to change almost all aspects of those scenarios. The link is only active while you have scenarios uploaded in the testing area.

The page is self explanatory, but here are some tips...

1. You cannot upload and replace an existing scenario file while any tests are registered against that scenario.
2. You can prevent any new tests being registered against your scenario by changing the 'Testing In Progress' box to 'Testing Stopped', you will need to do this when either you have enough tests running or you are waiting for current test to finish so you can modify or approve the scenario. If you modify the scenario remember to change this box back to 'Testing in progress' to allow tests on the new version to be registered.
3. When your scenario has the required score a link will appear in the 'Approve' box to allow you to move it to the Approved list.

How do testers register their tests on my scenario?
Testers register their tests at the scenario listing on the test page. This is important as having tests registered against your scenario shows the custodians that your scenario is currently under active testing.

Why is a correct Email address so important?
It is important that your correct email address is listed under your Blitz profile as all of the automated messages generated by the H2H area for feedback or points awarded is sent to this email address. Also testers with questions may try to contact you this way.

My scenario has achieved the required score but I cannot approve it, why?
This will be because there are still tests registered against the scenario, testing is done in "rounds" and it is only once a round of testing is finished will you be able to update or approved your scenario. If your scenario is stuck due to unreliable testers then contact Foul. who will help you remove the log jam.

My scenario cannot be updated?
See above.

Can a scenario be too large for the H2H Test Area?
Yes it can. A scenario which the custodian estimates would take longer than approximately one year to test will not be allowed past the holding area. If you have any doubts about the size of your scenario ask the relevant custodian before you upload the scenario.

Note: Just keeping the testing active will help to move even that largest scenarios along. If there is no action the large ones will be treated as any other inactive test scenario.

What bonus points will I earn?
Designers are awarded 20 points per Size Modifier once their scenario is moved to the approved list.

How does the rating formula work?
The rating formula for the scenario average score is
(balance*1.6)+(enjoyment*1.2)+(briefings*0.2)/3

Balance carries the most weight followed by enjoyment, while the briefings score has least weighting. There is guidance on the report to indicate to testers that the briefing should be scored highly if informative and complete.

Why am I only allowed to have 3 scenarios uploaded?
This is to prevent designers hogging all the available space on the test page, the best way to upload new scenarios is to get your present ones approved!

Note:This can be the most frustrating part for the designer. Keeping in active touch with the testers help to move scenarios along and allow more scenarios to be uploaded as existing ones attain approval.

I no longer wish to have my scenario on the test page?
Contact Foul. who will delete your scenario.

Any tricks of the trade?

1. Consider forming your own test group of testers who you can trust to be reliable and provide useful feedback.
2. Consider only having three tests registered against your scenario to keep things manageable and use the 'Testing stopped' feature to prevent any more tests being run until you are ready to approve or update the scenario.
3. Make sure any tests are registered as this will show the custodians that there is testing taking place with your scenario.
4. Any problems or queries contact Foul. who will do everything he can to help you out.

Note:We are here to help but, we cannot do it for you. Stay in touch. Stay active. It can only help?

HSL]]> What is the Designer's role?
Once the scenario is moved to the main test page it is the designer's role to arrange for players to test his scenario. This is best achieved by posting for testers on the relevant forums and ensuring the testers register any tests started (see below). You will also need to liaise with your testers to see how things are progressing, every time a test report is submitted you will be notified by email, so ensure your email address is correctly displayed on your member page. The test reports can also be accessed through the scenario listing at the testing area and through the My Scenarios page.

Note: Active designers need to get members to test the scenario.

Once you receive feedback and the current round of tests are completed, you can update the scenario file through the My Scenarios (see below) link. Taking feedback and uploading new versions of your scenario is very important to keep your scenario project moving forward.

Note: When you update the scenario let everyone know. Also put a version number in the scenario description (it can be removed later prior to being moved to the approved area). Remember to keep an open mind when viewing feedback. The testers are trying to help you.

The greatest issue the H2H Area has is designers uploading scenarios and then not fulfilling their role as set out above. Not only does this create a "log jam" of scenarios on the test page it also causes extra admin work for the H2H custodians. Any scenarios found to be abandoned on the test page by their designer will be deleted and that designer may not be allowed to upload new scenarios in the future!

*Please don't upload scenarios if you don't intend to have them tested*

Note: This is not meant to be punitive against any one designer. It is meant to keep things moving. We will be sending out e-mails shortly, to those who have designs in the testing area, to find out which designer is interested in supporting it or having it removed. As previously stated the H2H Custodians are willing to upload the scenario into the Scenario dBASE so that your work will not be lost. And, your scenario can be downloaded and rated through play.

Can a designer test his own scenarios?
This might sound unwise but it has been proved that having the designer involved in the testing can have real benefits to keeping a project moving. If you would like to test your own scenario you should contact Foul. who will discuss this further.

Note: I believe that you can also contact John and I. I usually play test my scenarios once from each side against the AI and then against Humans prior to adding them to the dBASE. I have also tested my own in the H2H area. Sometimes an opponent who is not from your regular pool can show you things that you do not often see. It helps to get as many perspectives as possible?

How does a scenario pass through testing and become Approved?
For a scenario to become approved the scenario requires four reports which rate the scenario with an average score of 8 or more, at that point the scenario can be approved provided there are no other tests registered against it, the scenario is moved to the Approved list using a link located in My Scenarios (see below).

If all the tests are finished and the scenario is still not approved the designer can make changes and upload a new version of the scenario using the My Scenarios link and a new round of testing can begin. This continues until the scenario achieves the required score to become approved.

Note: Sounds tedious but works quite nicely. Especially when the testers commit themselves to also be active.

What is the 'My Scenarios' link for?
This link is a powerful tool that all designers need to know how to use properly, the page lists all of your uploaded scenarios in the testing area and allows you to change almost all aspects of those scenarios. The link is only active while you have scenarios uploaded in the testing area.

The page is self explanatory, but here are some tips...

1. You cannot upload and replace an existing scenario file while any tests are registered against that scenario.
2. You can prevent any new tests being registered against your scenario by changing the 'Testing In Progress' box to 'Testing Stopped', you will need to do this when either you have enough tests running or you are waiting for current test to finish so you can modify or approve the scenario. If you modify the scenario remember to change this box back to 'Testing in progress' to allow tests on the new version to be registered.
3. When your scenario has the required score a link will appear in the 'Approve' box to allow you to move it to the Approved list.

How do testers register their tests on my scenario?
Testers register their tests at the scenario listing on the test page. This is important as having tests registered against your scenario shows the custodians that your scenario is currently under active testing.

Why is a correct Email address so important?
It is important that your correct email address is listed under your Blitz profile as all of the automated messages generated by the H2H area for feedback or points awarded is sent to this email address. Also testers with questions may try to contact you this way.

My scenario has achieved the required score but I cannot approve it, why?
This will be because there are still tests registered against the scenario, testing is done in "rounds" and it is only once a round of testing is finished will you be able to update or approved your scenario. If your scenario is stuck due to unreliable testers then contact Foul. who will help you remove the log jam.

My scenario cannot be updated?
See above.

Can a scenario be too large for the H2H Test Area?
Yes it can. A scenario which the custodian estimates would take longer than approximately one year to test will not be allowed past the holding area. If you have any doubts about the size of your scenario ask the relevant custodian before you upload the scenario.

Note: Just keeping the testing active will help to move even that largest scenarios along. If there is no action the large ones will be treated as any other inactive test scenario.

What bonus points will I earn?
Designers are awarded 20 points per Size Modifier once their scenario is moved to the approved list.

How does the rating formula work?
The rating formula for the scenario average score is
(balance*1.6)+(enjoyment*1.2)+(briefings*0.2)/3

Balance carries the most weight followed by enjoyment, while the briefings score has least weighting. There is guidance on the report to indicate to testers that the briefing should be scored highly if informative and complete.

Why am I only allowed to have 3 scenarios uploaded?
This is to prevent designers hogging all the available space on the test page, the best way to upload new scenarios is to get your present ones approved!

Note:This can be the most frustrating part for the designer. Keeping in active touch with the testers help to move scenarios along and allow more scenarios to be uploaded as existing ones attain approval.

I no longer wish to have my scenario on the test page?
Contact Foul. who will delete your scenario.

Any tricks of the trade?

1. Consider forming your own test group of testers who you can trust to be reliable and provide useful feedback.
2. Consider only having three tests registered against your scenario to keep things manageable and use the 'Testing stopped' feature to prevent any more tests being run until you are ready to approve or update the scenario.
3. Make sure any tests are registered as this will show the custodians that there is testing taking place with your scenario.
4. Any problems or queries contact Foul. who will do everything he can to help you out.

Note:We are here to help but, we cannot do it for you. Stay in touch. Stay active. It can only help?

HSL]]> https://www.theblitz.club/message_boards/showthread.php?tid=54773 Sat, 13 Feb 2010 21:02:32 +0000 Herr Straße Laufer]]> https://www.theblitz.club/message_boards/showthread.php?tid=54773 What is the tester's role?
A tester should try to play a scenario with the intention of providing useful feedback to the designer who can then make improvements to the scenario. On completion of the scenario both testers will independently score the scenario. It is from these scores that the approval of the scenario is decided.

Note: Play the scenario more as a test than as a "game". If the scenario is not one that you like to play (not your "cup of tea") try not to allow those feelings to color your assessment of the scenario. You may not like it but, it can still be balanced?

Once the test is finished you should return to the scenario test page where the scenario is listed and click Submit, this will open a test report which you should fill out with as much detail as possible, once the report is finished click Submit at the foot of the page and your comments will be emailed to the designer.

Note: Designers really want to see your feedback. It sometimes helps to keep notes as you play and then refer to them when you provide the feedback.

You will be awarded bonus points by the H2H Commander once your report has been checked.

Note: Bonus points are good. Helping to get a scenario into the Blitz Approval area is also good thing. ;)

Do not test a scenario if you play at a very slow rate as you will hold the current round of testing up, if you register a test you should be committed to finishing it in a reasonable period, also if you are unable to complete a test for any reason contact Foul. who will delete your test.

Note: This is critical for the designer. Some designs remain in H2H awaiting the completion of your test. If you cannot finish what you started, for the sake of the designer, contact Foul and have your test removed. This may be the only roadblock to gaining approval. Or, other testers might not sign up thinking that you are testing it? As with tournaments, if you sign up, please do your best to see it through.


You, the tester, are the ones that the designers rely upon. Please help them out to the best of your ability.

Thanks!



HSL]]> What is the tester's role?
A tester should try to play a scenario with the intention of providing useful feedback to the designer who can then make improvements to the scenario. On completion of the scenario both testers will independently score the scenario. It is from these scores that the approval of the scenario is decided.

Note: Play the scenario more as a test than as a "game". If the scenario is not one that you like to play (not your "cup of tea") try not to allow those feelings to color your assessment of the scenario. You may not like it but, it can still be balanced?

Once the test is finished you should return to the scenario test page where the scenario is listed and click Submit, this will open a test report which you should fill out with as much detail as possible, once the report is finished click Submit at the foot of the page and your comments will be emailed to the designer.

Note: Designers really want to see your feedback. It sometimes helps to keep notes as you play and then refer to them when you provide the feedback.

You will be awarded bonus points by the H2H Commander once your report has been checked.

Note: Bonus points are good. Helping to get a scenario into the Blitz Approval area is also good thing. ;)

Do not test a scenario if you play at a very slow rate as you will hold the current round of testing up, if you register a test you should be committed to finishing it in a reasonable period, also if you are unable to complete a test for any reason contact Foul. who will delete your test.

Note: This is critical for the designer. Some designs remain in H2H awaiting the completion of your test. If you cannot finish what you started, for the sake of the designer, contact Foul and have your test removed. This may be the only roadblock to gaining approval. Or, other testers might not sign up thinking that you are testing it? As with tournaments, if you sign up, please do your best to see it through.


You, the tester, are the ones that the designers rely upon. Please help them out to the best of your ability.

Thanks!



HSL]]> https://www.theblitz.club/message_boards/showthread.php?tid=54769 Sat, 13 Feb 2010 10:56:09 +0000 Kool Kat]]> https://www.theblitz.club/message_boards/showthread.php?tid=54769
Ed and I have worked out the initial kinks in my Rising Sun scenario Terror on Tarakan... and I'm now in need of some men to step forward and play test it with me!

You may download the game files and register for play testing here ----> Terror on Tarakan

Terror on Tarakan is a Complexity 4, 15 turn scenario that features engineers, Matilda tanks, commandos, garrison troops, and snipers. Tough battle for both sides across heavily forested hills, jungles, and flooded, swampy terrain.

The RS scenario has already gone through 6 rounds of initial human versus human play testing, so players will be testing a proven design that is a tense and exciting contest for both sides!

New RS scenarios are few and far between... so here is your chance to help add another H2H tested game for all players to enjoy!

Sunny and deadly Tarakan awaits... who will answer the call?

Register, download, and play test Terror on Tarakan today!

It is highly recommended that play testers for Terror on Tarakan play it blind! Please do NOT open and review scenario prior to play.

________________________________


Terror on Tarakan (May 7, 1945)

Tarakan: [H2H] [HISB] [GD] Following three weeks of intensive air and naval attacks that destroyed all Japanese aircraft on Tarakan and forced the majority of the Japanese garrison forces to retreat inland, the Australian 2/23rd Battalion and 2/48th Battalion of the 26th Brigade Group, in the early morning hours of 1 May, supported by a heavy air and naval bombardment, made an amphibious landing near Roach. Encountering only light resistance, the Australians quickly advanced east into Tarakan Town and north towards the airstrip - securing both by 5 May. But, in order to secure the island and protect the airstrip from attack, the 26th Brigade Group was forced to clear the Japanese from Tarakan's heavily forested hills. The 2/3rd Pioneer Battalion, 2/4th Commando Squadron and support troops were assigned the responsibility of securing the south-eastern portion of Tarakan. On 7 May the Pioneers begain advancing east of Tarakan Town, but encountered unexpectedly strong Japanese resistance centered around two prominent hill features nicknamed "Helen" and "Sadie." Here, the remnants of the 455th Independent Infantry Battalion, 2nd Naval Garrison Force, and Japanese civilian oil workers, commanded by Major Tokoi, were dug into positions on either side of a trail known as John's Track. Securing the interior just got a lot harder! [All: N EA: N VV: No Banzai]]]>
Ed and I have worked out the initial kinks in my Rising Sun scenario Terror on Tarakan... and I'm now in need of some men to step forward and play test it with me!

You may download the game files and register for play testing here ----> Terror on Tarakan

Terror on Tarakan is a Complexity 4, 15 turn scenario that features engineers, Matilda tanks, commandos, garrison troops, and snipers. Tough battle for both sides across heavily forested hills, jungles, and flooded, swampy terrain.

The RS scenario has already gone through 6 rounds of initial human versus human play testing, so players will be testing a proven design that is a tense and exciting contest for both sides!

New RS scenarios are few and far between... so here is your chance to help add another H2H tested game for all players to enjoy!

Sunny and deadly Tarakan awaits... who will answer the call?

Register, download, and play test Terror on Tarakan today!

It is highly recommended that play testers for Terror on Tarakan play it blind! Please do NOT open and review scenario prior to play.

________________________________


Terror on Tarakan (May 7, 1945)

Tarakan: [H2H] [HISB] [GD] Following three weeks of intensive air and naval attacks that destroyed all Japanese aircraft on Tarakan and forced the majority of the Japanese garrison forces to retreat inland, the Australian 2/23rd Battalion and 2/48th Battalion of the 26th Brigade Group, in the early morning hours of 1 May, supported by a heavy air and naval bombardment, made an amphibious landing near Roach. Encountering only light resistance, the Australians quickly advanced east into Tarakan Town and north towards the airstrip - securing both by 5 May. But, in order to secure the island and protect the airstrip from attack, the 26th Brigade Group was forced to clear the Japanese from Tarakan's heavily forested hills. The 2/3rd Pioneer Battalion, 2/4th Commando Squadron and support troops were assigned the responsibility of securing the south-eastern portion of Tarakan. On 7 May the Pioneers begain advancing east of Tarakan Town, but encountered unexpectedly strong Japanese resistance centered around two prominent hill features nicknamed "Helen" and "Sadie." Here, the remnants of the 455th Independent Infantry Battalion, 2nd Naval Garrison Force, and Japanese civilian oil workers, commanded by Major Tokoi, were dug into positions on either side of a trail known as John's Track. Securing the interior just got a lot harder! [All: N EA: N VV: No Banzai]]]>