Leaderboard

Описание Библиотека предзназначенная для облегчения написания установщиков модификаций для WoT. Основная функция -- поиск клиентов игры и получение информации о них (версия, локаль, реалм и прочее) а также помощь в разграничении контента для Wargaming/Lesta клиентов. Однако, есть и другие фишки, такие как: распаковка BigWorld XML работа с JSON конвертация PNG -> BMP поиск запущенных процессов в каталоге и их завершение отображение сплэшскрина замена в строке по регулярному выражению детектирование Wine поиск клиентов WGC / Steam / 360 / LGC Получение предпочительного клиента (текущий выбранный в WGC) работа с клиентом получение версии клиента и ее сверка по регулярному выражению получение версии исполняемого файла клиента получение реалма (EU/NA/ASIA/CN/RU) получение типа по контенту (SD/HD) получение типа лаунчера (WGC/Steam/360/LGC) получение типа релиза (Release/Common Test/Super Test/Sandbox) получение пути до активного в клиенте mods/res_mods получение языка клиента детектирование запуска и завершение клиента Как пользоваться 1) скачиваем 2) из комплекта поставки утягиваем два файла bin/openwg.utils.x86_32.dll innosetup/openwg.utils.iss 3) в своем корневом .iss файле прописываете #define OPENWGUTILS_DIR_SRC "bin" #define OPENWGUTILS_DIR_UNINST APP_DIR_UNINST #include "openwg.utils.iss" где OPENWGUTILS_DIR_SRC -- путь к каталогу куда вы положили .dll OPENWGUTILS_DIR_UNINST -- путь к каталогу файла деинсталляции относительно {app}, в подавляющем большинстве случаев должен совпадать с UninstallFilesDir 4) изучаем пример в innosetup_demo/openwg_utils_demo.iss и вызываем нужные вещи, подробности вызова можно подсмотреть в openwg.utils.iss и в *.h файлах в каталоге include Пользователи Название Сопровождающий Ссылка XVM.Installer v1 @Mixaill https://gitlab.com/xvm/xvm/-/tree/master/src/installer XVM.Installer v2 @ktulho https://gitlab.com/xvm/xvm.installer Protanki @Yusha https://protanki.tv/ Jove's @phantasm https://joves-modpack.ru/ KorbenTeam @phantasm https://korbenteam.org/modpack Amway921 @AtotIK https://wgmods.net/95/ Vspishka @AtotIK https://wgmods.net/131/ WGMods @AtotIK https://wgmods.net/16/ , RIP начиная с WoT 1.19.0 🥲 LeBwa team @POLIROID https://lebwa.tv/hub/modpack-lebwa-team Tomato.gg @POLIROID https://wgmods.net/6391/ напишите в комментариях если про вас забыл/не знал Скачать OpenWG.Utils_v2023.09.21.1.zip Исходный код https://gitlab.com/openwg/openwg.utils История версий v2022.12.04.1 первая для широкой публики v2023.03.17.1 переработано API для взаимодействия с JSON v2023.03.18.1 добавлены функции `JSON_SetDouble()`, `JSON_SetInteger()`, `JSON_SetString()` v2023.03.18.2 исправлена потеря комментариев в JSON-файлах v2023.08.01.1 исправлено дублирование клиентов WoT/МТ в случае если регистр имени каталога в файловой системе отличался от такового в конфигурационных файлах WGC/LGC v2023.09.01.1 добавлены фукнции `JSON_ContainsKey()`, `JSON_GetString()` v2023.09.17.1 добавлены функции WWISE_OpenFile(), WWISE_CloseFile(), WWISE_Close(), WWISE_LicenseGet(), WWISE_LicenseSet() v2023.09.21.1 добавлены конвертеры лицензий WWISE-файлов в виде exe-файлов: wwise_convert_to_unlicensed, wwise_convert_to_wg

В общем, с модом mod_tooltipsCountItemsLimitExtend, замах был богатырский, но реально не так много сделал, меньше чем идей в голове, возможно потом продолжу, сейчас всё желание отпало, ночь была весёлая, отвык кодить. В общем, список "расширенный список танков, где находится оборудка" починил Дальше в голову пришла интересная идея, показывать затронутые модулем\расходником\скиллом параметры танка, и сразу это показывать во всплывающей подсказке. Пока разобрался откуда какие параметры подтягиваются, вся ночь и закончилась. в общем сделал только для расходников (аптечка, ремкомплект, кола и бензин), возможно не всё сработает или могут быть косяки, времени на дебаг уже не нашёл, спать хочется. Если идея не затеряется, то сделаю для оборудки и самое сложное умений\скиллов экипажа. Хотя возможно это никому и не надо.

Unified Editor for WoT 1.22.0 https://download.openwg.net/editor/unified_editor_1.22.0.0.7z https://wgmods.net/4895 - больше не теряет секцию с камерой (однако в свои старые ангары копипастить до сих пор нужно самому, смотрите https://koreanrandom.com/forum/topic/45741-/?do=findComment&comment=534949 - внимание для Lesta: поскольку ассеты в клиенте другие (а именно, hangar_v3 в лесте другой/устаревший), у вас камера будет дохлая даже если добавите нужную секцию. Необходимо также скопипастить префабы из hangar_v3 в свой спейс и перебить пути в хмлках

Стиль "Леванте" для Char Futur 4 (в архиве и катки без стиля), клиент SD: F114_Projet_4_1.zip

Исправил совместимость с WG: aiming.py chancePenetration.py targetInfo.py infoAutoAim.py modesVehicle.py markerPosition.py reloading.py infoChargedShell.py quantityShells.py crosshair.py

updated Lesta version - compatibility with Tanki 1.20.1.0

updated - compatibility with WoT 1.19.1.0

Январское обновление уже доступно! https://disk.yandex.ru/d/2hWy5IHwZ1kUdg

Мы изучаем эту проблему и обнаружили некоторые зацепки, но потребуется больше времени, чтобы найти и устранить саму причину проблемы.

Адаптация к патчу 1.20.0.0

Что за скриншот выше ты прилепил? В первом посте выложена актуальная версия программы. И чеклист на вирустотале ничего не показывает при её проверке. Так что разбирайся давай, что там у тебя устарело и где И на будущее - если брендовые антивирусы типа Касперского ничего не показывают, то значит ничего там нет. А на 100500 всяких дешевых коммерческих недоантивирусов смотреть не надо. Они работают крайне топорно и там постоянно ложные срабатывания.

Пожалуйста восстановите тему, обновите шкурки...

Адаптация к патчу 1.20.1.0

Этот мод на https://github.com/Pruszko/DispersionReticle

RU Обновление Версия 1.9.0 для WoT 1.18.1.1 Изменения - Minor changes and fixes EN Update report Version 1.9.0 для WoT 1.18.1.1 Changelog: - Незначительные изменения и фиксы Скачать | Download WGMods GitHub - предпочтительный вариант, обновляется быстрее чем тот же WGMods

