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
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.
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: