| Age | Commit message (Collapse) | Author |
|---|
|
loading and unloading.
|
|
GetNextStoppingOrder so that we can access both branches in calling code
|
|
|
|
|
|
cases where it worked were corner cases rather than the general case.
|
|
|
|
|
|
an order is out of range.
|
|
|
|
from the station list
|
|
station when the vehicle allows it.
|
|
as no real order influencing path finding is added
|
|
more likely to be updated [o-s].
|
|
with only automatic orders
|
|
for intermediate stations and remove them when not visiting them anymore. This allows you to see what trains visit a station without actually having to order a vehicle to stop at all stations. Based on patch by fonsinchen
|
|
vehicle's order list from the validation of those (user) commands. Based on patch by fonsinchen
|
|
|
|
|
|
|
|
|
|
document some related variables/functions
|
|
|
|
which were sometimes missing and sometimes just typos
|
|
|
|
favour of their Station variants
|
|
wrong results due to OpenTTD codechanges
|
|
|
|
time, binary size and run time (with asserts disabled) should be improved
|
|
variable instead of var->index
|
|
In the first phase, indexes are stored. In the second phase, indexes are checked for validity and converted to pointers
|
|
|
|
PoolItem::IsValidID(index)
|
|
PoolItem::GetPoolSize()
|
|
|
|
-Fix: 'Go non-stop to nearest depot'-orders did not work wrt. the 'non-stop' part.
-Fix: Adding 'Go to nearest depot'-orders did not respect the default setting for 'non-stop'.
|
|
end, middle or far end of a platform from the point of view of the driver of the train that enters the station.
|
|
|
|
|
|
remove the order count from the savegame as we can easily count that (PhilSophus)
|
|
together (the vehicle didn't stop).
|
|
something more than whitespace as description of files that don't have a description.
|
|
|
|
instead of two. The "TTDP compatible order" setting now only sets the default behaviour of new trains.
-Feature: allow three different load type in a single game instead of two. One can choose full load all and full load any instead of full load being governed by the "full load any" patch setting.
|
|
load and full load any based on the patch setting instead of using the patch setting directly.
|
|
|
|
|
|
|
|
it more clear that they are no loading/unloading flags. Also add more type strictness.
|
|
not is there a non-stop order but the kind of non-stop order, so one doesn't need to check _patches.new_nonstop type everywhere.
|
|
|