Все моды Вы устанавливаете по своему желанию и под свою ответственность. Администрация игры World of Tanks не имеет отношение к модам и рекомендует играть на чистом клиенте. Разработчики игры и ЦПП не обязаны нести ответственность за игровой клиент, в котором установлены моды. Вы отдаете себе отчет о том, что моды разрабатываются игроками и для игроков, поэтому могут содержать ошибки (но все мы люди и иногда ошибаемся). Если же Вас все устраивает, то Вы можете смело скачивать данный модпак. Представляю Вашему вниманию пакет модификаций - JustSherlock ModPack! Перед вами новый пакет модификаций для игры World of Tanks, называемый саундпак, содержащий 15+ озвучек! Здесь я собрал для вас лучшие существующие звуковые моды для игры World of Tanks. Каждый звуковой мод был мною проверен на качество и интерес его использования. Также в данный пакет модификаций были включены самые полезные моды, например, радио Wargaming FM, менеджер реплеев в ангаре, самые полезные модификации XVM и PMOD. Саундпак постоянно дополняется/будет дополняться новыми УНИКАЛЬНЫМИ озвучками, которые Вы не найдете нигде больше (некоторые из таких озвучек уже на стадии обработки, скоро будут добавлены в модпак). Данный модпак имеет понятную пошаговую установку с описанием каждой модификации. ПОЧЕМУ ВЫ ДОЛЖНЫ КАЧАТЬ ДАННЫЙ САУНДПАК С 15 ОЗВУЧКАМИ, ЕСЛИ МОЖНО СКАЧАТЬ ОДНУ ОЗВУЧКУ? ДА ВСЕ ПРОСТО! ТАК ПРОЩЕ УСТАНОВИТЬ ОЗВУЧКУ (УСТАНОВЩИК ВСЕ СДЕЛАЕТ ЗА ВАС, УСТАНОВИТ ВСЕ В НУЖНУЮ ПАПКУ); В ЛЮБОЙ МОМЕНТ ВЫ МОЖЕТЕ ЗАМЕНИТЬ УСТАНОВЛЕННУЮ ОЗВУЧКУ НА ЛЮБУЮ ДРУГУЮ ИЗ САУНДПАКА; ТАКЖЕ ЗДЕСЬ СОБРАНЫ САМЫЕ ЛУЧШИЕ И НУЖНЫЕ МОДИФИКАЦИИ ИГРОВОГО КЛИЕНТА, НИЧЕГО ЛИШНЕГО. ВАМ НИЧЕГО НЕ ПРИДЕТСЯ ИСКАТЬ НА ПРОСТОРАХ ИНТЕРНЕТА. Текущая версия саундпака: 1.12.0.0 Release - UPD 8 от 11.03.21 Скачать: *ССЫЛКА* В первую очередь обновления модпака выходят на моем сайте [видеообзор на модпак: в процессе] УСТАНОВКА Скачать инсталлятор Запустить установочный файл Выбрать моды и наслаждаться процессом установки. При запуске установщика Вам покажется, что Ваш ПК завис на пару секунд. На самом деле это не так, просто процессор Вашего ПК занят распаковкой временных файлов для корректной работы установщика. Пожалуйста подождите немного. P.S. Обязательно внимательно прочтите ВАЖНУЮ информацию перед установкой, находящуюся в документе - faq2.rtf ЕСЛИ ВОЗНИКЛА ПРОБЛЕМА: В приложении Wargaming Game Center выбираем World of Tanks. Если стоит несколько версий игры (или Common Test) - не забываем выбрать нужную. Жмём кнопку "Настройки игры" -> "Восстановить игру". Если это не помогло пишите на почту - тык - автору саундпака или в данной теме. Состав модпака: История изменений:

Should be fixed in 55

Звук пока работает только на World of Tanks, Lesta в работе. Ожидается к концу недели

Мод "Потерянное время" Скачать Мод умеет собирать и отображать в системном канале следующие статистические данные: Статистика кредитов; Статистика опыта; Статистика урона; Статистика расходов; Статистика бонусов от резервов; Статистика штрафов; Статистика времени; Статистика боевой эффективности; Рейтинги боевой эффективности (WGR, EFF, BS, WN6, WN7, WN8, WN8KTTC, BR); Подробная статистика последнего боя; Статистика аккаунта на начало сессии; Влияние текущей сессии на аккаунт; Также мод обладает рядом следующих возможностей: Неограниченное кол-во настраиваемых сессии статистики с одинаковым набором макросов Каждая сессия включает: общую статистику, статистику по танкам, статистику по картам; Задание типов боев статистика которых будет попадать в ту или иную сессию; Произвольно настраиваемый вывод данных на основе макросов и шаблонов с поддержкой внутренних и внешних иконок; Вывод данных на несколько произвольно настраиваемых страниц; Вывод данных в панель ТТХ танка; Вывод данных в панель карусели танков; Настраиваемый вид кнопок для управления информацией; Вызов подробных результатов последнего боя из окна статистики; Обновление информации без закрытия Центра Уведомлений (для альтернативных кнопок); Настройка закладки ЦУ в которой будет выводится игровая статистика; Настраиваемый вывод результатов предыдущего боя в боевой чат; Задание произвольного пути к файлу статистики; Автоматическое обнуление статистики в заданное время; Обнуление статистики по кнопке; Автоматическая перезагрузка конфига для настройки вывода результатов; Автоматическая загрузка таблицы ожидаемых значений и цветовых границ XVM; Настройка вида используемых кнопок; Настройка скорости пролистывания сообщений в системном канале; Настройка вывода PopUp результатов боя в ангаре; Настройка вывода результатов боя в системный канал; Настройка вывода результатов боя в боевой чат; Поддержка много-файлового конфигурационного файла; Автоматический контроль версии файла статистики; Скачать скины по отдельности можно здесь

обновлено под новый патч

Понял, спасибо!

