Maybe instead of a fixed max we need to find the current max price for an airplane?
We need to revise depot orders: both should probably go to depot on same airport as the order before it!
But this will have implications in several other places that depend on the order of the orders.
We need to revise depot orders: both should probably go to depot on same airport as the order before it!
But this will have implications in several other places that depend on the order of the orders.
Should probably be moved somewhere elese (main.nut?)
Maybe only upgrade if we have enought money
CLOSED airports should not be checked once a month but as often as possible because we don't want them to be closed for a long time, loosing profits.
Maybe only upgrade if we have enought money
CLOSED airports should not be checked once a month but as often as possible because we don't want them to be closed for a long time, loosing profits.
Is this really useful. Does it matter what tile we build on in same town?
In early games with low maximum speeds we may need to adjust maximum and maybe even minimum distance to get a round trip within a year.
code from AdmiralAI Aircraftmanager suggests that airport_id may be same as airport_tile!
What to do if multiple airports have the same nearest town?
Add vehicles if there are airports available.
figure out what to do if there are more stations in orders...
If problems.Count() > 0 then randomly add them over the available routes. Since it's not that likely we will leave that for another time.
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?
Ideally we should include the tiles of the current airport in our search for a new spot!
Maybe add as an extra parameter an optional list (default null) with the tiles of the airport
Set acceptance to maybe 50 lower than acceptance of current airport? On the other hand it will already go for the highest acceptance spot, maybe do acceptance = 50?
Can we use RemoveAirport too or does that make it impossible to reuse station_id?
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...
Support more than 2 lanes.
Why is this different in CanBuildSingleRailStation?
Why is this different in CanBuildSingleRailStation?
part of these can be merged, to be done after we know it's working
generalize the different lanes so it will be easier to extend.
Can we determine bridge/tunnel costs in advance here (e.g. expensive bridge newgrf) Maybe also depend on railtype?
Maybe also valuate on price of the bridge and depend on the max speed we need maybe + a little extra for when we upgrade trains...
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