Wishlist thread
Moderators: alexs, Gregor_SSG
RE: @Admin - Wishlist
I think this is the CAW-2007 wishlist thread.
In any case, no Panther Games has no connection to the game 1830. The PC game was coded/ported by Simtek. This was about five years after Avalon Hill released the board game.
In any case, no Panther Games has no connection to the game 1830. The PC game was coded/ported by Simtek. This was about five years after Avalon Hill released the board game.
2021 - Resigned in writing as a 20+ year Matrix Beta and never looked back ...
RE: @Admin - Wishlist
ORIGINAL: geofactor
just curious.......did panther games make the game 1830 for the PC?......be nice to see a multiplayer version
A solution your question (see):
tm.asp?m=1574214
---
Sorry for the detour; back on topic now.
2021 - Resigned in writing as a 20+ year Matrix Beta and never looked back ...
RE: Wishlist thread
recenty bought game and am mildly pleased.....however.....the ship combat is pretty lame! i think the makers of this game would do well to look at SSI's Great Naval Battles series......i dont need to scale down to operate the guns or anything like that.....but it would sure be nice to be able to manuvre my ships in combat as well as put them in a few formations such as line ahead or AA defence....also when planes were readying for CAP...you couldnt load and arm bombers cause the flight deck was in use!.......and also where is the possibility of losing search planes to CAP.....there should be a chance a search plane is shot down before sighting an enemy fleet!....then as commander of a CV fleet you would have to make a decision to attack an area where you lost a search plane and hope the enemy CV's are there....and one more thing....the ability to load and land troops........and what about reinforcements.......im sure the US navy was sending planes to various bases on a daily bases......im sure ill think of more things later.......but you guys are close to having a really good game here.....plz consider what i have mentioned for you next update.....thx Geno
take it like a mannequin!
RE: Wishlist thread
The original game used to have planes shot down while searching. I haven't noticed if this one does yet - will check the squadron logs next time I play.
One thing I noticed playing midway as the japs last night:
I lost BOTH Hiei and the other BC (forget its name) to US submarine attacks (from two different subs, about 6 hours apart). No issues with that, the problem was when the game was over I noticed the US log had another 8 attacks that the US had carried out and missed, which I never knew anything about.
Should you be given notice that these attacks are occuring so you can vacate the area?
One thing I noticed playing midway as the japs last night:
I lost BOTH Hiei and the other BC (forget its name) to US submarine attacks (from two different subs, about 6 hours apart). No issues with that, the problem was when the game was over I noticed the US log had another 8 attacks that the US had carried out and missed, which I never knew anything about.
Should you be given notice that these attacks are occuring so you can vacate the area?
Awaiting the new CAW
- Ron Belcher
- Posts: 247
- Joined: Sat May 21, 2005 7:23 pm
- Location: Clovis, CA USA
- Contact:
RE: Wishlist thread
This may or may not have been asked. So here goes...
Co-op ? I'd like to see 2 fleet commanders .. Both in charge of their perspective TF's.
And yet, on the same side! Just a thought.
Co-op ? I'd like to see 2 fleet commanders .. Both in charge of their perspective TF's.
And yet, on the same side! Just a thought.

Artwork graciously provided by Rogueusmc
RE: Wishlist thread
a turn based version to do pbem would be nice but probably too hard to implement
Enlisted during Nixon, retired during Clinton then went postal - joined the USPS, then retired from that during Obama.
- GenChaos33
- Posts: 347
- Joined: Thu Sep 28, 2000 8:00 am
RE: Wishlist thread
My Wish List (to help with MP campaign games)
1) Ability for Human Controlled TGs to retreat off map (side of map set per game editor) And no resign til all forces off map.
2a) Add a third player to MP games (as referee: to view all forces during play, and scenario distribution/download to both Allied and Axis player at start)
or
2b) Password Protected Player-Created Scenarios. Some thing like a 2 part password. One part given to Allied player, second part to axis. Code will only show forces for that specific side.
NOTE: 2a and 2b are for hiding true composition of forces and locations in scenarios. So player cannot load scenario before MP match and snoop opposing side forces and locations.
1) Ability for Human Controlled TGs to retreat off map (side of map set per game editor) And no resign til all forces off map.
2a) Add a third player to MP games (as referee: to view all forces during play, and scenario distribution/download to both Allied and Axis player at start)
or
2b) Password Protected Player-Created Scenarios. Some thing like a 2 part password. One part given to Allied player, second part to axis. Code will only show forces for that specific side.
NOTE: 2a and 2b are for hiding true composition of forces and locations in scenarios. So player cannot load scenario before MP match and snoop opposing side forces and locations.

