Aslain

I don't have a separate link, I received it directly from Oldskool, and it's in my modpack too.

You have two options, display less items on this panel, or hide the background completly. No way around, the shadow background has limited width.

There was such bug in Oldskool's Crew Return but it was fixed already few days ago, you are using outdated mod. updated WG version: - added version with Elite levels, and without - adjustments for various elements, and for the Grand Battles

updated WG version - compatibility with WoT 1.22.1.0 micropatch from 26.10

This collection.py collection.py works fine on WG client, the messages are visible over the minimap, unlike the one from the op. I think Kthulo has to make further fixes.

1. It's man1aq contour icons I have them in my modpack, they are also here https://wgmods.net/647/ 2. Crew Return mods there are two currently, the one in XVM which was fixed recently, and from Oldskool, both available in my modpack as well 3. Sixth sense mod is in my modpack as well, it was ported to .wotmod

I have fixed my Anti-Mirror for WG, will be in my modpack and in thread on KR. Which my icons precisely? Could you show me pic? updated WG version - compatibility with WoT 1.22.1.0

On what game client do you use it?

On your screenie I think I see broken atlas files with your custom contour icons, most likely used old client files, but yeah, the battle loading is now showing elite levels, and there is no way to turn them off just like that. You can use custom mods to hide them for now, like the one I have in modpack from Kurzdor. kurzdor.elitelevelsremover_1.1.0.wotmod

updated LESTA version only, for 1.22.1.0 micropatch from 20.10 Tested: proof

updated LESTA version only, for 1.22.1.0

I mean it was always working fine, I press key defined to hide, and it was working, now they key is hidding it, I see the OFF message but some messages still showing up...

@ktulho Something is off with hideBattleChat.py, it's not hidding the chat on WG client. I didn't notice any errors in logs. python.log xvm.log

It seems that the indicator doesn't stay on screen for 12 seconds; instead, it appears to be around 6 seconds. I attempted to use the 'battleDamageIndicatorApp.swf' from the 1st post, but the game didn't load at all with that file. I also tried modifying the original SWF file by changing the frame rate from 24 to 10 using jpexes, but it doesn't appear to have made any difference. I've attached the original SWF file from the WG client if you'd like to take a look. original battleDamageIndicatorApp.zip modded battleDamageIndicatorApp_modded.zip

It's a risky question here; he will downvote you and tell you to fix it yourself instead of complaining. xD

I saw that errors in logs without atlas mods, even yesterday.

Seem to work now, thank you. No errors at least.

Broken in 1.22.0.1 WG 2023-09-22 08:34:14: [ERROR] Traceback (most recent call last): File "res_mods/mods/xfw_packages\xvm_pymacro\python\__init__.py", line 101, in __load_lib __execute(code, file_name, {'xvm': XvmNamespace}) File "res_mods/mods/xfw_packages\xvm_pymacro\python\__init__.py", line 93, in __execute raise ExecutionException("{} at file '{}' line {}: {}".format(error_name, file_name, line_number, message)) ExecutionException: ImportError at file 'res_mods/configs/xvm/py_macro\damage_indicator.py' line 4: cannot import name _DamageIndicator 2023-09-22 08:34:20: [X:000] [XFW/XfwComponent] loadMods: Loading swf mods: 2023-09-22 08:34:20: [X:001] xvm_battle/as_battle_classic/xvm_battle_classic.swf 2023-09-22 08:34:21: [B:002] [XFW/XfwComponent] onLibLoaded: ../res_mods/mods/xfw_packages/xvm_battle/as_battle_classic/xvm_battle_classic.swf 2023-09-22 08:34:21: [B:003] [XVM:BATTLE] processView: classicBattlePage 2023-09-22 08:34:21: [B:004] UI_fullStats 2023-09-22 08:34:21: [B:005] UI_PlayersPanel() 2023-09-22 08:34:21: [B:006] [XVM INFO] XVM_VERSION=10.7.0 #0056 for WoT 1.22.0.1 gameRegion=EU configVersion=6.1.0 autoReloadConfig=false markers.enabled=false servicesActive=true xmqp=true statBattle=true 2023-09-22 08:34:21: [B:007] [XFW/XfwComponent] onLibLoaded: Mod loaded: xvm_battle_classic.swf 2023-09-22 08:34:21: [ERROR] Traceback (most recent call last): File "res_mods/mods/xfw_packages\xvm_pymacro\python\__init__.py", line 156, in process (func, deterministic) = __get_function(arg) File "res_mods/mods/xfw_packages\xvm_pymacro\python\__init__.py", line 120, in __get_function (func, deterministic) = _container.get(func_name) TypeError: 'NoneType' object is not iterable arg='xvm.damageIndicator' 2023-09-22 08:34:21: [ERROR] Traceback (most recent call last): File "res_mods/mods/xfw_packages\xvm_pymacro\python\__init__.py", line 156, in process (func, deterministic) = __get_function(arg) File "res_mods/mods/xfw_packages\xvm_pymacro\python\__init__.py", line 120, in __get_function (func, deterministic) = _container.get(func_name) TypeError: 'NoneType' object is not iterable arg='xvm.damageIndicator_aim'

I know I can fix it myself, I help with that whenever I can, but it's not the point. We are reporting this bug to XVM devs so they can fix it. If they cannot fix it, they should at least respond something, like "we cannot fix" at least :)

It was already reported on the KR forums months ago, so I don't believe posting it directly on GitHub will expedite the process, but maybe worth a try.

Yup, it's fixed for me.

Wargaming XVM version, same problem: 2023-09-21 12:39:46.386: INFO: ============================= 2023-09-21 12:39:46.386: INFO: 2023-09-21 12:39:46: [ERROR] mods/xfw_libraries/xfw/events.pyc 2023-09-21 12:39:46.386: ERROR: Traceback (most recent call last): 2023-09-21 12:39:46.386: ERROR: File "./xfw/events.py", line 57, in __event_handler 2023-09-21 12:39:46.386: ERROR: File "./xfw/events.py", line 24, in fire 2023-09-21 12:39:46.387: ERROR: TypeError: showDamageFromShot() takes exactly 6 arguments (7 given) 2023-09-21 12:39:46.387: INFO: ============================= In the other mod, there was similar error, and the fix was to add new parameter: damageCausedByDiscreteFactor python.log

I'm keep pinging them about it, but no luck....

updated - compatibility with WoT 1.22.0.1 - compatibility with Tanki 1.22.0.0 micropatch

updated - compatibility with WoT 1.22.0.0 Lesta version of micropatch