2023-07-18 10:08:03: [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: AttributeError at file 'res_mods/configs/xvm/py_macro\reloading.py' line 42: type object 'AmmoPlugin' has no attribute '_AmmoPlugin__onQuickShellChangerUpdated'

WG 1.21.1.0 2023-07-18 15:53:24.889: INFO: ============================= 2023-07-18 15:53:24.889: INFO: 2023-07-18 15:53:24: [ERROR] mods/xfw_libraries/xfw/events.pyc 2023-07-18 15:53:24.889: ERROR: Traceback (most recent call last): 2023-07-18 15:53:24.889: ERROR: File "./xfw/events.py", line 57, in __event_handler 2023-07-18 15:53:24.889: ERROR: File "./xfw/events.py", line 24, in fire 2023-07-18 15:53:24.890: ERROR: File "res_mods/configs/xvm/py_macro\aiming.py", line 53, in aiming_getOwnVehicleShotDispersionAngle 2023-07-18 15:53:24.890: ERROR: aimingStartTime, aimingFactor, shotDispMultiplierFactor, _1, _2, _3, aimingTime = self._PlayerAvatar__aimingInfo 2023-07-18 15:53:24.890: ERROR: ValueError: too many values to unpack 2023-07-18 15:53:24.890: INFO: ============================= and 2023-07-18 15:53:56: [ERROR] Traceback (most recent call last): File "res_mods/configs/xvm/py_macro\markerPosition.py", line 75, in _VehicleGunRotator__getGunMarkerPosition dispersAngle, idealDispersAngle = dispersionAngles TypeError: 'NoneType' object is not iterable

Всё то же самое, но artillery на flamer меняешь. Событие попалось поиском по коду.

Да, можно вот этот файл vehicle_hangar_stat.py кидаем в ../xvm/py_macro/ (имя любое, также можно код из файла скопировать в свой py_файл) правим widgetsTemplates.xc : 1. Увеличиваем размер тени-подложки под текстом статистики на 15 для новой строки по танку (дважды - для "левой" и "правой" частей) // Фоновая картинка, левая часть. // Фоновая картинка, правая часть. ... "format": "<img src='xvm://res/icons/clock/clockBg.png' width='160' height='{{mystat.wn8?8095|2843}}'>" 2. Дописываем в поле "format" текстового блока новые макросы // Текстовый блок. ... "format": "...\n<font size='13'>{{v.name}}: <font color='{{v.c_winrate}}'>{{v.winrate%.2f~%}}</font> {{py:v_winrate_next(1,{{v.battles}},{{v.wins}},{{v.winrate}})}} / {{py:v_winrate_next(0.5,{{v.battles}},{{v.wins}},{{v.winrate}})}}</font>" наслаждаемся)) если xvm включен если не активирован

"Monochromatic Crash Tanks" Creator 2 СОЗДАНИЕ ОДНОТОННЫХ ТЕКСТУР ДЛЯ УНИЧТОЖЕННЫХ ТАНКОВ СБИТЫХ ГУСЕНИЦ, ВАГОНОВ, ПОЛУПРОЗРАЧНЫХ КАМУФЛЯЖЕЙ И ДРУГОГО Версия: 2.1.3 Совместимо с клиентом игры: 1.10.x и новее Описание: Программа "MCTCreator2" позволяет быстро и удобно создавать готовые модификации, изменяющие текстуры моделей уничтоженных танков и другой техники, путём перекрашивания их в однотонный цвет. Также программа умеет менять прозрачность камуфляжей в игре, делая их менее яркими. Возможности программы: Перекрашивание уничтоженных танков игроков (мод "TankCrashTextures") Перекрашивание сбитых гусениц (мод "TrackCrashTextures") (работает только при отключенной опции "Физика гусеничных лент") Перекрашивание техники, статически расположенной на картах (мод "TankMapTextures") Перекрашивание вагонов и поездов (мод "TrainMapTextures") Изменение яркости камуфляжей (мод "Camouflages") Имеется консольная версия программы "MCTCreator2.exe" и графический интерфейс к ней "MCTGui.exe" Программа использует конфигурационные файлы, новые версии которых загружаются из репо: https://github.com/StranikS-Scan/MCTCreator-Configs Модифицированные файлы сохраняются в виде wotmod-пакетов в папку "mods\XXX\", также программа может сохранять незапакованные файлы в папку "res_mods\XXX\" Поддерживается два языка, есть много дополнительных опций Установка: Чтобы создать моды с помощью креатора необходимо: Скачать zip-архив с программой, распаковать содержимое в любую папку на диске Запустить графический интерфейс "MCTGui.exe", указать путь к игре, выбрать нужные моды и задать желаемые цвета Запустить создание wotmod-файлов, нажав на кнопку "Создать моды". Дождаться завершения работы консольного приложения, после чего можно играть в игру. Обратите внимание! Моды по умолчанию сохраняются в папку "World_of_Tanks\mods\X.X.X\MCTCreator\". При выходе обновления игры или нового патча моды следует ПЕРЕСОЗДАВАТЬ ЗАНОВО!, при этом старые версии модов программа найдёт и удалит самостоятельно. Если вы играете с клиентом x64, то при создании модов НЕ ОТКЛЮЧАЙТЕ! галочку "Разбить пакеты на части по 2 Гб" Скачать: MCTCreator_2.1.3.226.zip __|__VirusTotal - 1/63 __|__Старые версии тут История версий: Ключи командной строки для запуска в консольном режиме с параметрами: Примеры запуска в консольном режиме с параметрами: Коды ошибок, возвращаемые консольной программой (ExitCode):

Исправил. Обновил скрипт в аддоне Режим прицела.

Ага, оно самое. Но спидометр это не исправило =/

The WNEfficency website has been dead for a long time, so I restored this information from there in case anyone needs it. Some of the information may be outdated, but the basics are still useful. Contents Contents Introduction Why WN8? How is WN8 different? Dmg/tier vs Per-Tank ratings Scale Limitations and Threats to Validity WN8 variability vs tier played Scenario 1: Keep playing a D1 Scenario 2: Play an IS-6 TL;DR Nuts & Bolts The Major Assumption of WN8 Data Sourcing Data Validation Expected Stats Matrix The Steps of WN8 - The Formula Step 1 Step 2 Step 3 Periodic Updates Summary, TL;DR Intro Main differences with WN7 Interval/Ratio scale explanation Per-tank stats explanation Brief explanation of the formula and how it was devised (Eureqa) Color Scale FAQ & responses to uninformed criticism Other Languages Credits Introduction WN8 is the latest iteration of the WN8* (WNx) project lead by Praetor77. WN8 seeks to measure the observable contribution to matches, across an account, and hopefully infers some information about the latent variable "skill". WN8 should not be considered the be-all-end-all of skill evaluation. It is intended to be looked at next to win-rate, battle count, average tier, and will never replace the inspection of the Service Record or platooning with someone or watching their replays. This is because WN8 cannot capture things like timing, target priority, teamwork or decision making abilities. Why WN8? As with all ratings before it WN7 had some weaknesses and limitations. Some of these were known at the time of release of WN7 and others were discovered and publicized shortly thereafter. In order of seriousness, as judged by the WN* team: Damage per tier scaling – namely that while tier is a nice linear 1-10, damage values scale up in a curvilinear fashion. Also, damage dealing capabilities are hardly balanced across all tanks of the same tier (think T40 vs A-20 for example or the ARL V39 and M18). Kill per tier scaling – lower skilled players are found in lower tiers, and thus getting kills at tier 1 is easier than getting kills at tier 10, holding constant for player ability above a certain threshold. Tier 1-10 problem – because of the two issues above, the tier 1-10 problem arose with WN7. Precambrian explained this very well in this post, which has some out of date info it, but still captures the problem very well, on a small, understandable scale. It is excerpted it below. precambrian: What complicates the metric is the fact that it is easier to rack up amazing stats at lower tiers than it is at higher tiers, since at lower tiers, the average skill level of new players is extremely low, and the damage potential of low tier cannons, relative to the small hitpoint pools, allows experienced players to destroy their noob counterparts without any difficulty whatsoever. This phenomena is perfectly illustrated by tier 1 autocannons, which can clip out opposing tier ones before the new players even can turn their turrets and react. This sort of destructive potential allows players with relatively low skill to win an extraordinary portion of low tier matches and inflate their stats. WN7 sought to address this by slapping on a low tier penalty; however this is easily avoided simply by alternating playing higher tiers and lower tiers. Take the following example (the categories are as follows:Tank, Result, Survived?, Damage Dealt, Damage Received, Kills, XP, Detected, Capture Points, Defense Points, WN7): If you were to average the individual WN7 values of these games, you would arrive at 2578. However, if you average all the stats of the individual games together, and then calculate the WN7, you arrive at 3260 WN7! There are multiple reasons for this. One has to do with the nonlinear nature of hitpoint scaling; a tier 8 does not have 8 times the hitpoints of a tier one, and thus much more damage can be farmed in tier 8 matches. Also, it is very easy to rack up kills in a tier one tank, skewing KPG upward. Ultimately, average tier gets skewed far lower than average damage does, and KPG gets skewed upward, causing a humongous differential in WN7 when calculated this way! Now consider what would occur if I averaged all the stats of the tier 8 tanks, without considering the Cunningham game. The result would be 2960 WN7. So although the WN7 of the Cunningham game, considered individually, was below 1600, it HUGELY inflates my stats when included in the calculation! Obviously small sample size is small but you get the idea. SPG and LT – Finally, these classes simply don’t output similar numbers to their per tier counter-parts. HT/TD/MT can be roughly comparable, but a tier 8 LT doesn’t put out the dmg or frags of the ISU/IS-3/T69/50 100. SPGs who scout are doing it wrong (and thus their spots should be a bit lower), and their damage values can be very high in some tiers, particularly before they were re-classified in patch 0.8.6 (although they a now lower due to the DPM changes)! How is WN8 different? Dmg/tier vs Per-Tank ratings WN1-7 and Efficiency v1 and v2 were all formulas directly applied to WG’s web API released stats, they selected different weights for each value, and transformed them, to try to make a meaningful total rating value. However, the problems listed above persist for any rating that uses “dmg/tier” computations. There is no way to get around the problem that damage isn’t worth the same (or as much is available) per tier, nor that kills weigh more or less by tier. So in WN8 we’ve adopted an entirely different method. We’re not the first to use this method, Mr. Noobmeter’s Performance Rating has used a per-tank rating since its inception, and while PR was initially skeptically received because the formula was closed source, Mr. Noobmeter released it months ago and explained its formulation. The per-tank ratings are significantly harder to develop (getting good data) and apply (requirea lot more computation power) but the results control for the tank composition of an account history in a way that dmg/tier method ratings can never duplicate. So WN8 becomes a “per-tank” rating, instead of a “dmg/tier” rating. This is why you won’t see the average tier term in the final equation, although the information from which tiers were played is in the methodology, in the earlier steps. So part of the information in WN8 now includes both the tanks a player has chosen, but also the number of games played on an account. Scale One of the first things a reader will notice is that the scale of WN8 is different than the scale introduced by Efficiency and adopted for WN1-7. The reasons for re-scaling are dependent on some decisions made during the development of WN8. You can see the technical side and logic for this in the Nuts & Bolts section. But the simplest explanation is that the Efficiency scale was not sufficiently discriminating of differentiating between player abilities. Top and bottom ends of the distribution were being compressed. You can see the WN8 scale, overlaid with the WN7 scale, and noobmeter’s PR below The upshot of this scale change is that the value of WN7 isn’t really comparable to WN8, even though they are both generally 3-4 digit numbers. We realize this is an inconvenience, especially as all of the color cut-offs also moved (the ones on the bottom are for WN8). However sometimes scales need to change or be re-centered or re-zeroed. See the Fahrenheit/Celsius/Kelvin scale for a physical science’s reference, or the College Board’s SAT history for examples of scale evolution. As before, a very small number of players fall in the extremes of the scale, and the majority of the differentiation is being applied to the middle of the population. Limitations and Threats to Validity History – Myriad things have changes since WoT was released and accounts began accumulating stats. Tier changes (T30, T34, IS-4, Batchat 25t, AMX LTs, arty, MT-25, VK2801, etc), balance changes, mechanics changes (physics, premium rounds for credits, 2 sigma shell distribution, +2/-2 MM) are easily pointed to. Things are not the same now, as they were, and they will also be different in the future. The WN* team fully recognizes that history is always a threat to validity of measurements, but because we can do nothing about it, we always remind people to check Service Records and ask questions if they need to know more about someone’s account history. WG is terrible at book-keeping. They could have left everyone’s T-50-2 stats in place, and published a new tank ID for the MT-25. We wish they had done so (same for all the tanks every moved or replaced). But in reality, 60-day or recent battle stats will have to do. Maturation – players, both individually and as a group, can get relatively better or worse over time. There is more info out on the web now than there was in 2011, and so player progression can be faster or slower depending on how much they can and do research the mechanics and meta-game of WoT. Additionally, since dossiers are always over-time, major changes in performance can take a long time to influence over-all or cumulative ratings, especially at higher battle counts. Damage Upon Detection – WG has indicated that this might be included in the API stats sometime in the future, but right now it is not available. Although DUD is a big part of quality play, especially LT play, we did manage to get a much better rating of LT players, even without having DUD data. Hooray for per-tank methods! Heavy play in a single tank – This makes WN8 work less well, because some folks will play so many games in a single tank that their account WN8 begins to approach the values for that single tank. But WN8 was formulated around whole accounts, not single tanks and while there is an assumption for playing a variety of tanks, that assumption is much weaker than in WN7 and prior ratings. At some point, someone can play enough games in a single tank to “break” the normalization assumptions of WN8. How many games is enough to break it? We have not conducted a formal analysis, but as a rule of thumb, wewould suggest that if someone has more than 50% of the games on their account in a single tank, it might be enough to make WN8 invalid. But as a reminder, it is OK to play a tank you like for thousands upon thousands of games. WN8 isn’t “penalizing” you if you do so, it just makes it hard to compare your account to everyone else’s account. We cannot account for all the outliers! Per-tank variability – Related to the above, although WN8 uses per-tank values, the variation possible (and observable) among tanks is not the same. To use an in-game example, lets consider the T49 vs the AT-2. The AT-2 being slow, blind but heavily armored is going to see a smaller range of possible stats than the T49, also a tier 5 TD. The T49 is fast, fragile and a camo master, but those attributes generally result in either much greater or much worse stats compared to its median values. The AT-2 will have less variability than the T49. So even though we have well-sourced average values for the AT-2 and T49, in the population you will see much higher and lower performances in the T49, than in the AT-2. WN8 does not include a per-tank variability factor in its weighting. We didn’t feel that the data available was sufficient to give good estimates, and the WN8 was already several orders of magnitude more complex to calculate compared to WN7. As the WN* team does not run the servers which make WN* calculations available to the public, we elected to leave exploration of per-tank variability factors to WN9 or later. For an example of per tank variability, and the math on why tanks with higher means or variability move your rating up faster (with good play) check, see this examples: WN8 variability vs tier played Here is an example, authored by Praetor77 and juicebar (who brought up the issue of how WN8 varies over time according to tier played), for how variability and tiers have effects in WN8. If you aren’t capable of reading and internalizing math, then just skip to the TL;DR. For simplicity this example only deals with one stat, damage, although of course WN8 would also take into account frags, defense, spots and winrate. Let us say in the past you have played 1000 games each in a Pz.Kpfw. 38H 735 (f) (300 average damage, below the expected value of 352) and 1000 games on a D1 (241 average damage, same as expected damage). Total damage: 1000*300 + 1000*241 Total damage: 541000 Expected total damage: 1000*352 + 1000*241 Expected total damage: 352000 + 241000 Expected total damage: 593000 rDAMAGE: = DAMAGE/expectedDAMAGE = 541000/593000 = 0.912 rDAMAGEc = (rDAMAGE – 0.22) / (1 - 0.22) = 0.89 Over time, your skill has increased and matured, and now you are capable of playing all tanks well enough to reach expected damage values. Scenario 1: Keep playing a D1 Play 1000 more games in a D1. Still doing 241 average damage (same as top players average). Total damage: 1000*300 + 1000*241 + 1000*241 Total damage: 300000 + 241000 + 241000 Total damage: 782000 Expected total damage: 1000*352 + 1000*241 + 1000*241 Expected total damage: 352000 + 241000 + 241000 Expected total damage: 834000 rDAMAGE: = DAMAGE/expectedDAMAGE = 782000/834000 = 0.937 rDAMAGEc = (rDAMAGE – 0.22) / (1 - 0.22) = 0.92 Scenario 2: Play an IS-6 Play 1000 games in an IS-6. Doing 1415 average damage (same as expected damage). Total damage: 1000*300 + 1000*241 + 1000*1415 Total damage: 300000 + 241000 + 1415000 Total damage: 1956000 Expected total damage: 1000*300 + 1000*241 + 1000*1415 Expected total damage: 352000 + 241000 + 1415000 Expected total damage: 2008000 wn8alpha2 damage: 1690*.71*2970000/3029000 rDAMAGE: = DAMAGE/expectedDAMAGE = 782000/834000 = 0.974 rDAMAGEc = (rDAMAGE – 0.22) / (1 - 0.22) = 0.967 This is simple math. If you add the same value to the numerator and denominator (playing a tank at exactly the expected damage value), the resulting ratio will be bigger, while the added value is larger. We could make a million different examples, but all this is saying is that your average damage ratio and your WN8 changes faster (in fewer games) if you use higher tier vehicles. If you played enough games on D1 to do the same total damage as 1000 games on IS6, your rDAMAGEc and WN8 in both cases would be identical – but the D1 would take almost 6 times as many games TL;DR Trying to explain this more clearly, if your present skill level is well above what is reflected in your average stats, your rating will change to reflect your present skill level faster ( in less games) if you play high tier tanks, than if you play low tier tanks. This is true as long as your playing level in high tier tanks is just as good as your playing level in low tier tanks. This goes both ways. If you are consistently playing worse than your average, your WN8 will drop quicker if you play high tier tanks than if you play low tier tanks. If your skill level at present is about the same and has remained constant throughout your playing of your account, your WN8 should not change much, regardless of your choice of tanks Nuts & Bolts The Major Assumption of WN8 WN8 makes a major assumption that is not shared with any previous rating system. We set expectation for mean performance players, based on their ability to influence the games played. This is a tricky concept, and one certainly open to debate. But basically, we hazard that there is an amount of output (dmg/frag/spot/def) that influences the outcome of the game (in terms of win-rate), but that there exists a baseline below which the output does not influence the outcome of the game regularly enough to be determinable. The exact value of this threshold was computed and then subtracted (the rSTATSc step, below) to compare all players to the theoretical (and sadly real) player(s) who do not perform enough measurable output to influence their win-rates beyond simply loading in and having MM weigh. The advantage of this assumption is that it makes the rating more meaningful for both high and low values. There were “free” points in WN7, basically for showing up, because virtually no accounts manage to accumulate ZERO stats, even the worst programmed bots. But many accounts do manage to accumulate so little stats that they do not manage to positively affect their win-rates in any measurable way. By adjusting for these baseline values, we get better differentiation at the lower levels, and also at the upper levels, because we’ve removed “noise”. And of course there is also better differentiation in the middle. We are postulating a “zero” point, below which manifest stats (damage/spots/frags/defense) don’t influence win-rate meaningfully. As noted earlier, this assumption is open to debate. Please bring a solid knowledge of stats and measurement as well as tanks to this debate though! Conveniently, this also turns the interval scale used in efficiency, PR and WN7 into a pseudo-ratio scale, which brings about numerous advantages. Debatably the most important one after improved accuracy in measurement is that by applying a baseline we can now say that a 2400 WN8 player contributes twice as much for his team to win than a 1200 WN8 player. This was not true for any rating before WN8. Data Sourcing Because WN8 was a per-tank rating, we needed data per tank, which as always is not available via the WG web API. We turned to Phalynx of vBAddict.net, who kindly handed over his database of 17k dossiers. The database was filtered for players with less than 1000 games played, and tanks that were played for less than 50 games. From this database we determined, using linear regression the stats to be expected on each tank for a median ability player. For each tank/player combination, we calculated playerWN8alpha and tankWN8alpha. WN8alpha was approximately WN7 in formulation, basically a means to measure per tank effectiveness. Afterwards, we filtered to the 50% of players who play that tank, who perform well ON THAT TANK, not overall. This incorporated a good mix of high win-rate and low win-rate players. We posit that using the top half of players in a given tank is a good way to compare tanks to each other, since they can squeeze out every last ounce of performance a tank has to offer. Otherwise, at the low end, you would be comparing tanks based on the performance of players who don´t know basic mechanics, or how to properly use a given tank. That being said, I use the top 50% of players to do the linear regression, because simply using the top player values would be biased and not generalizable to the entire population. To check that expected stats for each tank were balanced, we looked at the tankWN8/accountWN8 ratio. We checked that the players with top 10% tankWN8/accountWN8 corresponded to about 1.15 for all the tanks in the game. When a tank had a lower ratio, for example, we lowered the expected values used to regress with the top 50% of players, and then checked what the top 10% ratio was. This took several iterations of recalculating tankWN8 and playerWN8 until a balance was reached, and tankWN8/accountWN8 was about 1.15. The purpose of this was to try to, controlling for player skill, determine expected values which would normalize the dmg/frag/spot/def outputs across tanks. To find out how much dmg the same player would do in the ARL v39 and M18 Hellcat, given all other things being equal. A handful of tanks required a more in depth analysis of the distribution of the tankWN8/playerWN8 ratio, due to an abnormally low number of high level players playing the tank (A-20), or due to gross nerfs/buffs (like M41). We tried to come to a middle-ground for tanks that have been severely nerfed/buffed (like M48A1, AMX50B or T110E5) looking to get a wide representation of players that played the tank during different time periods, so that the value doesn’t simply represent the tank´s original or current most powerful state ( so that players who play it while better balanced do not get unfairly treated) or completely ignores it (so that players who played it while very powerful, and then never again, do not get unfair bonuses). Note: This manual process was the most scientifically weak portion of the WN8 creation. However, personal bias of the creators was not introduced during this section, and the team of individuals working on these adjustments comprised of dozens of contributors on WoTLabs combing the per-tank tables and collaboration between players from NA, EU, SEA and RU. When possible values from the “nearest possible match” were used for tanks with oddly distributed player histories, like the A-20, in which no one can be bothered to even try (the data shows this…). If you are upset over this manual process, please contribute to further refinement of the WN8 per-tank tables, by uploading your dossier at vbaddict. Also, the per-tank expected values table were compared with the table used for the PR rating by Noobmeter, and a table of top 1%/100 players of each tank for the RU server kindly provided by Seriych (similar to what was in the service record with XVM for 8.6 and older). Most expected damage values are pretty close with noobmeter´s (from tier 3-8 ), and if you multiply those damages by 1.5 (to see what a 2400 WN8 player would need to get on a tank), you get unicum values, which are quite close to Seriych´s values for top player numbers from RU. Also, using this approach resulted in numbers for low tier tanks that are obviously high for the new player, but that isn´t really an issue since average players only have 3% or less of their total games in tier 1. This conveniently also functions as a control against seal-clubbing your way into a high rating. It means you can still club tier 1 players, you just have to actually be good at it! No longer will averaging 1.7 kill/game (a good value in tier 10) at tier 1 make you appear good. This isn’t because the WN* team has any bias against folks who play low tiers, but simply that we wish to identify player skill irrespective of tier played (review the Why WN8? for reasoning). Reminder: What actually MATTERS from the table is the relationship of values between different tanks. We could divide all those values by 3, and it wouldn´t make a difference. It’s the relationships between the numbers that are important, not the actual values. Same goes for the 1.15 ratio used in balancing tanks, we could have used any number. We left them in “WoT dmg scale” for readability and ease of sourcing though! Data Validation A dataset of all players with more than 10000 games on several servers was kindly provided by Mr. Noobmeter (we needed games played on each tank), a 4GB database that can hardly be opened in Excel! Nevertheless, we filtered EU and NA only players from there, to end up with a 115000 player database, which is about as large Praetor77’s limp PC can handle. With this database, we determined expected stats, rSTATS and then rSTATSc. Using all the rSTATSc values, we used Eureqa (a very nice and intelligent program which uses iterative genetic algorithms to search for mathematical relationships between a set of input data) to determine the optimum mathematical formula which using the rSTATSc could “explain” (fit) the rWINc of the players in the database. By data analysis, we found that some players were clearly outliers on some rSTATSc (all of them except rDAMAGEc, actually), which lead us to implement a series of “caps” or maximum values to improve the usefulness of WN8. These same stats also seemed to be more correlated to rWINc individually only up to a certain value, after which the correlation decreased substantially. The caps implemented were: rFRAGcMAX = rDAMAGEc+0.2 rSPOTcMAX = rDAMAGEc+0.1 rDEFcMAX = rDAMAGEc+0.1 We re-entered the capped rSTATS into Eureqa which actually came up with a very similar solution as prior to the caps, but handled lots of outlying accounts. The final formula output was: rWINc = 0.09 + 0.613*rDAMAGEc + 0.131*rFRAGc*rDAMAGEc + 0.097*rFRAGc*rSPOTc+0.047* rFRAGc*rDEFc Then we multiplied every term in the formula by 1600, which leads to a similar central value for the players in the database as for WN7, which should make the server-wide WN8 average quite similar to WN7, in the 900-1000 range. Expected Stats Matrix You can view the expected tank values here: https://modxvm.com/en/wn8-expected-values/ The Steps of WN8 - The Formula Step 1 rDAMAGE = avgDmg / expDmg rSPOT = avgSpot / expSpot rFRAG = avgFrag / expFrag rDEF = avgDef / expDef rWIN = avgWinRate / expWinRate Step 1 takes the counts of tanks played on account, and multiplies them by the expected stats to get the account total expected values. Then the actual account totals (your total dmg, frags, spots, def, win-rate) are divided by the total expected values to give the ratios. Step 2 rWINc = max(0, (rWIN - 0.71) / (1 - 0.71) ) rDAMAGEc = max(0, (rDAMAGE - 0.22) / (1 - 0.22) ) rFRAGc = max(0, min(rDAMAGEc + 0.2, (rFRAG - 0.12) / (1 - 0.12))) rSPOTc = max(0, min(rDAMAGEc + 0.1, (rSPOT - 0.38) / (1 - 0.38))) rDEFc = max(0, min(rDAMAGEc + 0.1, (rDEF - 0.10) / (1 - 0.10))) Step 2 sets the zero point for the ratios. See the assumptions section for more info on why this happen. min and max are functions to ensure the ratios stay within bounds. The constants are in the format of (rSTAT – constant) / (1 – constant) To normalize that, a player with all rSTATSc = 1 would receive 1565 WN8. A player with all rSTATS = 1 would also have all rSTATSc = 1 because (1-c)/(1-c) = 1. Step 3 WN8 = 980*rDAMAGEc + 210*rDAMAGEc*rFRAGc + 155*rFRAGc*rSPOTc + 75*rDEFc*rFRAGc + 145*MIN(1.8,rWINc) Step 3 takes the weighted (in Step 1) and normalized (in step 2) performance ratios and processes them through the coefficients determined for the final formula, reported above. This puts the scale on the more meaningful 0-5000, gives the relative weights of damage and reflects the interactions between frags*spots, def*frags and dmg*frags. A Note on Interactions If you played 5000 games on T50, and the expected spots are 4 per game, and you average 4 spots per game, your rSPOTc is 1. If you played only the E100, and the expected spots are 0.88 per game, if you average 0.88 spots per game, your rSPOTc is also 1. So rSPOTc does NOT measure how much you spot, it measures how much you spot in comparison to how the median player would spot playing the same tanks as you. As such rSPOTc correlation with winrate is significantly higher than for average spots: And also, in the WN8 formula rSPOTc and rDEFc are multiplied by rFRAGc, which after which those terms are well correlated with winrate (as measured by rWINc)… So, rSPOT*rFRAG appear to measure something important for winning. These interactions seem to be properly measuring players that can do multiple things and adapt to what needs to be done to win as opposed to players who play absolutely safe, and simply deal out damage (rDMGc only). Per player analysis indicated (and Eureqa agrees apparently) that rFRAGc *rSPOTc can tell you a lot about how much a player actually manages to win. The authors believe it has to do with aggresiveness and willingness to create opportunities for the team. If you are solidly getting high rSPOTSc values, you are putting yourself in more risky positions on the map, and if you are doing so while maintaining high avg frags, damage, defense and wins, IMHO you are a better player than if you manage the same damage and frags sitting in the back and shooting targets your teammates light up. The most often repeated advice in this game is “get your gun in the game and stay alive to keep it there”, and rSTATc values appear to support that advice. Periodic Updates As tanks and players change over time, WN8 was developed with the intent of periodically updating the expected values to ensure that the relative performance of tanks, and the measured performance of the players who play them, remains accurate. The update methodology was developed 6 months after WN8 was originally introduced, and is implemented in a script written in R to ensure that the process is repeatable and, for over 95% of tanks, does not rely on manual adjustments based on subjective opinion. Using dossier data from vBAddict, filtered as explained above, a plot is generated in R that shows for every tank, and for every rSTAT (rDAMAGE/rFRAG/rDEF/rSPOT/rWIN) the 'dot plot' of every users rSTAT in that tank, vs every users overall rSTAT for all tanks. Here is an example, which is the rDAMAGE plot for the Type 59: The least squares line of best fit - the red line - crosses the user account rDAMAGE at a value of 0.953. This is the 'correction factor' that must then be applied to the expected damage value for the Type 59 in the update. These factors are automatically generated and applied for all 5 STATs for all 350 tanks in the WG API. For the handful of tanks where there is insufficient data to produce an acceptable line of best fit, these tanks are given the same values as a similar tank of the same tier and type. All players who would like to see WN8 become more accurate, and avoid the need for manual corrections of this nature, are encouraged to download use the vBAddict ADU Active Dossier Uploader to upload their dossiers and Battle Results as they play, so that WN8 - and vBAddict - gets more good data. (Gryphon, June 2014) Summary, TL;DR Intro WN8 is the latest iteration of the WN8* (WNx) project lead by Praetor77. WN8 seeks to measure the observable contribution to matches, across an account, and hopefully infers some information about the latent variable “skill”. WN8 should not be considered the end-all-be-all of skill evaluation. It is intended to be looked at next to win-rate, battle count, average tier, and will never replace the inspection of the Service Record or platooning with someone or watching their replays. This is because WN8 cannot capture things like timing, target priority, teamwork or decision making abilities. Main differences with WN7 WN8 has much more weight on damage than on kills, which was reversed in WN7. What allowed us to put more weight on damage was that WN8 uses per-tank normalization instead of the average tier-based normalization WN7 used. Per-tank normalization in WN8 now allows a fair comparison of players playing only highly effective tanks for their tier (think Wft100, Foch155, Hellcat, T49, T18, T29, the old Su-26, etc.) versus players who have played many lines, with many tanks. Due to per-tank normalization, light tanks and SPGs are now more fairly compared to other tank types in WN8 (they received lower WN7 than other tank types). Despite not being able to use spotting damage, WN8 expects less damage of light tanks, while WN7 expected the same as other tanks of the same tier. No tier-based penalty is introduced. Low tier tanks are measured fairly against high tiers, whereas in WN7, you could raise your score artificially by playing a mix of low and high tiers, and were penalized if you only played low tiers. However, you are expected to do VERY well in low tiers to gain WN8 points as opposed to playing high tiers. Scale has changed. See below. Interval/Ratio scale explanation WN8 uses a different scale from WN7. WN7 values ranged from 400-2800, and we turned this scale into a ratio scale, which brings about numerous advantages. Debatably the most important one after improved accuracy in measurement is that we can now say that a 2400 WN8 player on average contributes twice as much for his team to win than a 1200 WN8 player. This was not true for any rating before WN8. Per-tank stats explanation Briefly, what we have done is used vBAddict database (more than 1 million tanks played by about 20000 players) to calculate balanced and comparable “expected” values for each tank. The number of games you have played on each tank allows us to estimate what your “expected” total stats should be for your entire account. Then your actual total stats are compared to the expected stats ( rSTATS), which are then normalized and adjusted to a baseline (rSTATSc), and these numbers are then input into the formula shown below. rSTATSc are capped to prevent, for example, farming spots on tanks with low expected value of spots, like arty. Brief explanation of the formula and how it was devised (Eureqa) Using a subset of the noobmeter.com database (115k players), we used their stats as input to a program called Eureqa which uses genetic algorithms to find the best “formula” to explain winrate using the rest of the stats. So, Eureqa assigns weights to each stat according to how important it is in determining wins. The final formula is: WN8 = 980*rDAMAGEc + 210*rDAMAGEc*rFRAGc + 155*rFRAGc*rSPOTc + 75*rDEFc*rFRAGc + 145*MIN(1.8,rWINc) Color Scale https://modxvm.com/en/ratings/xvm-scale/colors/ FAQ & responses to uninformed criticism Is WN8 calculated on a per-tank basis? No, WN8 is calculated based on the only data available through the API, which is games played in each tank, and aggregate stats for damage, kills, spots and defense. However, from a 20000 player vBAddict database, the average error introduced to WN8 by using aggregate data instead of averaging per-tank WN8 (weighted by battles on each tank) is 2.15% of the total WN8 score, while 95% of players have an error under 6.3% of their total WN8 and 99% of players have errors under 9.2% of their total WN8. Other Languages Русский/Russian Deutsch/German Credits Praetor77, bjshnog, Crabeatoff, Mr. Noobmeter of NoobMeter.com, seriych, Phalynx of vBAddict.net, Orrie, Twistoon, NextToYou, Folterknecht, Precambrian, HibachiSniper, HubertGruber, juicebar, perpixel, sr360, jacg123 and anyone else we might have forgotten (sorry!). Neverwish, Allurai, Mr. Noobmeter and stumpjumper8 also get shout outs for their websites, which let us carry on our work and implement it for the public to use. Thanks everyone!

Попробуйте, пожалуйста, вариант из сообщения #531454 У меня на евроаккаунте. нет арты, поэтому не могу проверить, я его создавал только для скачивания мода с евросервера 7 лет назад и не играл на нем. Отпишитесь, пожалуйста, если прицел работает.minimapACCAzoomEU.wotmod Вопрос к скачивающим, какой формат архива удобен zip или 7z? Дело в том, что zip может быть открыт без установленного архиватора, а 7z лучше сжимается и меньше файл для скачивания.

Мод работает на версии игры 1.20.0.0 на еу регионе и на версии 1.19.1.0 на рубу регионе. Костыль для работы мода не нужен.

@[email protected] не понимаю что это за версии такие кстати, я обновил еще немного плагин, теперь материалы с атласами загружаются куда лучше(даже смешивание добавил)

Two main differences 1) different SSL backend * BigWorld.fetch() --> libcurl --> Windows Secure Channel * urllib1/2/3 -> CPython _ssl -> OpenSSL The CPython _ssl module supports TLS 1.2 since version 2.7.9, but WoT used Python 2.7.7 before the v1.18.0 release, which made BigWorld.fetch() the only possible way to communicate with hosts supporting TLS1.2 only. Since WoT 1.18.0 the game client switched to 2.7.18, this problem solved. 2) BigWorld.fetch() supports async-style and invokes callback on response ----------------- for XVM we use urllib3 + certifi to unify the network stack with other middlewares (sentry-python uses urllib3, so here we are) in general, BigWorld.fetch() looks like a more flawless solution for WoT.

