cokebottle

Ok cool. I'm on the official release, 7860. Another question: I've tried disabling the small stats blurb in the garage by setting statistics to false in widgetTemplates.xc, but it didn't work. Was I wrong in assuming that was the place?

This is from my XVM log. Anything to be concerned about? 2017-08-31 19:29:31: [ERROR] Traceback (most recent call last): File "./res_mods/mods/packages\xvm_main\python\python_macro.py", line 157, in process_python_macro return (func(), deterministic) File "./res_mods/mods/packages\xvm_main\python\python_macro.py", line 150, in <lambda> return (lambda: func(*args), deterministic) File "res_mods/configs/xvm/py_macro\hangar_stat.py", line 21, in winrate_next winrate = itemsCache.items.getAccountDossier().getRandomStats().getWinsEfficiency() * 100 TypeError: unsupported operand type(s) for *: 'NoneType' and 'int' arg='winrate_next(0.5)' 2017-08-31 19:29:31: [ERROR] Traceback (most recent call last): File "./res_mods/mods/packages\xvm_main\python\python_macro.py", line 157, in process_python_macro return (func(), deterministic) File "./res_mods/mods/packages\xvm_main\python\python_macro.py", line 150, in <lambda> return (lambda: func(*args), deterministic) File "res_mods/configs/xvm/py_macro\hangar_stat.py", line 21, in winrate_next winrate = itemsCache.items.getAccountDossier().getRandomStats().getWinsEfficiency() * 100 TypeError: unsupported operand type(s) for *: 'NoneType' and 'int' arg='winrate_next(1)'

It's Mods GUI by Spoter. A sort of configuration interface for some of his other mods, particularly Direction Indicator.

I don't think it's that bad to be paranoid. WG's policies are usually about as clear as mud. Not to mention WG representatives will often contradict each other. The right hand doesn't know what the left hand does.

There is no emphasis on spotted in the original text. By your logic showing the reload timers for unspotted enemies would be fine - which is of course, with all due respect, total nonsense. Enemies that have shot and hit you are spotted enemies. You can't show their reload timers, no matter if they are spotted or unspotted. There is also no distinction between "showing when the enemy tank has reloaded" and "showing when the enemy can hit you again". Even if WG's translations sometimes leave some things to be desired, it's patently clear what the meaning of this rule is: All kind of reload timers are disallowed.

That's how I interpreted it also. I never used reload timers, so I'm more miffed that they banned autoaim indicator+ :(

Apparently there exists a mod that shows "shadows" or "ghosts" where tanks were last spotted, not on the map but in the battle view. If that tank has not moved it means you could still aim at certain weak spots etc.

No, that was adopted into the game itself.

Yes, as I interpret it the reload timer functionality of XVM (and Gambiter's) is now expressively not allowed.

Thanks Aslain.

In battleLabelsTemplates.xc "fire": { ... "format": "ПОЖАР" }, That should probably be localized, right?

Reload timers seem to be legal (unfortunately) as long as they don't take into account things the player can't know, like crew skills or equipment. That is, they must show the "base" reload time of a gun. Not sure about overhead reload timers.

It works for me with no problems. Are you using the default configuration?

Yes it is. Unfortunately I don't remember exactly the format. According to macros.txt, I think it's something like "vtype=SPG?" or "vtype-key=SPG?". Edit: It's {{vtype-key=SPG?100|0}}

No idea then, sorry. Every time I've had fonts problems in XVM it's been because of conflict with older system installed font. Edit: I think the hitlog uses $FieldFont which I read somewhere is "ZurichCond". Make sure you don't have that one installed in Windows. Or maybe it just doesn't support Unicode and you'll have to specify some other font.