Установить 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 (вьетнамский)
Українська (украинский)
Сообщить о проблеме с переводом
I think it's due to the random improvement function of the mod. The same turn that Player 1 got a free Fishery at his capital Player 2 had a splash of vision there and meeting. Oddly enough it doesn't seem to happen for human player 1, only additional human players because P2 also had an unexpected meeting with an AI player previously but nothing happened with P1 in that event.
This appeared during an autoplay session, so I can't really pinpoint what exactly was happening when it occurred. However, there was no crash, and the log indicates that other reward(s) were successfully granted before and after this occurred. Upon examining the line in question, I'm guessing there's an issue when the Player ID returned by Events.GoodyHutReward is -1, nil, or otherwise invalid.
With this code present, the error has not manifested in several subsequent autoplay sessions. However, the following error has occasionally appeared, usually following a random unit reward:
Runtime Error: bad argument #1 to 'func' (integer expected, got nil) --> \Sailor_Goodies_Scripts.lua:453: in function 'Sailor_Goody_RandomUnit'
The line in question is:
Within said file, iNumberWaterTiles only appears in this line.
- Reloaded a save game.
- Closed the game, deleted the database cache, and reloaded a save game.
In both cases, the changes persisted. While your issue may very well be occurring (and sucks if so), it isn't one I can reproduce.