Other Means

I think Steve has hardline about the player moving his own wounded, or developing the expectation that he could do so. With the idea I'm suggesting, it's halfway between the "fading into the ground" idea and the "moving to the aid station" idea plus the already existing prisoner taking. I think in playing you don't want to be bothered moving cas to the rear, or at least I don't. But you do want some form of penalty for abandoning your WIA. Setting a time limit before automatic evac means you need to hold the ground to enable it, but don't have to actually do it. The evac icon could also fade out over time. I think it would add info that the CO would have available IRL and add a dynamic to the game, encouraging staged withdrawls etc, without adversely impacting gameplay.

Info from a plane gun sight would ruin FOW. As it is we get too much info from them.

Here's what I'd like, and is I think a middle ground between the 2 camps: State 1) When a soldier is wounded, they become immobile & broken. They are still targetable etc but cannot be moved or controlled by the player. They are in this state for X time, say 3 mins. If they are still within command radius after this they become an "evac'ed" icon and are treated as recovered. Recovered will mean they have Z chance of death vs WIA in the AAR/next battle. State 2) If after X time they are outside of command radius but within Y distance of enemies, they become captured and are treated as now, i.e. able to move to the enemies rear. Or possibly change them to a captured icon. State 3) If after X time they are out of command radius but are not within Y of enemies, they are treated as recovered, i.e. turn to an "evac'ed" icon, but now have a much greater chance of death vs recovery in the AAR/next battle. ISTM that that will simulate as closely as possible the correct behaviour without over complicating it. This does not take into account the possible state where a WIA and solider are trying to occupy the same space, but I was thinking the live soldier would automatically displace the wounded in the terrain feature.

If you're British, you use Fahrenheit for warm and Celsius for cold. "God it's hot." "Yeah it's got to be 95". "Holy crap it's cold" "I know, what is it - minus 10?".

We've finished TV and we're proceeding well with StNaz. LfB OTOH was started very late and isn't really ameanable to playing TCP/IP so we'll have to step it up on that one. I was British in TV and I can't remember having a better time with CM. More like that please.

Facinating. It's nice to see behind the curtain oh Wizard.

XML defines and holds the data, it's like a name/value pair codified. You then render it via XSLT (think there's other methods). It's about the most inefficient method of data transfer that you could possibly imagine, it also makes no sense without the XSLT & wouldn't allow non technical people to have a stab at it. HTML for me, any day.

TRP's give an addition to the aiming of MG's, ATG, Mortars as well as Arty. This is indicated by "boresighted". This corresponds to the real world example of the defensive weapons being zeroed in an a piece of scenery.

I think the ideal solution would be to launch a browser & have them in HTML. Templates could be supplied for the hard of thinking.

I'm for it. It's in my list of 5 in the sticky thread.

No, sounds like 'I need a new PC'... I wonder what is in the pipeline for grass... </font>

I agree with URC that the "what if?" battles were some of the most fun, but I can also see Steve's point on having a rolling release schedule and revenue stream, which is I guess the last word on the subject. The only thing I'd like to know is; is a 2 month, 2 armies scope likely? With all that entails?

Sorry about that - it's there now.

I've recieved no emails which seems odd - please re-send any.

Casting my mind back as a virgin player, who are the untapped revenue pool BFC want to tap, the things that I remember really wanting are; Campaign system - I hear this is in. Variable camera heights/configurable keys/storing camera angles - it's hard to find your way around at first Formation grouping - like "keep 25m apart" The main thing that stops me playing games is the setup. There are countless ones I've started and abandoned (sorry Elmar), therefore; Default layout of own troops done by the AI - this would at least give you a start point if everyone was in a reasonable formation And of course we need to keep Asynchronous play These are all about gameplay, rather than units etc. Which I think is what's required?

What methods of asynchronous file exchange are there other than PBEM? Thanks. </font>

Whhhhoop whoooop whooop whooop. *does that thing on the floor where you pivot on your elbow and run in circles*

...and things that go *bumb* in the night.

Not sure if I'm missing mails. If anyone is mailing me and not getting a response, please post here.

Congrats man. My Mrs and I had a daughter last year, and we've another kid on the way in feb. And I STILL manage to play in ROW (for a given level of 'play'). The only way it changes your life is for the better. Welcome Héloïse.

I reckon he surrended and then un-surrended, thereby losing the HMG.

I thought Finnish cuisine WAS big hairy donkey balls? Percival for me, although that's only because he's British. Mekhlis seems a good choice generally (sorry).

I'm in that London wed so hopefully a) it won't be as eventfull as last thu - we were just down the road I can still get a few turns out in the evening. Especially Tiger Valley - I'm loving that scenario.

And don't forget the Firefly. Being able to fit it with the 17pdr turned what should have been a completely outclassed tank into something that can kill kitties at all ranges. You can kill a kitty, a kitty can kill you - what does the armour matter then? I'd trade that for extra reliability any day.

Folke, can you send me your .edu address again, I think I've deleted it. Cheers.