安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题




















It only affects any "Apply Bleed" Trinket from another Mod being equipped to the Navigator.
The Amount & Chance for the Bleed from that Trinket will be affected by the same scaling as Navigator's Sunward Isles Trinket.
Will other modded bleed trinkets not work on any hero or only this hero if this class mod is present in the mod list?
It is definitely possible, but I have no immediate plans to do so.
I’ve had a few ideas for what Navigator’s Vermintide trinket could be in the past but in the end I wasn’t happy with them.
Yeah, unfortunately this is a limitation of the game, it ends combat before the check that restores Volatile is resolved.
Lack of reach and utility - she can hit 1-2 positions (main attack with 80 acc, ouch), apply mediocre debuffs and pull. Lacking reach is pretty big issue. With self debuffs (which apply on missess too), she feels like leper (weak) little sister.
Volatile - 50% of the time it hit targets what she cant reach. With huge debuff to health (antiquarian lvl of hp). On top of this transition from debuffed hp to normal one screwed - with 100% hp if you use volatile and kill target - you will end with less than 100% hp, due to game mechanics.
Without reach her gamplay can be summirise in "Try to use volatile, and be screwed by RNG and 1 hitted by enemy or (badly) cosplay leper". Ofc you can make babysitting team so she can reach volatile target all the time, but its have same issue as babysitting said leper - "just pick hero with better reach and hit target twice".
C:\Program Files (x86)\Steam\steamapps\workshop\content\262060\3232729723\heroes\Navigator
Step 2: Open the Navigator.info file using notepad & scroll to the bottom
Step 3: You should see this:
mode: .id nav_tooltip
mode: .id nav_tooltip2
mode: .id volatile .is_raid_default true
mode: .id stable .battle_complete_combat_skill_id move
If the .is_raid_default true is anywhere other than next to volatile, change it to be there.
if .is_raid_default true is already where it should be, delete the 2 lines with nav_tooltip & nav_tooltip2
This should fix the problem but cause a few of Navigator's skill descriptions to look a bit weird.