Только одно, какой то мод устаревший и конфликтует с миникартой, обновите все моды

- Адаптация к патчу 1.19.0.2

@Lom Попробуй использовать полную библиотеку, без переписанной локализации, возможно ты что-то упустил. Скачать можно из интернета, если не найдёшь, могу свою скинуть

Обновил в шапке скрипт myHP.py из аддона Очки прочности своей техники.

@steaxch Режим "Натиск" прячется под цифрой 43, добавляем просто в includeBattleType Будет время - возможно добавлю в мод сразу. Пока что - дичайшая нехватка по добавлению новых фич в моды. Что мои, что тех, что я поддерживаю.

Ну да, ведь это же в евро-регионе за десять лет запилили 10-12 серверов, а не жалких 2, потому что играть тупо некому. Игрой WG по настоящему никогда не занимался. WOT уже много лет, это дитище филиалов, прокладок и аутсорсеров по всему миру. Потому нет ни какой разницы кто там будет апдейты пилить и с чем - Майк из Конберры или Пашка из Минска. А самолеты - тут совсем не причем. Тема самолетов - никому массового не зашла ибо игры про самолеты унылы сами по себе.

Думаю на этой ноте буду заканчивать деятельность связанную с WoT. Ибо для меня уже подобное увлечение не приносит удовольствия. В саму игру я уже давно не играю, последнее что меня держало в ней это два режима (Стальной охотник и Линия фронта). Первый уже мне не так интересен, а второй после переделок вообще не заходит. Продолжал лишь обновлять моды/конфиг/сборку можно сказать что по привычке. Это всегда для меня было лишь хобби которое никогда не приносило никакого дохода. И занимался я этим лишь до того момента как было это самому интересно. Сейчас же интереса совсем не осталось, да и времени тратить уже самому на это все не хочется. Думаю стоит сказать спасибо тем кто пользовался по сей день моими поделками P.S.: Тему на какое то время пока оставлю открытой, но через определенное время закрою её.

