Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The interrogate function I'm currently drafting, so it failing is normal. I specifically gave it yellow fail logs, not game breaking.
The red wall-of-text afterwards is not thrown by Fog-O-Pawn.
It begins inside VEF (VEF.Pawns.StatPart_RangeAttackSpeedFactor.TransformValue).
VEF 1.6 still references fields that were removed/renamed in the game DLL, so its
static constructor crashes and triggers a cascade of
TypeInitializationException / NullReferenceException.
Fog-O-Pawn’s two stat-worker postfixes appear in the stack trace only because every
call to StatWorker.GetValue() passes through them once the VEF code has already
exploded.
At the 26th, I'm not getting this VEF error anymore.