Help needed POI Update Issue

I was working on doing a new poi and was testing it for updates I had done. When this last save it has a n issue where the poi appears in the test scenario as a big round pit. It was working fine until this last save. I tried saving it again from creative mode, but it does not fix it. The last update I did was to add some blocks that have damage so that they can be destroyed in real play. I saved it checking the box to save damage states.
Any idea what could have gone wrong? I copied the updated POI edb file to the scenario folder. I see no errors in the log when starting/loading the scenario for the first time. Any thoughts?

 

Triple check the correct group names are set in the blueprint and on the playfield and that you did copy the correct file over to your scenario. Also of course that you're testing in survival and not using console commands to swap it to creative.

Also try spawning your blueprint in creative via the blueprint library to check to make sure you can actually spawn it correctly, as some blueprint errors won't show up until you try to spawn a fresh copy of it.

 

I am still having this issue. I spawned it fine in creative and resaved. Any other ideas?

 

I tried changing the ground offset which was -80, as it is 40 blocks deep, to -40, but that did nothing? Which brings up another thing how do custom scenarios know about the ground offset if it is not part of the epb file?

 

3rd question that I havent found any information on yet. Is the import/export of epb files that is supposed to be in this latest 1.17 release. Anyone know how to do it?

 

If it's not spawning then there is something wrong with either the blueprint itself, and/or the POI entry in the playfield file.
Half using the incorrect group name is what causes this issue, the other half is because you were swapping between creative and survival or moving save files from singleplayer to a dedicated server or something weird like that.

I couldn't tell you why it's not spawning for you unfortunately. If you can't figure it out I suggest trying to spawn a default POI instead and see if that works, or create a new test POI to test to narrow down the issue.