Quaksen

Guess you might have to try without ticking this: Backup session stats cache (untick this option in case of problems)

Odd that it would display the macro instead of the actual stuff, that would suggest a part of the config is missing entirely, I guess?

Did you use "wottools" on scripts_config.xml, and then save the output into res_mods\version folder? That should do the trick, and let you edit the silhouetteColors The values used there are RGBA in 0.0 to 1.0 scale, so if you wan to set a color as 243, for example, divide it by 255.

Please attach logs, and try to explain better than "it will not work" See this:

The filename linked is the wrong one - just change 14 to 15, and it'll work. "Workaround" until Aslain updates the post

Relax. It'll be fixed soon enough.

The thread I found for TessuMod had this to say: "The mod can be configured by editing file res_mods\configs\tessu_mod\tessu_mod.ini. The file is not included with the release package, but is created when you start WOT. This ensures that you don't accidentally overwrite your modifications when updating mod to newer version. The mod automatically reloads the file when ever you change it, so you don't need to restart WOT after changing it."

At a glance, I didn't see anything wrong in that screenshot. Would be interesting to find out if WG ends up admitting to making a mistake, in some of their bans, but they're too scared to admit it, it would look bad if they do

You already have the tier options though - and same for the types. You can select all tiers, except the ones they don't have. You can select all types, minus the light tanks. The garage filters are part of XVM.

I think it's the proper place It's World of Tanks - and it's a general question, not an issue or bug report

Yes - if you use the skin pack, JSGME allows you to pick and choose which skins from the pack to install

It is, most likely, used for the various skin mods. You're installing a skin pack, right? JSGME stands for JoneSoft Generic Mod Enabler.

Hahaha... what a perfect image...

Problem is - if they told us how the detection system worked.. they're also telling those that create cheats, what to avoid... making it easier for them to combat the detection.. In Cynd3r's words: "The number is so low because we used very conservative, specific conditions in determining which players were to be sanctioned. These sanctions are incontestable--no appeals will be considered--so we wanted to be 100% certain with this first wave that those who were sanctioned were done so with reason." http://forum.worldoftanks.eu/index.php?/topic/601238-fair-play-policy-first-actions-taken/page__st__20__pid__13438883#entry13438883

That would create a big mess, hehe... I do hope they have just a couple of braincells working, when it comes to their mod scan.. Some mods used to contain forbidden features - but forbidden feature(s) were removed - but mod has the same file name, for example.

If they have just 2 braincells - they can see, even from the python.log - that the date on his version is 8th November, which is the date that the mod author removed the illegal feature But... they're WG...

Hm - what version of the modpack were you using before your reinstall of the modpack? You reinstalled today.. but what did you use prior to that - which version - if you remember?

Danish for WoWs installer updated: WoWs_da_translation_v5.14.1_06.ini.zip (Missing some lines still, shouldn't be too many - will get those fixed when the next translation update is out )

Danish for WoT installer updated: WoT_da_translation_9.16_54.ini.zip

Because the file is missing from that link. If you click it, it'll show you the 404 error page - which is what you're saving.

Interesting. And weird. You should be getting the adfly page, unless something on your computer is messing up the link somehow.

If you use USA 1 link, then you'll see the adfly page, and the skip in the top right corner. If you use the direct link, just behind it, it'll download directly (but not support Aslain through the ads shown on the first link)

The snapping part is illegal - WG said so - which is why the snapping was removed. It's weird if your normal autoaim is disabled too... mine works fine. Source for the snapping part: http://forum.worldoftanks.eu/index.php?/topic/598224-fair-play-policy/page__st__200__pid__13344242#entry13344242 "As for autoaim, our "forbidden" list includes mods that allow players to enable built-in auto-aim/target lock without having the enemy tank highlighted by the crosshair."

That feature was removed from the Autoaim Indication mod, since it is now forbidden by the Fair Play Policy.

The worst part overall - is that they forbid something like the snap-to-target, which doesn't provide a huge advantage (you're aiming at the center of the enemy tank using it.. some tanks you'll hit tracks or spaced armor, and if you are peeking from a building, he'll hit you before you can shoot too..) And then they go ahead and allow the "enemy view direction on minimap" - letting you see where every single enemy, inside the draw distance, is looking towards... which tells you where he's aiming.... eh, it's Wargaming we're talking about.. something aint right on the top floor.