Scorpiany

Which is why I make these guides. To try to help people player more efficiently. ;)

You're trying to mix incompatible mods. Aslain's Damage Panel and Seafalcon's Damage Panel are both... damage panels. You can't have 2 different kinds of damage panels at once. You'll have to choose between one or the either. (Go with Seafalcon's! :D )

For the second installment of my "No Duh" PSA series, I will be covering Team Killing, how to avoid it, and what to do if someone is trying to team kill you. How to avoid accidental Team Kills: First thing's first. Sometimes, you accidentally team kill an ally. However, it is avoidable. The easiest way to avoid Team Killing is to pay attention to your surroundings. Occasionally look around your tank, check the mini-map, etc. Not only will that make sure that you're not flanked by enemies, but it will also help you see any allies that may be trying to drive past your gun. Also, don't drive in Sniper Mode. That is a literal example of tunnel vision, which will make it extremely difficult to notice your own scouts and mediums driving by. In addition, if someone is face-hugging a tank, don't shoot unless you have a clear shot at the enemy, and don't risk hitting the ally. Remember - if even a small part of your aiming circle is displayed over an ally, then there is a chance that you might hit him/her. How to avoid being Team Killed: Pay attention to where you allies are pointing their guns. If the gun appears to be locked on target, don't drive past it unless the ally just fired a shot (and has a somewhat long reload). Otherwise, simply drive around the ally. In addition, avoid face-hugging enemies that are being shot at from all directions. This will only put you directly into your ally's line of fire, and there is a significant chance that your snipers or artillery may end up hitting you. If someone tries to Team Kill you: DON'T SHOOT BACK! After the ally shoots you 3 times, he will turn blue and receive a ban. If someone begins shooting you, don't shoot back. Let them earn a ban. Also, add the player to your Ignore List (Ctrl + Right click on a player's name, then press Ignore), save the replay (Enable Battle Recording in Settings), and send it in to Customer Support (https://na.wargaming.net/support/Tickets/Submit). Saved replays are found within the following directory: C:/Games/World of Tanks/replays If someone is blocking your way: Add the player to your Ignore List, and send in a ticket to Customer Support. If the ally is preventing you from getting anywhere, you have five options: Load an HE shell, and shoot the ally once in his tracks. This will immobilize him and allow you to move on. Ask an ally to load an HE shell and shoot his tracks. Wiggle around the ally; figure out a way to get around him. Lead the ally that is blocking your way to enemy fire. It sounds mean, but if he's doing his all to stop your team from winning, it would be best if he got destroyed. Lead him to the enemies, and let them take care of him for you. Pretend to go AFK. Trolls try to annoy other players. If you pretend to go AFK, then the troll will not receive the kind of response that he wants; thus he will most likely leave. Regardless, DON'T try to team kill the ally, don't cuss in chat, and don't shoot his tracks more than once. Also, remember: If you shoot at an ally, you risk a ban. Shooting an ally once is usually forgiven by the server; sometimes it doesn't even yield a fine. This is why I say load an HE shell and shoot the tracks of the ally who is blocking your way. You won't risk a ban, and it will immobilize the ally; thus allowing you to escape... as long as you did it once, and once only. If an ally is being circled by an enemy: Remember the ranges that you're shooting at, and the type of ammunition you're shooting with. If you're in an artillery, don't shoot at any enemy nearby an ally unless it is the ally's last hope of survival. Also, if you're shooting high caliber HE shells, such as when in the KV-2, make sure that you will hit the enemy; otherwise you greatly risk destroying the ally, or at least dealing splash damage to him. In addition, remember that your shell takes time to reach the enemy if you are sniping at range. Take this into consideration when aiming your shot. Try to ensure that you aim slightly ahead of the enemy so he will drive into the shot. However, if aiming ahead of the enemy would require pointing your gun directly at the ally, don't do it! If an ally is circling an enemy: Here are a few images that demonstrate where you are safe to shoot, where you should be cautious whilst firing, and where you should avoid shooting in certain scenarios: (Green is safe to shoot, yellow is be cautious [especially if the ally is moving], red is a "don't shoot zone". The green star is an ally, red star is an enemy, and the blue triangle is you.) Additional Information: There is a known glitch where your bullets may exit your gun barrel at a 45 degree angle if you just finished rotating your turret whilst driving your tank at a high speed. There are two ways to avoid shooting shots at strange angles due to this glitch: Enable Server Reticle in your Game Client's Settings Don't shoot immediately after rotating your turret at a high speed. Give the gun an additional half a second, up to 1 second, and you will most likely eliminate the possibility of a strange shot.

Arty... Please, when you see this: DON'T SHOOT! Even though the aiming recticle is entirely upon the enemy vehicle, in reality, your shell has the following travel path in terms of height: Thus, you could very well end up hitting the ally directly in front of the enemy vehicle. Take it safe; and wait for the ally to move out of the way. Otherwise, your shot to save your ally could very well end up killing him/her! I have seen this happen in battle before, and have seen confused players post it on the Forums. So please, don't make the same mistake! Note: If the ally is about to die anyways; and has no means of escape, then maybe it is a risk worth taking. If it is the last hope for your ally, then take the shot. But if he can escape, or is not in any danger in the first place, DON'T TAKE THAT SHOT!

Here are the two 9.2 hangars. http://wotapi.ru/files/wot/9.2/hangar_premium_15aug.zip http://wotapi.ru/files/wot/9.2/hangar_premium_wg_bday.zip

Try this. It's the Clan Icons Pack from my WoT Folder. They've been working fine for me. http://www.mediafire.com/download/djvzdkl963tjf04/clanicons-full-na-20140419.zip

Vanilla WoT is scary WoT... no mods... the horror... the horror!

Invisible mods. :ph34r:

Drive a tank through the traffic. That should get you through. :ph34r:

Hmm... surprisingly the standard re-installation procedure removed the issue for me. I guess the bug is limited to certain scenarios?

I removed the Wide Borders mod on my system, and the issue has disappeared. I'm somewhat sad though... Fiery Salient almost appeared like a volcano... Tanking on a volcano was pretty fun. :P

Ironically, I've been having problems with the engines on some tanks (Type 64, Te-Ke, T71), yet no problems with the gun sounds. I tried a Clean re-installation of Aslain's Mod Pack, removing Aslain's Installer Cache File, and the World of Tanks Cache, and the issue has not sprung up again (was resolved). I suggest you try the same thing.

If the money has Aslain's name on it, wouldn't that mean it's been counter-fitted? :o Either that, or Aslain's revolution has advanced further than I thought! :blink:

Ok, today's the day. Time to update! :P

The Zoom Out mod is already within the mod pack. I'm not exactly sure what you're requesting with this one. Max draw distance for SPG's part of the mini-map settings if I'm correct. Isn't that already the default XVM text for base capture? Regardless, you are allowed to modify these files and manually replace them in res_mods/xvm. http://www.modxvm.com/en/xvm-xvm-xvmconf-configuration-editor/

You are welcome. ^_^

You are very welcome. ^_^ I will try to upload a guide once or twice each week. I hope they'll be useful!

I actually am experiencing the exact same issue. I originally thought that it was intended to be that way. I guess not. :blink:

I know that these mods may conflict with the hitzone skins: Regular tank skins Camouflage skin remover If you have either of these, remove them. Otherwise I won't be able to assist you unless you upload a copy of your _Aslains_Comp_List, _Aslains_Installer_Options, and python.xml files.

I honestly don't know how this mod works. I've been wanting to try it out, but I have never been able to figure out how to make it work. I'll do a bit of research and tell you guys if I found any useful information.

We need some logs. (_Aslains_Installer_Options, _Aslains_Comp_List, python.xml) [You may upload them to MediaFire or Google Drive] However, mods that I know to cause this problem are: Sixth Sense mods Garage mods Lighting Mods Loading Screen mods (ones that modify the appearance of the loading screen) If none of these mods are causing the issue, try re-installing Aslain's Mod pack using a Clean Install, and select "Clear WoT Cache" before you install the mods. Let me know how it goes!

If Firey Salient is the only map that you're experiencing problems with, than it's most likely: Lighting Mod No Fog WoT Tweaker If you have any of these mods, try removing them and see if it resolves the problem. If not, then potentially: Wide Borders Tank skins Could be causing the problem, especially if the Tank Skins are not hit-zone skins. Under some lighting, I have had certain tank skins (especially very reflective ones) cause some issues. Try removing these as well. If none of those mods were causing the issue, try re-installing Aslain's Mod Pack, and clearing your WoT Cache file. If the issue persists, send me a copy of your python.xml log, and I'll be able to assist you further.

Ok. Here is what I have found: The BatCave hangar has been replaced by WarGaming with the Anniversarry Hanger. No Hangar mods will be functional until WarGaming goes back to the old hangar. The Te-Ke has not been seen in-game until today, thus many mods don't properly incorporate it. I am having no issues with the Crosshair Mod that you are using. It is working well for me. I'm afraid I can't help you with that, since I can't duplicate the issue.