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

[Bug] Map art created and locked then wiped by server #1892

Open
GodzillaHawkMama opened this issue Nov 18, 2024 · 3 comments
Open

[Bug] Map art created and locked then wiped by server #1892

GodzillaHawkMama opened this issue Nov 18, 2024 · 3 comments
Labels
Issue type: Bug Something isn't working

Comments

@GodzillaHawkMama
Copy link

Server

Aurora

Describe the bug

[Bug] Map art created and locked then wiped by server

To Reproduce

[Bug] Map art created and locked then wiped by server

Expected behavior

[Bug] Map art created and locked should not be wiped by server

Screenshots

See comments in issue #1891 please

Additional context

No response

@GodzillaHawkMama GodzillaHawkMama added the Issue type: Bug Something isn't working label Nov 18, 2024
@Kuziemekk
Copy link

why make a duplicate of an issue that was already posted

@GodzillaHawkMama
Copy link
Author

GodzillaHawkMama commented Nov 19, 2024

why make a duplicate of an issue that was already posted

Several reasons made it logical to do so. 1. Troubleshooting

  1. It was commissioned work and carpets were still on art deck.

  2. Cause of issue is not known. Additional data could help resolve issue for others.

  3. Hoping to get repaired mapart to replace wiped map from mods or helper fruitloopins.

Ty for asking. Any other questions?

@jkmartindale
Copy link
Member

Several reasons made it logical to do so. 1. Troubleshooting

Making a duplicate issue offers no advantages for troubleshooting. You can just comment on the older issue, as you already did, and keep all relevant info in one place.

Making a duplicate issue adds the disadvantage of splitting relevant discussion into multiple threads, making it harder to track and troubleshoot. Well, in most cases. This specific issue doesn't even have any info worth reading, it's just "hey look at the comments on the older issue".

Cause of issue is not known. Additional data could help resolve issue for others.

What additional data?

Hoping to get repaired mapart to replace wiped map from mods or helper fruitloopins.

Make a ticket for anything you want looked at in a "timely" (relative) time frame. If you have loss due to a bug, it makes sense to both report the bug to get it added to the dev backlog and to make a ticket to get your specific loss remedied.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants