Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/04/19 in all areas

  1. I finally did it... I've gotten my recent WN8 above 3,000. I intend to keep it climbing, but for now - I'm going to jot down a few key things which I have learned that really stand out. Maintain a healthy situational awareness: Don't let yourself tunnel vision... no matter what you do, no matter how you're fighting or who you're fighting, you always want to watch your surroundings. Not only will you be able to detect enemy vehicles trying to flank you before they get the opportunity, but you will also be more likely do dodge artillery, and avoid finding yourself in a crossfire. I've seen too many allies and enemies focus upon one vehicle in the battle, only for their enemy to take advantage of this and absolutely wreck them. Don't be afraid to pull back from a flank: If your gun is desperately needed in a flank, put it in there and use it. However, there are times when it becomes increasingly obvious that the flank you are at will be quickly overrun, or flanked and destroyed from behind. If your flank is disintegrating, don't be afraid to turn your tank around and put on your "Nope" shoes. However, if you feel as though you need to pull back, don't hesitate. The more time you spend at a failing flank, the more likely you are to be shot up during your grand escape. When I feel as though it's time to begin pulling back, if I don't begin moving immediately, all too often I'll be destroyed while I'm trying to escape. If you find that you have hesitated for too long and escape is now impossible, just stick with your allies and try to do as much as you possibly can... the enemies which overrun you are the same enemies that the rest of your allies will be fighting, so at least try to cripple them. If your gun is not shooting your tracks should be rolling: If you are not contributing to the battle, your allies are effectively down a tank. There are very few times when you should be cowering behind a corner while your allies are fighting... usually this is only the case for non-scout autoloading tanks. However, unless you have an empty autoloader or a very long reload, you should be in the battle. Yes, you should wait for the right opportunity to make your moves, but don't hesitate for extended periods of time. The longer you're not doing anything, the more likely your allies are to lose. XVM Win Chance is not to be used to judge a battle before it starts. Remember - it's a chance (i.e. prediction of the likelihood of a victory or loss). If your chance to win is low (let's say 33%), you will still win 1 out of every 3 battles with similar predictions - however, if you give up and don't even try in the battle, you are only reducing your chance to win; and often times significantly. Also, keep in mind that recent posts on the Forums and FTR including data from thousands of battles has indicated that in general, XVM Win Chance gives an inaccurate prediction - If you were to average the XVM Predictions for 1,000 battles (let's say you end up with the number 55%), you would find that (assuming you don't give up) will win anywhere from 1%-5% more battles than it predicts (the greater the gap between your recent WN8 and overall, the greater the percentage of additional victories). Even though 1%-5% doesn't seem like much, keep in mind that is 10-50 more victories than XVM predicted... if you give up when you see a low Win Chance, you are more than likely to turn some of those would-be victories into losses. Don't let XVM Win Chance ruin your mood - it's a prediction of probability, and an inaccurate one at that. Every battle always has a chance to be won. Giving up or getting upset about the prediction only reduces the likelihood that you will win. If the entire team lemming trains... follow the train: Sadly, there are times when the entire team goes off in one direction, or rather simply sits at base. If your team does this, don't go off on your own to a doomed flank. The only result will be that you get yourself killed to no avail. When your team lemmings, follow the lemming train and make it a success. Once you've won your lemming flank, either push to the enemy base, or fall back to your own... just work with what you have and make the lemming train work. Never trust allies: As much as I hate to say it, you just can't trust your allies. Unless you got confirmation from an ally that they will do exactly what you have told them to do, don't expect an ally to do anything, no matter how simple or easy it is. Sadly, most players in pub battles are a lot worse than you would hope. Do not do anything that relies heavily on your team. Always leave yourself an escape route and a Plan B. Also, communicate. Talk with your allies... if you want them to move up, or support you, let them know. Saying "Attack!" or "Help!" won't work... type out a text message and try to get confirmation from your allies that they will follow it... and if you get no response, assume they're doing their own thing. If you're going to say something, make it positive: If you're going to type in the chat, keep it positive. Negative text only reduces your team's chance to win by taking the focus of your allies away from the game, as well as breaking their mood and focus. If you want an ally to do something, be specific: Earlier today, there was a JagTiger 8,8cm. facing a Chaffee who's behind a rock. The JgTig8,8cm can one-shot the Chaffee, and the two tanks are 300m away from eachother. The Chaffee isn't even directly behind the rock... he's a distance aways from it. I told my JgTig to move his tank and kill the Chaffee... sadly, he drove straight up to the rock and let the Chaffee circle him... all what the JgTig needed to do was turn his tank to the left, and move about 30m or so to the left... driving up to the rock was not only unnecessary, but suicidal. Obviously, that was my fault. I presumed that the JgTig would figure out that he simply needed to change his line of sight.. instead, he charged the Chaffee (plunging his tank into shallow water, thus reducing his speed). The way my comment came out was unproductive, and had very negative consequences. I needed to specify to the JgTig that he needs to move 30m to the left so he'll have shots at the enemy Chaffee. Have fun: If you lose, or if you have a bad battle, bad RNG or something of the sort, try not to get frustrated. Frustration only reduces your focus, and will only make you do worse, thus become even more frustrated... the cycle then repeats as a self-fulfilling prophecy. If you did well, even if you lost or missed a critical shot, keep your cool. Take note of what you did wrong and what you could have done better, but don't get frustrated. Instead of focusing on the negatives of a battle, focus on its positives. Criticize yourself: Watch your own replays, or think about how you did and what you did after a battle ends. Try to find your mistakes and realize what you did wrong. If you discovered something new which works out very well, take note of that as well. Learn from mistakes, and emphasize your strengths. Don't be afraid to ask for help. I may have 3,000 recent WN8, but there are still some things which I have no idea how to do - I'm clueless when it comes to setting up my artillerly, I have no idea how to brawl in the city in Windstorm, I just can't stop drifting in my MT-25 when trying to circle a tank, and despite putting on Camo, Emblems and Inscriptions onto everyone of my tanks prior to taking them out to battle, I did not realize that I could translate the inscriptions in foreign languages to English by simply highlighting them. Everyone has there strengths and weaknesses. I can't play slow tanks very well - I try to avoid any tank which is not fast (or at least fast for its class). There are some parts of maps which I have never once taken my tank to fight, even though I see allies go there all the time. There are maps which I've mastered one side of the map, and haven't learned any of the other side... obviously that's bad. I perform a lot better on maps on which I am familiar with the entire map. That's why when I have the opportunity, I will explore and try out the "other side" of any map I'm not familiar with. Keep learning, keep asking questions. When trying to learn how to play a tank, focus on playing only that tank... don't keep bouncing around back and forth between the tanks in your Garage. Yes, it may be frustrating at first because you're unfamiliar with the tank, but the only way you will master a tank is by playing it and (not necessarily solely but) mostly it. You won't learn how to play your heavy tanks if you keep switching back to lights, and you won't master scouting if you bounce between your TD's. There are times when your team is at a position to absolutely over-whelm the remaining enemy, but they are all too afraid to move up. If telling them to move up in chat doesn't work, sometimes you will have to be the one who leads the push into the enemy. You don't have to suicidally rush out; you can inch out and try to encourage the enemy to fire their guns and bounce off of your armor, but if the enemy don't fire then at least your allies are likely to being inching out with you. If you have the HP and armor though, sometimes you will have to sacrifice a handful of your tank's HP to allow your allies to win the push. 99% of the time in this scenario, as soon as the enemy fire off their guns your allies will push all the way up. Just make sure that there aren't any TD's or artillery waiting to strike - if that's the case, you may be better off leaving your allies there and trying to go around. If you don't have the HP nor armor, you may have no choice but to go around, or wait for your allies. The very least you can do is tell your allies which tanks they have that are in the best position (and most likely to survive) a forwards push, to hopefully give your team the courage to do something... but don't be the one who sits still with your allies in silence; otherwise you're contributing to their cowardice. If you can't lead the push yourself, at least try to organize a push via. chat, or flank around the enemy to distract them from behind. My apologies for the blob of text, and for any errors which it may contain. I'm tired right now, and was about to go to sleep, until I discovered I reached my goal. I hope my tips prove to be useful!
    1 point
  2. Not really, they got nothing for this, it's probably friends of modstation maker or people who don't care to create a topic to share it on forums.
    1 point
  3. Hello everyone! I've noticed a few things that many people often miss about Aslain's Mod Pack. In this Thread, I will discuss them in detail. I hope this is of some use! The topics that I will cover are: Basic Installation PSA Mixing Aslain's Mod Pack with other mod packs Files that Aslain's Mod Pack leaves behind in your Game Client. Partial Un-installation In-game Crashes and Freezes Other Information [basic Installation PSA] Whilst downloading Aslain's Mod Pack, there will not be a shortcut on the Desktop. If you are planning on using the same version of the installer in the future, go to your Downloads folder, and Create a Shortcut on your Desktop. This is also where you can access all versions of Aslain's Mod Pack that you have downloaded in the past. You may select the installer's language upon start-up. You may not change the language once you have gone past the Language pop-up. If you have selected the wrong language, turn off the installer, and turn it back on again. You will then be able to select the correct language. If Google Chrome says that Aslain's Mod Pack contains a virus, don't believe it! Google Chrome often sends off false alarms. Aslain's mod-pack is absolutely safe to use. If you cancel the installation of selected mods in the middle of the process, some traces of the modifications may remain. In order to remove these, simply go to your res_mods folder and delete them, or run a clean installation next time you download mods. [Mixing Aslain's Mod Pack with other mod packs] You can use multiple mod packs with your game client. In order to avoid conflicts, make sure that you're not installing the same mod twice, or installing an out-dated mod with a different mod pack. As long as you're installing different mods, and up-to-date mods, there should be no conflicts. You may notice that some other mod packs have similar lay-outs to Aslain's installer. Make sure that you read the buttons carefully. Some other mod pack authors use similar appearances, but may place certain buttons in different locations. Double check what you are pressing! This applies to Aslain's Mod Pack too! Other mod packs may or may not over-write mods that Aslain's Mod Pack has installed. Chances are, they will over-write and update your current mods. If this does not happen, un-install Aslain's Mod Pack, and remove any traces of it. [Files that Aslain's Mod Pack leaves behind in your Client] There are several different files that Aslain's Mod Pack will leave behind in your Client. The file names are: Aslains_Downloaded_FilesThis is where all of the archived Downloadable Content (DLC) files end up after you finish installing Aslain's Mod Pack. If you wish to remove Aslain's Mod Pack in the future, but keep one of these mods, simply drag the appropriate RAR file to your Desktop. _Aslains_InstallerThis is the text file that the Installer creates and leaves behind whilst installing your mods. This is essentially an event log of everything that the installer has done. _Aslains_Installer_CompListThis is a ReadMe file of all of the most recently installed mods and selected options. If for whatever reason Aslain's Mod Pack does not detect your most previously saved settings (usually due to a cache clearing), then this ReadMe file is where you can find exactly which mods and options you had selected. _Aslains_Installer_Options (Setup Information)This file also states which mods you had most recently installed. However, this is a file that Aslain's Mod Pack may read and use to pre-set these settings the next time you run a Custom Installation (if I am correct) _Aslains_Installer_Options (Text file)This is a Text File for Aslain's Installer. This file is not directly used by Aslain's Mod Pack, rather it's a remainder after an installation has been run. It's essentially a text file of the Setup information. unins001This is the un-installation wizard for Aslain's Mod Pack. Double click on it and follow the steps to remove Aslain's Mod Pack from your computer. You might also see a file called: IMPORTANT REGARDING THIS VERSIONThis file is left behind by GnomeFather's Historical Realism Gun Sounds Mod. Since GnomeFather's Mod is part of DLC, Aslain's Installer uses all of the files that GnomeFarther left behind in his mod, including the Read Me file. Deleting it will have absolutely no effect on your computer. [Partial Un-installation] If you want to un-install only some of the mods within Aslain's Mod Pack, you have two options. Manually look through your res_mods folder and remove the un-wanted modifications Run Aslain's Mod Pack again, except de-selcect all of the mods that you do not want. Make sure that your desired mods are still selected, and then run a Clean Installation. This will remove the un-wanted mods, and will re-install the mods that you want to keep. [in-Game Crashes and Freezes] If you are experience crashes and/or freezes in-game, there is most likely a conflict with some of the mods that you have installed. For example, if you install several different sound mods of the same type, an internal conflict error may occur and cause your game to crash. The sound mods are most likely responsible for any freezing that you will experience; especially GnomeFather's Sound Mod. Whilst known as a great mod, it is notorious for causing a screen-freeze for a few seconds whenever multiple tanks are spotted in the beginning of the battle. If your game begins crashing, this is either caused by a mod conflict (perhaps a sound mod conflict, or a conflict with other mods you had previously installed, or your computer may have ran out of memory. If you heavily mod your Game Client, and put a lot of stress on your processor, your game (whilst uncommon) may crash. Sound mods and lighting mods usually are the causes of these kinds of crashes. [Other Information] If you are experiencing a problem with Aslain's Mod Pack, you should first try a Clean installation, as well as clear your World of Tanks and Installer Cache files. If this does not work, upload your CompList and Installer Text File, and someone may be able to help resolve your issue. If you have pinned Aslain's European Forum Thread for download convenience, you should consider pinning Aslain.com instead, since Aslain has moved his download link here. If I made any errors or missed something, please let me know; and I will fix it immediately!
    1 point
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.