- GenChaos33
- Posts: 347
- Joined: Thu Sep 28, 2000 8:00 am
RE: Wishlist thread
add on to - My Wish List (to help with MP campaign games)
3) Battle Results - text report created at the end of scenario/battle. Listing final VPs, all ship status damaged/sunk, all planes damaged/destroyed, airfield damage by airstrike, island bombardment, invasion troops landed, etc., etc..
3) Battle Results - text report created at the end of scenario/battle. Listing final VPs, all ship status damaged/sunk, all planes damaged/destroyed, airfield damage by airstrike, island bombardment, invasion troops landed, etc., etc..

- GenChaos33
- Posts: 347
- Joined: Thu Sep 28, 2000 8:00 am
RE: Wishlist thread
Update to my wishlist.......
1) already exists - strike from wishlist
2) would like, but understand that it would require alot of work
3) needed badly, and could be easily done?
1) already exists - strike from wishlist
2) would like, but understand that it would require alot of work
3) needed badly, and could be easily done?

- Admiral DadMan
- Posts: 3394
- Joined: Fri Feb 22, 2002 10:00 am
- Location: A Lion uses all its might to catch a Rabbit
RE: Wishlist thread
Make the "On Station, Waiting for Strike Recovery" feature after launching a strike from a Carrier TF optional.
Although this feature is designed to prevent gaming the system by players who wish to use single pulse "dump and run" attacks, it creates 2 other issues that can also be gamed out as well.
First, it prevents sustained attacks by locking the Carrier TF in one location, and hampers pursuit for follow up attacks.
Second, it exposes a CV TF to attacks by Surface Action TF's by locking the Carrier TF in place, negating a chance to evade laterally.
Some time ago, I argued (unsuccessfully) that this "feature" could be alternately coded by imposing penalties for aircraft losses due to "failed to return" from air strikes.
I don't wish to rain on everyone's parade as I'm sure that I am a tiny minority of 1, but I'm disapointed that this feature is still employed.
Are we too far down the road to explore this?
Although this feature is designed to prevent gaming the system by players who wish to use single pulse "dump and run" attacks, it creates 2 other issues that can also be gamed out as well.
First, it prevents sustained attacks by locking the Carrier TF in one location, and hampers pursuit for follow up attacks.
Second, it exposes a CV TF to attacks by Surface Action TF's by locking the Carrier TF in place, negating a chance to evade laterally.
Some time ago, I argued (unsuccessfully) that this "feature" could be alternately coded by imposing penalties for aircraft losses due to "failed to return" from air strikes.
I don't wish to rain on everyone's parade as I'm sure that I am a tiny minority of 1, but I'm disapointed that this feature is still employed.
Are we too far down the road to explore this?
-
- Posts: 23
- Joined: Wed Jul 23, 2008 1:30 am
RE: Wishlist thread
I heartily endorse GeneralChaos's third wish list item. It would be great to have all of the information presented at the end of a battle in some kind of text file. The amount of information on SSG 's CAW stats pages suggests that some of the data is easily accessible. Any thoughts SSG?
RE: Wishlist thread
Greetings!
I'm new here, so I wanted to say that I love the game. Because my background is a bit more historical that gaming, I tend to see things from that persepctive. So, some things that are seen as routine I see in a different light.
So, I wanted to add my $.02 regarding a couple of items in the Wish List.
Similarly, Carriers turned into the wind all the time, to launch and recover CAP, searchplanes and ASW patrols. We see this as a routine ocuurrence which didn't affect the big picture of carrier battles. The big picture is all about how you place your forces relative to those of the enemy, and how you handle them when those relationships are established.
I don't entirely agree- I think wind not only could affect the big picture, but it did, and it did so in the most famous carrier battle of all.
At Midway TF-16 suffered terribly on the morning of 4 June from a light wind that cause them to steam AWAY from KIDO BUTAI for one full hour between 0656 and about 0750 while launching their morning attack. Not only did they have to steam away from the Japanese, but they also need to bend on more speed because the wind was light. This had a number of effects:
1. It meant the planes had to planes had to not only spend as long as 40 minutes forming up, it meant they were actually moving AWAY from their target while doing so. This is a big deal when a strike is launched at maximum range.
2. The carriers (TF-16) weren't where the pilots expected them to be when they got back. Not only was this because of the initial launch, but because TF-16 had to turn away from Point Option each time she conducted flight ops, including the rotation of CAP. When you are short on fuel, this is a big deal.
3. Lots of high-speed steaming is bad for destroyers with regard to range.
It's important to remember that as successful as the 1020 attack was, HIRYU escaped, and by doing so crippled YORKTOWN that afternoon. What if HORNET's SBDs ability to searh for KIDO BUTAI when they didn't find them initially wasn't hampered by fuel shortages that resulted, in part, from a light wind from the wrong direction? While we'll never know what happened for sure, I think it's reasonable to suppose had HORNET been able to hit a carrier, perhaps YORKTOWN might never have have never been attacked.
All 10 of the F4F-4s HORNET launched ditched for lack of fuel in part because HORNET had to steam away from the Japanese (and in part because they were stupidly launched first). What if the Japanese emerged from the 1020 attack with, say, AKAGI undamaged. The loss of 10 fighters could have been disasterous later in the battle.
Many an ENTERPRISE SBD ended up in the water in large part because ENTERPRISE wasn't where she was supposed to be when they got back. As few as 10 miles meant the difference between a safe landing and a swim. Did this affect the results of the morning attack? No! But it did effect future operations, including those against HIRYU later that afternoon.
All of those things "affect the big picture". Having 17 fighters instead of 27 is a big deal- if it wasn't, VF squadrons would have stuck with the fixed wing F4F-3s and retained 18-aircraft squadrons instead of expanding them to 27 and 36.
Having three extra SBD's is a big deal- just ask AKAGI.
I do understand the need to keep things simple, and when designing software you have to make compromises, both to keep the game playable and to keep down overhead in the software. But wind and weather (see Coral Sea) were not "routine" and they both played a huge factor in how things turned out in more than one battle.
Make the "On Station, Waiting for Strike Recovery" feature after launching a strike from a Carrier TF optional.
Although this feature is designed to prevent gaming the system by players who wish to use single pulse "dump and run" attacks, it creates 2 other issues that can also be gamed out as well.
First, it prevents sustained attacks by locking the Carrier TF in one location, and hampers pursuit for follow up attacks.
Second, it exposes a CV TF to attacks by Surface Action TF's by locking the Carrier TF in place, negating a chance to evade laterally.
Some time ago, I argued (unsuccessfully) that this "feature" could be alternately coded by imposing penalties for aircraft losses due to "failed to return" from air strikes.
I like those suggestions. It would be nice if you could set your Point Option. Once it's set, you can either steam towards it (and if you reach it, remain on station) or not, depending upon the tactical situation.
Again, I don't mean to sound like I am complaining or I think the game is terrible- I'm not. I love the game, and if these things never make it into the game, I can deal with it. But for the historian in me, those little details mean a lot, and it would take a great game and make it more historically accurate and, well, greater.
Thanks for listening.
Chris
I'm new here, so I wanted to say that I love the game. Because my background is a bit more historical that gaming, I tend to see things from that persepctive. So, some things that are seen as routine I see in a different light.
So, I wanted to add my $.02 regarding a couple of items in the Wish List.
Similarly, Carriers turned into the wind all the time, to launch and recover CAP, searchplanes and ASW patrols. We see this as a routine ocuurrence which didn't affect the big picture of carrier battles. The big picture is all about how you place your forces relative to those of the enemy, and how you handle them when those relationships are established.
I don't entirely agree- I think wind not only could affect the big picture, but it did, and it did so in the most famous carrier battle of all.
At Midway TF-16 suffered terribly on the morning of 4 June from a light wind that cause them to steam AWAY from KIDO BUTAI for one full hour between 0656 and about 0750 while launching their morning attack. Not only did they have to steam away from the Japanese, but they also need to bend on more speed because the wind was light. This had a number of effects:
1. It meant the planes had to planes had to not only spend as long as 40 minutes forming up, it meant they were actually moving AWAY from their target while doing so. This is a big deal when a strike is launched at maximum range.
2. The carriers (TF-16) weren't where the pilots expected them to be when they got back. Not only was this because of the initial launch, but because TF-16 had to turn away from Point Option each time she conducted flight ops, including the rotation of CAP. When you are short on fuel, this is a big deal.
3. Lots of high-speed steaming is bad for destroyers with regard to range.
It's important to remember that as successful as the 1020 attack was, HIRYU escaped, and by doing so crippled YORKTOWN that afternoon. What if HORNET's SBDs ability to searh for KIDO BUTAI when they didn't find them initially wasn't hampered by fuel shortages that resulted, in part, from a light wind from the wrong direction? While we'll never know what happened for sure, I think it's reasonable to suppose had HORNET been able to hit a carrier, perhaps YORKTOWN might never have have never been attacked.
All 10 of the F4F-4s HORNET launched ditched for lack of fuel in part because HORNET had to steam away from the Japanese (and in part because they were stupidly launched first). What if the Japanese emerged from the 1020 attack with, say, AKAGI undamaged. The loss of 10 fighters could have been disasterous later in the battle.
Many an ENTERPRISE SBD ended up in the water in large part because ENTERPRISE wasn't where she was supposed to be when they got back. As few as 10 miles meant the difference between a safe landing and a swim. Did this affect the results of the morning attack? No! But it did effect future operations, including those against HIRYU later that afternoon.
All of those things "affect the big picture". Having 17 fighters instead of 27 is a big deal- if it wasn't, VF squadrons would have stuck with the fixed wing F4F-3s and retained 18-aircraft squadrons instead of expanding them to 27 and 36.
Having three extra SBD's is a big deal- just ask AKAGI.
I do understand the need to keep things simple, and when designing software you have to make compromises, both to keep the game playable and to keep down overhead in the software. But wind and weather (see Coral Sea) were not "routine" and they both played a huge factor in how things turned out in more than one battle.
Make the "On Station, Waiting for Strike Recovery" feature after launching a strike from a Carrier TF optional.
Although this feature is designed to prevent gaming the system by players who wish to use single pulse "dump and run" attacks, it creates 2 other issues that can also be gamed out as well.
First, it prevents sustained attacks by locking the Carrier TF in one location, and hampers pursuit for follow up attacks.
Second, it exposes a CV TF to attacks by Surface Action TF's by locking the Carrier TF in place, negating a chance to evade laterally.
Some time ago, I argued (unsuccessfully) that this "feature" could be alternately coded by imposing penalties for aircraft losses due to "failed to return" from air strikes.
I like those suggestions. It would be nice if you could set your Point Option. Once it's set, you can either steam towards it (and if you reach it, remain on station) or not, depending upon the tactical situation.
Again, I don't mean to sound like I am complaining or I think the game is terrible- I'm not. I love the game, and if these things never make it into the game, I can deal with it. But for the historian in me, those little details mean a lot, and it would take a great game and make it more historically accurate and, well, greater.

