Page 1 of 1

COIN: The Struggle with Insurgency in Wargames

Posted: Tue Dec 05, 2017 4:33 pm
by admin
Pushing pixel soldiers around pixel battlefields is something we all love. Some of us also belong to those small, insular Facebook groups of fans of our weird hobby.

http://www.wargamer.com/articles/coin-t ... -wargames/

Re: COIN: The Struggle with Insurgency in Wargames

Posted: Tue Dec 05, 2017 6:17 pm
by The Fox
There is also the controversial game Syrian Warfare and the Return to Palmyra DLC where you fight against Daesh.

http://store.steampowered.com/app/48598 ... n_Warfare/

http://www.wargamer.com/reviews/review-syrian-warfare/

Posted: Wed Dec 06, 2017 7:58 pm
by Urielkell
The article is well written and thought out except this line "The Soviets in Afghanistan employed a level of cruelty far lesser than Coalition excesses that birthed ISIS in Iraq - and still lost." This sound like the the soviets were the the nice kids on the block compared to the coalition. I reaaallly hope this was a an editing mistake and not really trying to pretend the atrocious behavior of the soviets in afghanistan.

Posted: Mon Dec 11, 2017 1:55 am
by Daniel Merritt
Uriel -

I don't want to speak for the author, but I think it was an editing mistake. The way I think it was intended was, "The Soviets were willing to employ far greater cruelty, yet failed" - IE, the problem isn't just that we have pansy politicians back home, or are squeamish about doing what needs to be done; that's been tried against insurgencies and has failed at least as badly as any "soft" approach.

The Soviets in Afghanistan weren't the most vicious counter-insurgents in the world, but they certainly had fewer inhibitions, cared less about any internal or international pressure, etc. And the real point is - it didn't help. The way out isn't to "be tougher".

Re: COIN: The Struggle with Insurgency in Wargames

Posted: Thu Dec 14, 2017 5:17 pm
by EICJoe
Sorry about the delay in dealing with this. The line was mean't to read "...far greater than..." - the article has now been fixed.