Maybe set a max amount of upgrades at one time?
Maybe order by highest amount of waiting cargo to choose the station to be converted first.
register this case and wait a while before trying to upgrade again!
Maybe order by highest amount of waiting cargo to choose the station to be converted first.
register this case and wait a while before trying to upgrade again!
Refactor the parts of this function into separate functions.
Refactor the parts of this function into separate functions.
Do this on a per group basis (each route a group).
That way we can decide to not check a group wich was created less than x years ago.
When maintenance costs are on we should set low profit limit too at least the yearly costs.
Don't sell all aircraft from the same route all at once, try selling 1 per year?
Refactor the parts of this function into separate functions.
Do this on a per group basis (each route a group).
That way we can decide to not check a group wich was created less than x years ago.
When maintenance costs are on we should set low profit limit too at least the yearly costs.
Don't sell all aircraft from the same route all at once, try selling 1 per year?
Think of a better computation than stationcount * 50 since I think maintenance costs don't increase linearly.
Maybe also use InflationCorrection on GetLoanInterval or is that already corrected for inflation?
Maybe also use InflationCorrection on GetLoanInterval or is that already corrected for inflation?
Check if this gets sorted furthest or nearest expire date first. I think the highest value (thus furthest expire date) comes fist
Instead of GetSetting we should define a value for ourselves...
define a var/const instead of the fixed value we now use...
Shouldn't 1, 1 be enough then?
Shouldn't 1, 1 be enough here?
Why is this different in CanBuildSingleRailStation?
Why is this different in CanBuildSingleRailStation?
The connection start and finish tile need to be at the same height, needs to be checked too!
The connection start and finish tile need to be at the same height, needs to be checked too!
replace number by a definied constant or variable depending on date and other factors
check first if we are below max no. of trains...
if vehicle count = 0 because we didn't have enough money to buy trains then
we should (try to) add trains or wait until we have more money
Maybe add a status to routes like [nomoneyfortrains, unprofitable, ...]
Don't use platform length but compute optimal length for this group!
maybe do this for all trains in one go instead of per group probably more efficient
possible duplicate code with profit checking in air manager. Maybe combine in 1 function?
Do this on a per group basis (each route a group).
That way we can decide to not check a group wich was created less than x years ago.
When maintenance costs are on we should set low profit limit too at least the yearly costs.
When maintenance costs are on we should set low profit limit too at least the yearly costs.
Don't sell all trans from the same route all at once, try selling 1 per year?
Should we save this?
save building state! if (builder != null) { toremove.vehtype = builder.vehtype; toremove.stasrc = builder.stasrc; toremove.stadst = builder.stadst; toremove.list = [builder.ps1_entry[1], builder.ps2_entry[1]]; } else { AILog.Error("Invalid save state, probably the game is being saved right after loading"); table.buildingstage = BS_NOTHING; }
EventQueue, bridgesupgraded?, inauguration?, bs_building building stage