Attempting to change the rate option in Max Rate Calculator crashes my game to the main menu and gives the following error:
"Error while running event OutpostPlanner::on_gui_click (ID 1)
OutpostPlanner/gui.lua:270: attempt to index local 'frame' (a nil value)"

Screenshot:
https://i.imgur.com/R5IZcJK.jpg

I am posting this on both mods as I am not sure which one should be fixed.

I would also like to let you know how amazing this mod is! I have been wanting something like this for a very long time as I hate setting up mining outpost even with regular blueprints. I finally broke (after 1k hours) and starting searching the other day and came across your mod. I've loved it ever since! This works exactly as I had hoped it would when it comes to quickly building mining excavators over fields of ore.

Thanks again!

My game also crashes to main menu just attempting to open the Outpost planner GUI. It gives a different error for this crash:

Error while running event OutpostPlanner::on_gui_click (ID 1)
OutpostPlanner/gui.lua:461: attempt to index field 'OutpostBuilderWindow' (a nil value)

I haven't been able to reproduce either of these, but in both cases it appears the settings window has been destroyed. OutpostPlanner doesn't destroy the settings window except to recreate it on configuration change.

Maybe it has been destroyed by another mod, or maybe I have just missed something.

v1.0.3 should handle this better, if you still get the crash please upload a save file and tell me exactly what you did to reproduce the problem.

Thanks :)

I am getting an error after updating. At first I thought it was a new mod I installed but I removed all my new mods and the problem is still there. When clicking UI for other mods I get an error:

[OutpostPlanner] Warn: GUI Checkbox Change element name 'button17' not recognized

Diff-ing the new/old version I see the following line:

l.debug("GUI click element name '" .. event.element.name .. "' not recognised.")

I don't think I changed anything special to show debug messages. Is there any way to disable this?

Yep you're right, v1.0.3 added logging which has exposed an old bug, there's an l.warn a few lines above that which is the culprit (debug logging is off by default).

You're safe to ignore the warning. I have a fix for this, I'll release v1.0.4 later today.

Edit: 1.0.4 released, should fix this warning. I'm not at home, so I haven't updated GitHub, or tested it as much as I would like. It is a very small change so it should be OK, let me know if there are still problems.