When setting up waypoints.

The mod Spidertron Patrols (2.5.2) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event SpidertronPatrols::on_player_used_spidertron_remote (ID 179)
SpidertronPatrols/scripts/waypoint-rendering.lua:91: attempt to index local 'next_waypoint' (a nil value)
stack traceback:
SpidertronPatrols/scripts/waypoint-rendering.lua:91: in function 'create_render_paths'
SpidertronPatrols/scripts/waypoint-rendering.lua:184: in function 'update_player_render_paths'
SpidertronPatrols/scripts/waypoint-rendering.lua:219: in function 'update_spidertron_render_paths'
SpidertronPatrols/scripts/waypoint-rendering.lua:259: in function 'update_render_text'
SpidertronPatrols/scripts/spidertron-control.lua:49: in function 'on_patrol_command_issued'
SpidertronPatrols/scripts/patrol-remote.lua:48: in function 'handler'
core/lualib/event_handler.lua:47: in function <core/lualib/event_handler.lua:45>

Thanks for reporting this crash. I don't suppose you are able to reproduce this crash? Or expand on how often it occurs, what you were doing specifically at the time? Were you setting up waypoints for a regular spidertron, spiderling, or something from Lex's Aircraft?
Did you ever use "Shift click" with the patrol remote (which replaces the previous waypoint rather than adding a new one)?
Did you ever use the "Insert new waypoints mid-schedule" buttons (https://media.discordapp.net/attachments/1002362105049120880/1305909537466749008/Screenshot_2024-11-12_at_14.57.43.png?ex=6734be88&is=67336d08&hm=02d7750fa427f9a7a5c2174e21e742af6efc27de190b1ff097ef674b52f60298&=&format=webp&quality=lossless&width=1224&height=826) or were you always adding to the end of the waypoint list?

I'm afraid I can't recall anything more specific other that I was setting up waypoints on remote view while inside the Spiderling. I will be sure to update this thread on any other occurrences.
Epic mod.
Cheers!

Let me know if the inactivity condition works on your end, I have not been able to get it to work. The spiderling just keeps waiting long after the set inactivity time when no more loading or unloading via inserters from the dock occurs when the spiderling is docked.

Yep inactivity is broken. I've just fixed it, will probably release tonight.

I've added some code that will print a warning with some more logging, rather than crashing (although I suspect if it gets to that state, it would crash before long regardless).

I will keep a watch on it.

Thank you!