Coh opposing fronts campaign
Sometimes, you'll be forced to retreat a squad.
If you end up facing an enemy, and can finish capping a point, or uncapping, do it. Go for strategic points, they're quick to cap, and great for cutting off additional resources. Don't wait for it to arrive, just disappear. Pios can't put up much of a fight, scare them off. This is when you're hard to beat back, and when you'll set the tone for the game. Watch your resources and make sure the support truck is on the way as soon as possible if this happens. Punch yourself in the face again if you've already lost your LT. An HMG can't hold off three squads, only two. If you get this tommy squad caught at your base under HMG/Sniper fire, you can call your other units back. Don't blame your enemy, you can keep him alive. If he dies, you may as well punch yourself in the face. Shortly after you're set up, you'll have three Tommie squads and a LT spread all across the map. Manpower is more important than fuel or munitions, don't worry about it. When you get to your new base, set up, you should be able to build more Tommies. Just remember that if he comes out under fire, he's most likely going to die. If you think that your enemy isn't coming for your target base, do it at home. Either before or after is fine, but remember, your whole tech tree, and your Tommies depend on that guy. Tommies have balls, don't sell them short.Īs soon as you're set down, and probably before you move, you can build an LT. You can take down a bike with the loss of one man. If you face someone who is mobile, pull back. Most of what your enemy will throw at you won't be as mobile as you are. It's very important to always be capping. Map control is key, and that site won't be able to be uncapped with a big truck sitting there glaring at the MGs drawing pictures in the dirt. They can't hurt you, don't waste your men. MG's, snipers, and bikes won't hurt your HQ - don't babysit it. Do the same for the Recon squad, once your HQ is set up. Queue up capping order, and just keep an eye on them in the map. Before you move your truck, always build support forces. To be the most prepared, SPREAD OUT YOUR FORCES. PE will come with G43's, Wehr will come with MG's and snipers. Continued abuse of our services will cause your IP address to be blocked indefinitely.Your enemy will rush you. Please fill out the CAPTCHA below and then click the button to indicate that you agree to these terms. If you wish to be unblocked, you must agree that you will take immediate steps to rectify this issue. If you do not understand what is causing this behavior, please contact us here. If you promise to stop (by clicking the Agree button below), we'll unblock your connection for now, but we will immediately re-block it if we detect additional bad behavior. Overusing our search engine with a very large number of searches in a very short amount of time.Using a badly configured (or badly written) browser add-on for blocking content.Running a "scraper" or "downloader" program that either does not identify itself or uses fake headers to elude detection.Using a script or add-on that scans GameFAQs for box and screen images (such as an emulator front-end), while overloading our search engine.There is no official GameFAQs app, and we do not support nor have any contact with the makers of these unofficial apps. Continued use of these apps may cause your IP to be blocked indefinitely. This triggers our anti-spambot measures, which are designed to stop automated systems from flooding the site with traffic. Some unofficial phone apps appear to be using GameFAQs as a back-end, but they do not behave like a real web browser does.Using GameFAQs regularly with these browsers can cause temporary and even permanent IP blocks due to these additional requests. If you are using Maxthon or Brave as a browser, or have installed the Ghostery add-on, you should know that these programs send extra traffic to our servers for every page on the site that you browse.The most common causes of this issue are: Your IP address has been temporarily blocked due to a large number of HTTP requests.