drt: attempt to handle waiting time explicitly when teleporting #3095
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Attempting to explicity handle waiting time when teleporting drt (e.g. when using drt-speedup) by delaying the
PassengerPickedUpEvent
accodingly. The remaining problem is thatTeleportingPassengerEngine
delegates to theDefaultTeleportationEngine
for throwing the arrival-related events likeTeleportationArrivalEvent
.DefaultTeleportationEngine
therefore callsagent.getExpectedTravelTime().seconds()
, i.e. looks up the estimated travel time in the pre-computed route (if available), which does not include the waiting time (and should not??). This then leads to the fact that theTeleportationArrivalEvent
is thrown without accounting for the waiting time. Is there any smooth way out without overridingDefaultTeleportationEngine.handleDeparture
@michalmac ??