[2.0.13] on_player_driving_changed_state doesn't trigger when entering remote driving but it does on exit?

Things that has been reported already before.
Oarc
Fast Inserter
Fast Inserter
Posts: 122
Joined: Sun Sep 18, 2016 2:04 pm
Contact:

[2.0.13] on_player_driving_changed_state doesn't trigger when entering remote driving but it does on exit?

Post by Oarc »

I would expect to see on_player_driving_changed_state triggered for both entering and exiting remote driving, but I only see it for exiting it seems?
I tested with a spidertron and a train.

Not sure if I was doing something wrong maybe? Or I have an incorrect expectation?

Barebones scenario control.lua I used for just dumping the driving state:

Code: Select all

script.on_event(defines.events.on_player_driving_changed_state, function (event)
    log("Player driving changed state")
    log(serpent.block(event))
end)
I only see this print when exiting remote driving, not entering remote driving.
Oarc
Fast Inserter
Fast Inserter
Posts: 122
Joined: Sun Sep 18, 2016 2:04 pm
Contact:

Re: [2.0.13] on_player_driving_changed_state doesn't trigger when entering remote driving but it does on exit?

Post by Oarc »

Thanks! Sorry I didn't check for duplicates before posting.
Post Reply

Return to “Duplicates”