Hi.
From what I have read, one solution would be to create a new rule TimeStampManager, that will offer to select a subset of the route industries, stations, trackmarks, MCPathStops to be surveyed at run time by the rule, that will register for all these selected objects the trains that stops at and the game time where the event happens. The rule will include a run time monitor that will display the results with filtering option possible on trains or on path objects names.
for schweitzerdude, sorry but scripts executed in Trainz don’t have any access to the file system and cannot read or write in any .txt file. That has been a choice done initially by Auran then now by N3V for performance reason that is a constraint for all third party développer. That is why the rule needs to include its own display module.
If in the future, we want to expand the system so that other rules or driver commands can retrieve the already collected information, it will be still possible by adding some internal API so that other scripts can retrieve the information.
I have a few updates on EIT in progress to finish first, but I expect I should be able to start this new development end of August, so the new rule may be ready for first beta test about mid September ...
Regards.
Pierre.