Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
Will be looking if I can delay the logging.
This is only an issue if you flee from combat.
So, basically it means that the next battle will not begin with CM Pools set to 0, but will continue with what both sides had from last battle. (annoying, I know...)
The scripting APIs are currently undocumented. Which means trying to utilize the variables being passed from the core game requires a lot of "trial & error" as some could be null or lack meaningful values.
Part of the reason for the excessive logging was to help discover this and then adjust as needed.