Summary: (a short description of the bug)
There appears to be a new XML element "PrefabSize" that is not present until you save the POI in the Prefab Editor. World Generation throws a DivideByZeroException when placing Wilderness POIs.
Game Version: A20 B231
OS/Version: Windows 11
CPU Model: Not relevant
System Memory: Not relevant
GPU Model and VRAM: Not relevant
Screen Resolution: Not relevant
Video Settings: Not relevant
Game mode: RWG
Did you wipe old saves? Yes
Did you start a new game? Yes
Did you validate your files? Yes
Are you using any mods? Yes - Custom POIs
EAC on or off? ON
There appears to be a new XML element "PrefabSize" that is not present until you save the POI in the Prefab Editor. World Generation throws a DivideByZeroException when placing Wilderness POIs. My guess is the code for non-Wilderness POIs still checks for the POI size in the old location if the XML element PrefabSize is not found. But, that the Wilderness placement code only tries to find the POI size in the XML file. And, since the element is new, our existing XML files for custom POIs does not contain the new element. Loading and Saving the custom POI does generate the new element, though I suspect y'all don't want bad XML to crash RWG.
Detailed steps to reproduce the bug:
1) Attempt to build a world using Wilderness POIs that do not have the PrefabSize element in the XML file.
2) If one of those POIs is selected for placement, you should see the DivideByZeroException.
3) Have a nice day.
Actual result: (description of what is occurring)
RWG throws an exception and then appears to the user to be stuck. You have to kill it with the Task Manager.
World Generation or a nice error message saying "Cannot find the PrefabSize element in <xml-file-name>." Listing the name of the file is important for folks who have lots of custom POIs. Imagine somebody with the CompoPack installed, for instance.
Rock on folks. Y'all are doing great.