Difference between revisions of "Development"

From FYM Wiki
Jump to navigation Jump to search
m
m (Progress)
 
(One intermediate revision by the same user not shown)
Line 2: Line 2:
  
 
== Features to add ==
 
== Features to add ==
 
"Cross-loading" logic (UP loading for BNSF destination that UP serves)
 
  
 
Shortline affiliations for cross-loading logic (UP loading for CN destination that IHB, a jointly owned belt railroad, serves)
 
Shortline affiliations for cross-loading logic (UP loading for CN destination that IHB, a jointly owned belt railroad, serves)
Line 11: Line 9:
 
Car pool logic, including pool logic that varies by car type and pool type
 
Car pool logic, including pool logic that varies by car type and pool type
  
Spacer cars, buffer cars
+
Make bad order cars always flashy red - can't see destination, etc.
  
Make bad order cars always flashy red - can't see destination, etc.
+
Change MIM should take into account cross-loading logic (probably by changing destination to the appropriate alternative, to avoid soft-locking cars)
  
 
== Work to do ==
 
== Work to do ==
 +
 +
Loads of documentation!
  
 
Car weighting data
 
Car weighting data
Line 24: Line 24:
  
 
Define car repair config that varies by cartype
 
Define car repair config that varies by cartype
 +
 +
Car marks database
  
 
== Bugs/issues ==
 
== Bugs/issues ==
  
All child IDs are considered to be 'virtual' IDs, which have slightly relaxed rules on LD logic.
+
All child IDs are considered to be 'virtual' IDs, though with very few effects. FYMYMRR holds the data to distinguish.

Latest revision as of 12:24, 30 August 2021

Notes on ongoing internal development.

Features to add

Shortline affiliations for cross-loading logic (UP loading for CN destination that IHB, a jointly owned belt railroad, serves)

Should car damage be auto-generated by distance but hidden until detected?

Car pool logic, including pool logic that varies by car type and pool type

Make bad order cars always flashy red - can't see destination, etc.

Change MIM should take into account cross-loading logic (probably by changing destination to the appropriate alternative, to avoid soft-locking cars)

Work to do

Loads of documentation!

Car weighting data

Add car shop data

Finalise car repair config (although we expect further iteration)

Define car repair config that varies by cartype

Car marks database

Bugs/issues

All child IDs are considered to be 'virtual' IDs, though with very few effects. FYMYMRR holds the data to distinguish.