Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ImageFrame Overwriting Existing Map IDs #77

Closed
Gazmanovich opened this issue Sep 22, 2024 · 4 comments
Closed

ImageFrame Overwriting Existing Map IDs #77

Gazmanovich opened this issue Sep 22, 2024 · 4 comments

Comments

@Gazmanovich
Copy link

Gazmanovich commented Sep 22, 2024

We use ImageFrame on server (Purpur, 1.20.1+), which alredy have some vanilla maps, like, old territories and etc. but, at some moment, ImageFrame's maps begin to replace vanilla maps iwith own image, even if you dont touch it at all! How it can be fixed or configured to not replace vanilla maps?

@HerrCraziDev
Copy link

I have a similar issue with ImageFrame replacing its own maps, recently created images reuse IDs that were attributed to older images !

image

This is also visible in ImageFrames/data/<image_id>/data.json, some of them reuse older map_id, just as if the map ID counter got rollbacked. Does ImageFrame has its own id counter, or is it based on the world's counter in level.dat/idcounts.dat ?

@LOOHP
Copy link
Owner

LOOHP commented Jan 16, 2025

It is based on the world's counter as IF uses the method from Bukkit. I guess the problem occurs when you reset your world?

@HerrCraziDev
Copy link

Oh ye, so perhaps restoring a backup caused the counter to revert backwards while new images were added ? Is there a way to manually skip the counter forward so new images don't override older ones ?

@LOOHP LOOHP changed the title ImageFrame's map replacing vanilla maps! ImageFrame Overwriting Existing Map IDs Jan 16, 2025
@LOOHP LOOHP closed this as completed in cdfc2b4 Jan 16, 2025
@LOOHP
Copy link
Owner

LOOHP commented Jan 16, 2025

Please give the latest build #116 a try and see whether the issue is fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants