You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the webadmin pages "Latest claims" and "Latest changes", the images for the areas seem to have an off-by-one problem, usually exporting the whole 256-block-high area and a part of the sidewalk rather than just the changes.
The text was updated successfully, but these errors were encountered:
The root of the problem is that the plugin is trying to export too large an area as the image. Instead of exporting only the bounding-box of the changed voxels, it exports the entire gallery area, including the ~180 air blocks above any build and all the way down to the bedrock layer.
The original idea for the export coords is as follows:
If the area has a user-defined bounding box (as maintained in the shared DB by the GalExport plugin), use that.
If not, use the stored min and max coords of the edits (each block placement and removal should update these).
If not (for areas created before the edit-tracking code), calculate the diff of the area with the original area data (as set in the gallery's template schematic)
It seems part of this decision code is missing, and the third step has the off-by-one problem when diffing.
In the webadmin pages "Latest claims" and "Latest changes", the images for the areas seem to have an off-by-one problem, usually exporting the whole 256-block-high area and a part of the sidewalk rather than just the changes.
The text was updated successfully, but these errors were encountered: