安装 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(越南语)
Українська(乌克兰语)
报告翻译问题




1) On Unit Destroyed. This is to be used for a very specific unit. It isn't a unit counter. The field takes in a unit ID (unique). I was about to say the tooltip explains you this, but for some reason this particular tooltip says 'no translation. So I'm fixing that now.
You can get the unit's ID by left clicking on it when it is on the map in the editor (fingerprint icon indicates the field + tooltip)
2) Set fixed income sets fixed income. When you open the scenario's setting, you have a field that says 'fixed income'. This fixed income is as it says 'fixed' and simply is X amount of money that will be added on top of regular income every turn. This should be used to balance scenarios in a fast way, without needing to go over all victory points on the map. If after you made your map the Germans are missing 500 income per turn, you can just write 500 in the fixed income field and they will have their regular turn income + 500. This obviously does not get modified in ANY way, otherwise there would be no point in entering something there. So, no policies, no difficulty, no nothing. If you say it is 500, it is 500, it will remain the same.
3) Set fixed income % will set the fixed income to be a % of the current fixed income. You should enter a number from 0 to 100, as it is a percentage. If your current fixed income is set to 1000, if you execute this event with a value of 25 (%), it will set the fixed income to be 1000 * 0.25 = 250
4) Set fixed income based on turn income % sets the fixed income to be a % of the player's turn income. If the player is making 1000, and you set this event value to be 10 (%), then the fixed income value calculated will be 1000 * 0.1 = 100
This is applied on the regular turn income, not taking into account the fixed income. So if the player is making 1500 a turn (but 500 comes from fixed income) then it will be calculated only on the 1000, without taking into account the 500 from fixed income, which would be breaking the calculations
5) Add / Remove fixed income does what it says. It will add any number you set in that field. So if it is -500 it will remove 500 from the fixed income you originally had. It can take both negative or positive numbers.
And yes you have a 'executions' and 'chance' field. Which do what they say, chance being the % of chance the event actions will execute when even is triggered (0-100%)
And executions is the amount of times the event can be triggered.
Obviously, for one shot trigger, they will not be able to trigger more than once, but this is common sense (Example: On Unit Destroyed, since it uses a unique ID well you cannot have it run more than once)
Just to summarize for myself or any other soul searching for clarity on how income is build up:
total income = base (tiles like cities and factories)(1) + fixed income (2) + other income (conquest, gifts from allies, etc.) - upkeep
(1) - adjusted by policies and Set fixed income based on turn income % modifier
(2) - adjusted by Set fixed income % and Add / Remove fixed income, these are not affected by policies
About event trigger unit destroyed, now I know how it works, but is there any way with today options to check status of army size (and losses) and to make some actions after certain number is reached?
No, events are not in any way capable to be triggered based on those parameters for the time being
I think I will add 2 additional triggers soon: Income > X and Income < X
This should help for some cases (checking the 'health' of a country)
Yes this will do the trick as with time AI is investing a lot in new troops and then it start to suffocate as no enough money to maintain all army in healthy state.
Perfect, thanks.
Will implement within next few days, I got a busy weekend coming up... (IRL)
I have to admit it would be nice to see when hover with mouse over income to see this split like how much is regular income and how much is fixed and in case that turn you get some extra from conquest or from gifts.
This way you can better judge is it worth investing in policies as maybe regular income is not that high and you will get less to what you expected.
I cannot show it in any way as it isn't being tracked
Nothing is, as a matter of fact
I only have a single function called 'AddMoney()' and this is tracked, but there is no 'source' or 'context'
I am not planning on implementing anything alike
Is there any way to grant fixed bonus to side that control VP. I'm talking about fixed income irrespective of gain from that tile itself.
This would be neutral trigger event where controller of the tile gets income fixed bonus.
You cannot have it check who took captured the VP, at least not now
That is why the 'don't fire before' conditions were implemented recently
I hope it is ok to put it here.
I was running more test on my scenario for east front map.
Played myself on soviet side.
Not sure if you have seen but I tried to simulate confusion and unpreparedness of soviet side by reducing per turn income.
I made this using Set fixed income based on turn income %.
it starts with -74% and then with time it goes gradually up (or malus get smaller).
Soviet base is 10580 (or close to it) and initial few turns this is about 2750 base with minus unit upkeep this is less then 1000 netto per turn.
On turn 8 Set fixed income based on turn income % changes to -70%.
with this it slightly improve situation raising base to 3174 and netto is variable depending how many units are lost in these 8 turns (and it is a lot :)...but about 1500 netto.
At this point I selected war economy that gives 15% increase in per turn earning. My netto sudenly jumps to approx 3250. I could not get right calculation for this. Following what we discussed, Set fixed income based on turn income % shall be calculated like base x policies bonus (in this case 1.15) x Set fixed income based on turn income % (in this case 0.3) right?
With this formula it would be:
10580x1.15x0.3= 3650, but instead my base was showing me 4656!!
Only way to get this value is like this:
10580x0.3 + (10580x1.15-10580) = 3174 + (12167-10580) = 3174 + 1587 = 4761
Variable here is some villages and towns being lost.
But in general this is not how it should be right?
And confirmation for this came on turn 20.
At this turn there is new change in Set fixed income based on turn income % that is now -65%.
So if we follow all above I should get more money as in formulas instead of 0.3 I use 0.35. But alas I get less money as now formula was reset and it follows expected one:
10580 x 1.15 x 0.35 = 4258 and this is like 500 less then before!
I would expect that no matter when you introduce policies you will get output as per above formula where policies multiplier is multiplied with other benefits/maluses and all this is applied to base value.
Would be good you can look into this please.
Alright so that's a lot of text and numbers, and I am not sure I understand the issue
I would like to share with you the code used: https://imgur.com/a/QBl5dFm
it should be transparent enough so that a non initiate can still understand what's going on
What I can tell, from what I read, is that any policy is taken into account, when applying the fixed income with % turn income
So, if you are having the +15% income policy, the calculated value of the fixed income will take it into account
base is multiplied by value in editor (I guess this is (int)) and then it is further multiplied by value from event and then divided by 100.
I also explain that after even value changed everything gets as it should but by that moment I was getting more credits.
How often this formula is in place? I mean is it updated only when some of the values are updated or it is calculated every turn?
I mean, it is no big deal and you can ignore this issue.
So it runs once, at the moment of the trigger