summaryrefslogtreecommitdiff
path: root/src/rail.h
AgeCommit message (Collapse)Author
2012-01-03(svn r23735) -Codechange: remove ~50 includes from headers that weren't neededrubidium
2011-12-03(svn r23415) -Feature: Infrastructure maintenance costs.michi_cc
2011-11-07(svn r23129) -Add: [NewGRF] Property for the rail type name.michi_cc
2011-07-04(svn r22633) -Fix: Implement variables 25 and 7F for railtypes.frosch
2011-05-08(svn r22436) -Fix (r18969): Apply railtype property 12 (station graphics) ↵frosch
also to station groundsprites from action 1.
2011-01-27(svn r21919) -Fix: Converting an expensive rail type to a cheap one could ↵planetmaker
give more money than removing and rebuilding cost
2011-01-20(svn r21866) -Feature [FS#4394]: [NewGRF] Rail type property to influence ↵rubidium
sorting of rail types in the drop down list
2011-01-18(svn r21846) -Codechange: move documentation towards the code to make it ↵rubidium
more likely to be updated [o-s].
2011-01-18(svn r21842) -Feature [FS#4393]: [NewGRF] Introduction dates/required types ↵rubidium
for rail types; e.g. introduce a particular rail type in 1960 (or when a vehicle using it is introduced), but also allow limiting its introduction to only happen when the required railtypes are available
2011-01-18(svn r21841) -Feature: [NewGRF] Allow to define other railtypes that should ↵rubidium
be introduced if a particular rail type is introduced, e.g. to make sure slow rail is introduced when fast rail gets introduced
2010-08-01(svn r20286) -Codechange: Unify end of doxygen comments.frosch
2010-08-01(svn r20283) -Codechange: Unify start of doygen comments.frosch
2010-07-02(svn r20049) -Feature: [NewGRF] Add a railtype flag to disallow level ↵michi_cc
crossings per railtype.
2010-03-23(svn r19507) -Codechange: remove semicolon after DECLARE_POSTFIX_INCREMENT ↵smatz
and DECLARE_ENUM_AS_BIT_SET
2010-03-16(svn r19433) -Codechange: Limit rail clearance earnings to 3/4s of rail ↵peter1138
build cost, to avoid money making loophole when rail build cost is less than rail removal earnings.
2010-03-14(svn r19414) -Doc: Several doxygen additions and corrections.alberth
2010-03-14(svn r19413) -Codechange: Merging RailtypeFlag enum (a bit number) with ↵alberth
RailTypeFlags enum (had values only).
2010-03-07(svn r19365) -Codechange: Move EnsureNoTrainOnTrackProc() to src/vehicle.cpp.alberth
2010-03-03(svn r19307) -Add: Let railtypes specify their own smallmap colour. No ↵peter1138
legend support yet.
2010-03-03(svn r19306) -Change: Railtype cost factor from byte to word valuepeter1138
2010-02-07(svn r19056) -Add: [NewGRF] Action 3/2/1 (i.e. new graphics) support for ↵peter1138
rail types. (To be documented...)
2010-01-31(svn r18972) -Add: [NewGRF] Per-rail type speed limits.peter1138
2010-01-30(svn r18969) -Add: [NewGRF] NewGRF-settable rail type properties.peter1138
2010-01-15(svn r18809) -Codechange/Cleanup: remove unneeded headers from some files, ↵rubidium
if a header require a header make it include that header
2010-01-09(svn r18766) -Codechange: Make train acceleration type (rail/elrail/monorail ↵peter1138
vs maglev) a rail type property
2009-12-15(svn r18509) -Codechange (r2515,r2753): Data for drawing single_x/y rail ↵peter1138
pieces was inverted.
2009-11-09(svn r18028) -Codechange: unglobalise some functionsrubidium
2009-11-07(svn r18005) -Codechange: Convert the Prices struct into an array and an enum.frosch
2009-09-19(svn r17570) -Fix: a number of Doxygen warnings about missing parameters, ↵rubidium
which were sometimes missing and sometimes just typos
2009-08-21(svn r17248) -Fix: add GPL license notice where appropriaterubidium
2009-07-18(svn r16869) -Codechange: make drawing waypoints a tiny bit more like ↵rubidium
drawing stations
2009-06-24(svn r16643) -Codechange: replace GetStationByTile() by Station::GetByTile()smatz
2009-05-22(svn r16393) -Codechange: move VehicleRail to Train.rubidium
2009-02-08(svn r15417) -Codechange: Add default rail type labels and support for ↵peter1138
per-GRF translation table.
2009-01-13(svn r15050) -Codechange: Use one absolute SpriteID with offsets to draw ↵peter1138
track fences.
2008-10-07(svn r14448) -Codechange [FS#2328]: rename a few variables (based on a patch ↵smatz
by planetmaker)
2008-09-30(svn r14421) -Codechange: rename all player variables/types to company *or* ↵rubidium
client so it is immediatelly clear which one you are working with.
2008-08-24(svn r14162) -Fix: Allow rail type conversion if the rail type cost ↵peter1138
multipliers are the same.
2008-08-24(svn r14160) -Codechange: Move _railtype_cost_multipliers into the rail type ↵peter1138
information struct.
2008-08-24(svn r14158) -Codechange: Initialization of rail type data from static ↵peter1138
source, so data can be changed.
2008-08-24(svn r14157) -Codechange: Add and use string properties for rail types ↵peter1138
instead of relying on consecutive string IDs.
2008-08-01(svn r13912) -Codechange: remove some casts by returning the proper type ↵rubidium
instead of void*.
2008-06-11(svn r13469) -Codechange: add support for loading Action 0x05, type 0F: ↵rubidium
"tracks for slopes". It's not useful right now, but it will be in the future.
2008-05-08(svn r13016) -Codechange: unify the detection if rail catenary should be drawnsmatz
2008-05-06(svn r12971) -Documentation: add @file in files that missed them and add ↵rubidium
something more than whitespace as description of files that don't have a description.
2008-04-23(svn r12853) -Fix: catenary on tunnel entrances and middle bridge pieces was ↵smatz
drawn twice in some cases
2008-04-08(svn r12624) -Codechange: Make drawing of catenary an attribute of rail ↵peter1138
types, instead of deciding by the rail type directly.
2008-03-25(svn r12410) -Codechange: abstract out the test for catenary on electric railspeter1138
2008-03-19(svn r12386) -Fix [FS#1841](r2428): train could break apart when reversed ↵smatz
while partially in a depot
2008-01-09(svn r11802) -Fix [FS#716]: do not crash trains when leaving depot to a very ↵smatz
long track -Codechange: use dedicated pathfinder for signal updating, resulting in better performance and possible future improvements