Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
Behind the scenes: when any one of us uploads a mod, it checks the delta/changes between the last version and this one to determine when to update that "last updated" timestamp
The main reason for re-uploading the same mod on my end (with no changes needed) is that it changes the Mod Manager's "Yellow Warning Icon" to the "Green Checkmark Icon" in the Mod Manager, which people will bug mod makers about (despite the mod still working OK)
Basically it's just sending a message to CA servers that I checked that the mod was working with the next major patch number (6.2 in this case) and no changes were needed to maintain compatibility
Probably something in Patch 6.2? I haven't gotten around to updating all of my mods for the newest patch, but when I get a spare moment I'll check to see if there are any major issues (and update them for it)
@itachiaurion
Ahh that's a tricky one; when I get a second to update this for 6.2 I'll check that out as well, thanks for the error message! (those do actually help for debugging)
The callstack of the script which established the failed listener is:
stack traceback:
[string "script\_lib\lib_core.lua"]:1908: in function 'add_listener'
[string "script\campaign\mod\!vampire_coast_enhanced_rites.lua"]:121: in function 'vampire_coast_expanded_rites_init'
[string "script\campaign\mod\!vampire_coast_enhanced_rites.lua"]:199: in main chunk
[C]: in function 'pcall'
[string "script\_lib\lib_core.lua"]:714: in function 'load_mod_script'
[string "script\_lib\lib_core.lua"]:647: in function 'load_mods'
[string "script\_lib\lib_mod_loader.lua"]:85: in function 'callback'
[string "script\_lib\lib_core.lua"]:1930: in function <[string "script\_lib\lib_core.lua"]:1930>
[C]: in function 'xpcall'
[string "script\_lib\lib_core.lua"]:1930: in function 'event_protected_callback'
[string "script\_lib\lib_core.lua"]:1991: in function 'event_callback'
[string "script\_lib\lib_core.lua"]:2051: in function <[string "script\_lib\lib_core.lua"]:2051>
stack traceback:
[string "script\campaign\mod\!vampire_coast_enhanced_rites.lua"]:190: in function 'vampire_coast_expanded_rites__trigger_bountiful_treasure_treasury'
[string "script\campaign\mod\!vampire_coast_enhanced_rites.lua"]:134: in function 'callback'
[string "script\_lib\lib_core.lua"]:1930: in function <[string "script\_lib\lib_core.lua"]:1930>
[C]: in function 'xpcall'
[string "script\_lib\lib_core.lua"]:1930: in function 'event_protected_callback'
[string "script\_lib\lib_core.lua"]:1991: in function 'event_callback'
[string "script\_lib\lib_core.lua"]:2051: in function <[string "script\_lib\lib_core.lua"]:2051>
ERROR - SCRIPT HAS FAILED - event callback was called after receiving event [RitualCompletedEvent] but the script failed with this error message:
[string "script\campaign\mod\!vampire_coast_enhanced_rites.lua"]:190: attempt to index local 'item_list_category' (a nil value)
The callstack of the failed script is: