scyorkie

Hmm I don't understand why everything is the same color XD Did you copy-paste everything? Anyway here's a different version. Pastebin here: https://pastebin.com/qrAJELce Screenshot here: http://i.imgur.com/x5iCmGY.jpg I felt that having the entire background colored was too distracting. Is there a particular look you are going for btw? I'm merely experimenting with my own config to show you that your idea is possible.

See line 69 of this new pastebin for background color: http://pastebin.com/ygWAswmR This is the effect: http://i.imgur.com/sH1vY5e.jpg If you want to, you can also create a definition: "def": { "classColor": "{{v.type=LT?0x00EE00|{{v.type=MT?0x00B4FF|{{v.type=HT?0xFE0E00|{{v.type=TD?0xAE42F3|0xFF00FF}}}}}}}}" }, ... "extraFields": [ { "x": 1, "y": 1, "h": 84, "w": "135", "bgColor": ${"def.classColor"}, "alpha": "{{v.selected?50|15}}", "layer": "bottom" }, ...

Remove the // at the start of lines 65-67?

This is the pastebin for my carouselNormal.xc: http://pastebin.com/WY7ywPU0 Lines 34-38 (currently commented out) are the test lines I used for the 2 methods above. They work for me. Lines 65-67 (also commented out) are a further test, where the left border of all the tank icons are colored (5 classes, 5 colors). That works for me also. Test using my carouselNormal.xc and see if it works for you?

I just realised that there was a switch to .wotmod, but even after copying the .wotmod file into mods folder and removing the excess pyc files, many parts of XVM still do not work. Since this is just an alpha version, I'll just leave it alone until there are further updates.

Yes it is possible. Method 1: Set 5 different lines (one color for each class) and determine which of the 5 is displayed by using "alpha" and the {{v.type}} macro. Example I just tested in my carouselNormal.xc "extraFields": { "x": 1, "y": 57, "h": 27, "w": "133", "bgColor": "0x420000", "alpha": "{{v.type=SPG?{{v.selected?75|0}}|0}}" }, { "x": 1, "y": 57, "h": 27, "w": "133", "bgColor": "0x000242", "alpha": "{{v.type=TD?{{v.selected?75|0}}|0}}" }, ... So SPG is dark red, TD is dark blue, etc. And I've also made the boxes display only when the particular tank is selected with {{v.selected}} macro. Method 2: Contain everything within one line, with the conditions set within "bgColor" using the {{v.type}} macro. Example (using only 2 classes so that the entire line doesn't get too complicated: { "x": 1, "y": 57, "h": 27, "w": "133", "bgColor": "{{v.type=TD?0x000242|{{v.type=SPG?0x420000|0x000000}}}}", "alpha": "{{v.selected?75|0}}" },

I cannot get to the login screen with 7271. All I see is a blank, black screen. Reverted to 7266 for now.

I've had the same problem for a while: https://koreanrandom.com/forum/topic/37822-soundsxc-is-modify/?do=findComment&comment=380791

I am using a single client, for multiple regions (using a region-changer mod). Why do I see this long warning on my SEA account (which is not my primary region): ..but a simpler message on my NA account:

"clanIcon" is defined early on in playersPanel.xc, and is called up in "extraFieldsLeft" and "extraFieldsRight" (i.e. not in those 4 lines you are pointing to).

When screenVAlign=top, the X and Y coordinates determine where the top left corner of your hitlog starts. When screenVAlign=bottom, the X and Y coordinates determine where the bottom left corner of your hitlog will be. A negative Y value moves that corner up from the bottom of the screen. Then your height value determines where the top of your hitlog starts. So in my settings above, the top left corner of my damageLog is 240 pixels from the left of the screen, and 230 (23+207) pixels from the bottom. In yours, the top left corner is 160 pixels from the bottom. You're replacing the vanilla client's hitlog with the XVM hitlog. I've done that before and 160 was just right for me as well.

My damageLog section in battleLabelsTemplates currently contains the following: "x": 240, "y": -23, "width": 310, "height": 207, "screenVAlign": "bottom", "x" moves it away from the left border of the screen, and a negative "y" moves (I think) the bottom of the damageLog away from the bottom of the screen when screenVAlign=bottom. Use the same screenVAlign=bottom for your hitlog sections?

I have the same problem. Until that gets fixed, there's a quick workaround: click the notifications button to get the garage to load.

I just tried what Tornado_Odan_Rot and konrad509 said above, and it works fine with damageText. Also, "damageText": ${"markers.xc":"damageText"} works only if "damageText" is the top-level section within markers.xc. If you have it under another "def" section, use "damageText": ${"markers.xc":"def.damageText"}.

Mouse over your ammo and you see the average damage per shot.

That happens when one of your .xc files has an error (missing comma, etc).

I'm not sure if we are having the same issue, but I noticed that I don't hear the default 6th sense sound when I have XVM loaded. I can't even preview the sound in the Settings menu. However, when I remove XVM, everything works fine. My sounds.xc used to contain these 5 lines: "lightbulb": "", "lightbulb_02": "", "sixthSense": "", "xvm_sixthSense": "xvm_sixthsense", "xvm_sixthSenseRudy": "xvm_sixthSenseRudy", They now look like this, and everything works with XVM loaded: "lightbulb": "lightbulb", "lightbulb_02": "lightbulb_02", "sixthSense": "sixthSense", // "xvm_sixthSense": "xvm_sixthsense", // "xvm_sixthSenseRudy": "xvm_sixthSenseRudy",

1. I have the same issue as plkJaqenHghar with 7143. I've reverted to 7133. 2. I've always posted issues about nightly builds in this section because I don't understand Russian. Response time doesn't matter to me, so long as the devs receive my posts at the end of the day.

WN8 is calculated off expected values. Anytime those values change, WN8 also changes. There was a recent change and most were affected. A 11-point drop is not a lot. Just continue to improve on your play.

I had a battle where I was disconnected because of router issues. After I reconnected, (i) there were no stats displayed for the players, and (ii) the watermark was visible until the end of battle. I seldom disconnect so this isn't a big problem, but I just wanted to highlight the above.

I can't scroll damageLog (was testing it in a replay where the number of hits exceed the max that can be displayed at once). How is it supposed to work? Do you Ctrl-Click-Drag-and-Move or Ctrl-Scroll? I deleted the folder %appdata%\Wargaming.net\WorldOfTanks\xvm\DamageLog before starting the replay. This is the relevant part of my battleLabelsTemplates.xc (build 7112): "damageLog": { "enabled": true, "updateEvent": "PY(ON_HIT)", "x": 240, "y": -23, "width": 310, "height": 207, "screenVAlign": "bottom", "shadow": { "distance": 1, "angle": 90, "alpha": 80, "blur": 5, "strength": 3 }, "textFormat": { "color": "0xF4EFE8", "size": 14 }, "format": "{{py:xvm.damageLog.dLog}}", "mouseEvents": { "mouseDown": "dLog_mouseDown", "mouseUp": "dLog_mouseUp", "mouseMove": "dLog_mouseMove" } },

7112 fixed it for me. Thanks!

When I was hit by an unspotted arty in clan wars, {{type-shell}} was displayed as "unknown" and {{vtype}} was displayed as "not_vehicle", even though my config contains: - "type-shell" > "not_shell": "" - "vtype" > "not_vehicle": "" Nothing changes even if I edit those lines to: - "type-shell" > "not_shell": "---" - "vtype" > "not_vehicle": "---" Can we not customize this? damageLog.xc here. Build 7102.

Set "directionTriangleAlpha": 0 in minimap.xc

I update to the latest build every day :)