Так и непонятно.. А зачем, а зачем.. Карты запускаются и можно кататься хоть на одной карте? Или это только вход в ангар и всё?

1. Установка Wine sudo apt-add-repository ppa:ubuntu-wine/ppa sudo apt-get update sudo apt-get install wine 2. Установка зависимостей через winetricks winetricks d3dx9 d3dx9_43 d3dcompiler_43 lucida ie8 msxml6 vcrun2008 wininet 3. Установка WoTЗагрузите клиент для EU, NA или RU регионов и установите игру. Вы также можете использовать клиент, предварительно установленный на Windows. Обратите внимание: производительность WoT на NTFS разделах ниже, чем на ext* разделах. 4. Установка XVM Загрузите релиз XVM или ночную сборку Распакуйте архив в папку, где установлен WoT. В папке res_mods/xvm/configs/ переименуйте папку Default во что-нибудь другое, например ваш ник (в данном примере используется koreanrandom). В папке res_mods/xvm/configs/ переименуйте файл xvm.xc.sample в xvm.xc (т.е. уберите расширение .sample) В файле res_mods/xvm/configs/xvm.xc, который у вас получился после переименования, укажите путь к вашей конфигурации: ${"/koreanrandom/@xvm.xc":"."} вместо стандартного ${"Default/@xvm.xc":"."} В файле res_mods/xvm/configs/koreanrandom/rating.xc измените значение параметра showPlayersStatistics на true (по умолчанию стоит false). 5. Запуск WoT 5.1. Только одна видеокарта Дважды щелкните по WorldOfTanks.exe или выполните wine WorldofTanks.exe в терминале. 5.2. Intel HD graphics + NVidia Optimus (bumblebee) выполните bumblebee wine WorldofTanks.exe в терминале 5.3. Intel HD graphics + NVidia Optimus (PRIME) 1. Откройте Nvidia X Server Settings 2. Включите видеокарту NVidia в PRIME profiles 3. Выйдите из системы и снова зайдите в неё 4. Дважды щелкните по WorldOfTanks.exe или выполните wine WorldofTanks.exe в терминале.

