Quaksen

Please attach log files, so it can be checked

I have no clan channel without mods at all - so - WG is probably having issues - AGAIN - with things like friends list and clan chat... sigh. They need to sort their stuff out.

Exactly. Thank you for posting it. (and looks just fine from here, in terms of files inside the zip, so should be all good for when Aslain wakes up)

As I already posted.. there's a link in my signature.. there's a thread stickied in this forum section.. and I even posted the direct link to the thread as well. There's a very clear section there, detailing how to run the logs archiver, which makes the zip file, with all required log files. Not posting log files, just makes Aslain's task of fixing things much harder. (Having to guess at mod setup, having to guess if it's local issue, or not.. having to guess other variables.. you get the point..) Keep in mind for the future.

Posting log files is your "job", if you want to get proper help... otherwise it's pure guesswork. But you have been told what the mod causing troubles are. But in the future, attach log files.

You locked your gold using the XVM feature. Click the little lock next to your gold. (Expensive choice to use gold for consumables, when you can easily earn credits on a premium tank/premium account, to pay for consumables.. buying them in bulk during 50% off sales)

The link is in my signature. It's stickied in the forum section too.

Please attach log files.

It's 3 clicks to add an exception, and it hasn't changed that often.

The change is that you cannot just right click near a target anymore, and it'll snap on. That function was removed. Now, if you right click near a target, you'll activate a timer (if it's set with a timer), and if you at some point in that time frame, highlight an enemy tank, it'll lock to that.

All servers have the same rules now. All mods in the modpack are allowed under the Fair Play Policy. XVM is still around.. it'll never go away, hehe. The "auto-aim" mod has changed quite a bit.

Please attach log files properly, see the link in my signature. The "Unexpected lack of fashion, but camouflage is being applied." error is a vanilla WoT error. Happens without mods.

Please attach log files

Yes, you run the installer again - it'll remember your choices from last time, so you can untick the choice you do not want... and then clean-install again.

Don't hesitate to make a bug report, if you end up finding an issue - Aslain fixes things fast if there is an issue, so you shouldn't find one

I do enjoy the player panels by hakabase (v2) and his standard contour icons as well. Beyond that, I'd say it's up to what appeals to you in the selection list Keep in mind if you select a different crosshair, that you'll need to select it in the settings menu in World of Warships, otherwise it won't show up.

There are preview images of most features in the modpack itself. You'll be asked when first starting the installer if you'll want to see them (though if you skip that option, you can still click to view descriptions / previews while already on the list)

Those backup options have sometimes caused local issues, for some weird reason

For Battle Observer's "Display damages" on the player panel, try pressing B currently, in next modpack update, it'll be changed to Left-ALT.

Will do, thanks for adding a reply, since you snuck that into an edit It seems I only have the mod.xml file there, nothing else.. back to the drawing board

Lucky you... I hear weird russian voice when I use Steven, even though I got the pirate voice selected.

Newest game update broke a lot of sound mods, since they changed their sound system file structure and what not. They even broke their own voices doing that... the ARP voices etc. I get weird russian voices now, playing with Steven, for example, lol. Supposed to be hearing the english pirate, but nope.

The chat/friendslist is a WG issue, they've tried to fix it, but apparently that didn't work for them yet.

@Falconeer82 Could you post log files as well, please?

That would be quite comical If Norton was hijacking links, sending it to a bad link, and then blocking it