I had made a severe mistake in an unpublished feature where you can decide an arbitrary lowest point value. When assigning the basic ground level the code would check if the override is set and use that or if there isn't one then just using the minimum ground level.
And then I had set a default value for the override.
Anyway, this should now be fixed and work again properly.