| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2019-11-10 | Cleanup: Removed SVN headers | S. D. Cloudt | |
| 2019-09-29 | Fix: Some typos found using codespell | JMcKiern | |
| 2019-07-06 | Fix f53817987: unsafe mix of type 'TileIndex' and type 'bool' | glx | |
| 2019-06-30 | Feature: Multi-tile docks and docking points. | peter1138 | |
| 2019-04-29 | Codechange: Remove OrderTypeByte | Charles Pigott | |
| 2019-04-10 | Codechange: Use null pointer literal instead of the NULL macro | Henry Wilson | |
| 2019-03-31 | Change: Remove ship max order distance. | peter1138 | |
| It is skipped when NPF is in use. It is trivial to work around by adding and removing dummy orders. It is mostly alleviated by the ship path cache in YAPF. | |||
| 2019-03-21 | Fix #7391, 9b99b95: Don't invalidate go to depot orders of non-aircraft when ↵ | Michael Lutz | |
| invalidating hangar orders that happen to share IDs. This was caused because hangars are referred to by station ID, which is not unique with respect to depot IDs. | |||
| 2019-03-04 | Fix: Runway too short for large aircraft message should not depend on plane ↵ | PeterN | |
| crashes setting. (#7325) | |||
| 2019-02-27 | Fix #6574: Remove go to hangar orders when rebuilding airport | Samu | |
| When replacing an airport with another, cancel current orders of type 'go to depot' from aircraft still heading to it if the rebuilt airport doesn't have a hangar (helicopter vs heliport), or if the airplane can't land on the rebuilt airport (airplane vs helistation). Removes 'go to hangar' orders from all aircraft when replacing an airport with hangar with another without hangar (heliport). | |||
| 2019-01-27 | Fix: Direct the aircraft to the correct location of the hangar when skipping ↵ | Samu | |
| to a go to hangar order When manually skipping to a 'go to hangar' order in the order list, while the aircraft is flying, direct the aircraft to the correct location of the hangar. | |||
| 2019-01-19 | Change: Add path cache for ships. | Peter Nelson | |
| 2019-01-14 | Codechange: Use const instead of magic number for ship order distance. Allow ↵ | Peter Nelson | |
| slightly further distance when following orders. | |||
| 2019-01-05 | Add: Conditional order for max. reliability (patch by Cirdan, #6360) (#7017) | Eddi-z | |
| 2018-10-31 | Doc: Lots and lots of doxymentation fixes | Charles Pigott | |
| 2017-08-13 | (svn r27893) -Codechange: Use fallthrough attribute. (LordAro) | frosch | |
| 2014-07-16 | (svn r26694) -Fix (r26547) [FS#6063]: When orders become invalid, reset the ↵ | frosch | |
| waiting time, but keep the travel time. | |||
| 2014-05-06 | (svn r26567) -Cleanup: Remove unused StringID offset in orders check | planetmaker | |
| 2014-05-06 | (svn r26566) -Add [FS#6009]: Give a warning when a plane's orders tell it to ↵ | planetmaker | |
| use a runway which is too short for it (3298) | |||
| 2014-05-01 | (svn r26547) -Codechange: Collect order travel and wait times independent of ↵ | fonsinchen | |
| timetables | |||
| 2014-05-01 | (svn r26546) -Codechange: Make order wait_time, travel_time and max_speed ↵ | fonsinchen | |
| private | |||
| 2014-04-23 | (svn r26482) -Codechange: add an include that allows us to undefine/redefine ↵ | rubidium | |
| "unsafe" functions to prevent them from being used, and thus having to care about certain aspects of their return values | |||
| 2014-02-19 | (svn r26357) -Fix [FS#5845]: Some order options do not combine with others. ↵ | frosch | |
| (3298) | |||
| 2014-01-19 | (svn r26267) -Fix [FS#5865]: Really fix the infinite recursion problem and ↵ | fonsinchen | |
| always consider all branches of conditional orders as possible next stopping stations. | |||
| 2014-01-16 | (svn r26263) -Fix [FS#5865]: Don't run into infinite recursion when getting ↵ | fonsinchen | |
| next stopping station | |||
| 2013-10-20 | (svn r25891) -Feature: Use smallstack to allow for multiple next hops when ↵ | fonsinchen | |
| loading and unloading. | |||
| 2013-08-20 | (svn r25736) -Codechange: move condition prediction out of ↵ | fonsinchen | |
| GetNextStoppingOrder so that we can access both branches in calling code | |||
| 2013-08-11 | (svn r25718) -Fix: return INVALID from GetNextStoppingStation if vehicle ↵ | fonsinchen | |
| would have to unload everything at this same station at the next stop | |||
| 2013-07-05 | (svn r25562) -Fix [FS#5633]: If the next order cannot be resolved, reset the ↵ | frosch | |
| current order property instead of leaving it in an intermediate state. | |||
| 2013-06-09 | (svn r25361) -Feature: distribute cargo according to plan given by linkgraph | fonsinchen | |
| 2013-05-19 | (svn r25259) -Codechange: track capacities and usage of links | rubidium | |
| 2013-02-24 | (svn r25041) -Remove [FS#3764-ish]: ordered refit with subtypes, since the ↵ | frosch | |
| cases where it worked were corner cases rather than the general case. | |||
| 2013-02-14 | (svn r24995) -Codechange: Add flags to vehicle service interval for custom & ↵ | rubidium | |
| ispercent (peter1138) | |||
| 2013-01-23 | (svn r24936) -Fix [FS#5446]: Don't allow order refit to be set for no-load ↵ | peter1138 | |
| orders. | |||
| 2013-01-08 | (svn r24900) -Fix [FS#5389]: Comments with typos (most fixes supplied by ↵ | planetmaker | |
| Eagle_rainbow) | |||
| 2012-12-20 | (svn r24833) -Codechange: Replace magic numbers for invalidating ↵ | michi_cc | |
| vehicle-related windows with an enum. | |||
| 2012-08-03 | (svn r24457) -Fix [FS#5264] (r23087): Changing auto-refit for a 'goto ↵ | michi_cc | |
| station' order was inadvertently modifying the full load state. | |||
| 2012-07-09 | (svn r24390) -Change [FS#5213]: Allow cloning of orders which are ↵ | frosch | |
| unreachable for the destination vehicle if they were already unreachable for the source vehicle. This makes cloning/autorenewing/autoreplacing behave more smooth during station reconstruction. | |||
| 2012-05-26 | (svn r24282) -Codechange: Add AddVehicleAdviceNewsItem function to ↵ | frosch | |
| preemptively deduplicate code. | |||
| 2012-04-01 | (svn r24086) -Fix [FS#5131] (r23504): Cloning orders of aircraft with ↵ | frosch | |
| limited range failed. | |||
| 2012-02-14 | (svn r23947) -Feature: Timetabled maximum travel speeds for non-flying vehicles. | michi_cc | |
| 2012-01-27 | (svn r23859) -Fix: Inserting conditional orders for ships checked the wrong ↵ | frosch | |
| orders wrt. maximum distance. | |||
| 2012-01-25 | (svn r23849) -Fix [FS#5008]: when the network is lagging, you try to copy a ↵ | rubidium | |
| vehicle's order but accidentally create a station order and then copy the vehicle's order (before the first command is executed) one could trigger an assertion from the pool. Simplify the ancient code and make it more fool proof, even though it could stop copying a vehicle's orders slightly earlier than it would now... but who has come near that limit and really needed that many orders? | |||
| 2012-01-03 | (svn r23740) -Codechange: remove some 300 unneeded includes from the .cpp files | rubidium | |
| 2011-12-13 | (svn r23511) -Fix [FS#4885] (r23504): Aircraft orders could not be shared ↵ | planetmaker | |
| anymore when they had no range property declared (Hirundo) | |||
| 2011-12-13 | (svn r23505) -Add: Indication in the order list if the next destination of ↵ | michi_cc | |
| an order is out of range. | |||
| 2011-12-13 | (svn r23504) -Feature: Aircraft range. | michi_cc | |
| 2011-12-09 | (svn r23464) -Fix [FS#4876]: clear the backed up orders of a removed station ↵ | rubidium | |
| as well, otherwise one could create orders to a station that was never in the original backupped orders. For example a road vehicle trying to go to a buoy. | |||
| 2011-11-12 | (svn r23199) -Fix [FS#4822]: oil rigs that "expired" did not get removed ↵ | rubidium | |
| from the station list | |||
| 2011-11-04 | (svn r23087) -Feature: Auto-refitting of vehicles during loading at a ↵ | michi_cc | |
| station when the vehicle allows it. | |||
 |
index : Erich/openttd | |
| Unnamed repository; edit this file 'description' to name the repository. |
| summaryrefslogtreecommitdiff |