@freak527 bigworld.key 和 loginapp的私钥和公钥放入到对应的目录了吗？ 或者你可以把错误的日志信息截图

Здравствуйте, друзья! Подскажите, пож-та, как убрать звуки, при загрузке игры до входа в ангар? С уважением.

@DemouN carouselNormal.xc проверь параметр с дефолтным значением: // Spacing between carousel cells. // Отступ между ячейками карусели. "gap": 10,

у меня в gui-part1.pkg две ,а в gui-part2.pkg 8 картинок. Попробуй заменить заглушками.

Ещё раз chancePenetration.py

привет народ! подскажите: как исправить проблему!???----я собираю хум в папке res-mods , извлекая из архива в папке mods версия обновления---- получаю (папку рес а в ней гуи-мод-скрипт) папку мод перемещаю в папку ресмод где версия обновы танков,--все работает ,но есть проблема с маркером типа техники пропавшей из засвета -за места маркера типа танка -пропавшего из засвета- квадрат !!!!(а устанавливая как предлагает хум , папки (гуи-мод-скрипт) находящиеся в архиве и в папке модс версия обновы--проблемы нет!!!!--- в версии обновы 1.0 игры танки, проблемы не было ---кто в курсе где они пути поменяли чтоб использовать только формат (*.wotmods)??????--зарание спасибо

Еще как актуальный. Актуальность не по дате смотри, а тексты коммитов почитай и вспомни когда и какой был последний микропатч. При каждом мелкопатчике на 3.5 обновленных файла нет смысла делать новый коммит. В прочем, все равно своим пользуюсь.