@@ -19,7 +19,7 @@ the last track from the position before Mopidy was shut down.
1919
2020If you simply want to restore Mopidy's state exactly as it were when you left,
2121you can set
22- `core/restore_state <https://docs.mopidy.com/en/latest/config/#confval-core-restore_state >`_.
22+ `core/restore_state <https://docs.mopidy.com/en/latest/config/#confval-core-restore_state >`_
2323to ``true ``. The default behaviour of this extension is to mimick this, but by
2424using this extension, you can modify the state. You can set the entries in the
2525tracklist, the tracklist options, the playback state (e.g. set it to
@@ -43,6 +43,10 @@ There are some similar extensions which might suit your requirements better:
4343- If this extension tries to play tracks from backends, that have not finished
4444 initialising, the playing might fail. For a discussion see this
4545 `topic <https://discourse.mopidy.com/t/restore-state-not-working-for-dlna-extension/4358 >`_.
46+ If that happens, the next available track from the tracklist is played. If
47+ there is no later track available, Mopidy-Autoplay will not play anything.
48+ (All those tracks which cannot be played, can be found in the logfile with a
49+ warning level.)
4650- If you set Mopidy's configuration option ``core/restore_state = true ``, this
4751 might interfere with Mopidy-Autoplay, so it is best to either set
4852 ``core/restore_state = false `` or delete this entry. (When I tested it,
0 commit comments