Thanks for listening.
Chris
- Prince of Eckmühl
- Posts: 2459
- Joined: Sun Jun 25, 2006 4:37 pm
- Location: Texas
RE: Wishlist thread
I'd genuinely like to see the game adapted to air combat in the 1930's:


- Attachments
-
- navycolor2.jpg (190.7 KiB) Viewed 999 times
Government is the opiate of the masses.
RE: Wishlist thread
I'd genuinely like to see the game adapted to something that wasn't abandonware. Why does it still cost anything? It's not supported in any way and noone cares anymore!
- Prince of Eckmühl
- Posts: 2459
- Joined: Sun Jun 25, 2006 4:37 pm
- Location: Texas
RE: Wishlist thread
I don't know, but these are some sweet looking birds:


- Attachments
-
- tbd2.jpg (125.58 KiB) Viewed 999 times
Government is the opiate of the masses.
- Prince of Eckmühl
- Posts: 2459
- Joined: Sun Jun 25, 2006 4:37 pm
- Location: Texas
RE: Wishlist thread
And look at the beautiful fighters:


- Attachments
-
- F3Fgray.jpg (162.92 KiB) Viewed 996 times
Government is the opiate of the masses.
RE: Wishlist thread
Those are indeed some beautiul birds! I just wish there was a CAW scenario we could use them in...
- Prince of Eckmühl
- Posts: 2459
- Joined: Sun Jun 25, 2006 4:37 pm
- Location: Texas
RE: Wishlist thread
The SBU was the first USN scout to bust 200 mph:


- Attachments
-
- SBUCorsair.jpg (82.47 KiB) Viewed 996 times
Government is the opiate of the masses.
- Prince of Eckmühl
- Posts: 2459
- Joined: Sun Jun 25, 2006 4:37 pm
- Location: Texas
RE: Wishlist thread
Of course, black and white photography doesn't do it justice:


- Attachments
-
- SBU3.jpg (77.15 KiB) Viewed 995 times
Government is the opiate of the masses.
- Prince of Eckmühl
- Posts: 2459
- Joined: Sun Jun 25, 2006 4:37 pm
- Location: Texas
RE: Wishlist thread
Then there was the Vindicator:


- Attachments
-
- SB2U.jpg (72.89 KiB) Viewed 996 times
Government is the opiate of the masses.