diff --git a/Handling-Tickets/index.html b/Handling-Tickets/index.html index edbae882..7defcf77 100644 --- a/Handling-Tickets/index.html +++ b/Handling-Tickets/index.html @@ -4644,14 +4644,19 @@

Claiming a TicketIf a Developer Becomes Active Againlink

Who handles tickets for achievements edited while the developer is Inactive?

-

If an inactive developer becomes active again, they are still responsible for their achievements that have been fixed by other developers. -* It is strongly recommended that the newly active dev review any tickets that were resolved during their inactivity period so they can understand the changes made to their achievements. -* If necessary, reach out to the developer who made the updates that resolved the tickets. -* If the newly active developer no longer wants to be the owner of the achievements, they can reach out to the Developer Compliance team to inquire about a reauthor of said achievements. - * Note that an accepted reauthor will be handled on a case-by-case basis, depending on the developers in question as well as the changes made to the achievements. This rule will be reevaluated if the implementation of a set or achievement maintainer is introduced.

+

If an inactive developer becomes active again, they are still responsible for their achievements that have been fixed by other developers.

+

Changeloglink

Last 10 changes on this page: