-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Comments
why make a duplicate of an issue that was already posted |
Several reasons made it logical to do so. 1. Troubleshooting
Ty for asking. Any other questions? |
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".
What additional data?
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. |
Ok - so i'll try and delete this post |
taking advise of jkmartindale to reduce duplicate tickets on same issue. I didn't know making a ticket for a bug was different from making ticket in discord for refund until recently. I'm glad issue was fixed. Hopefully, i'll get copy of the mapart that was lost. Thanks for all you do! |
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
The text was updated successfully, but these errors were encountered: