House Cleaning

Welcome back to the third month of House Cleaning!
Link to original thread here

House Cleaning is an ongoing event which will run month to month with the aim of staying on top tickets being raised for inactive developers, and to help maintain quality of our existing library of supported achievement sets.

But don't be fooled, this event is for both developers and players!

Each month developers and players will be able to earn up to 2 tokens with 12 being required for the event badge. The first token will be awarded upon completing 10 tasks, and the second for completing 25 tasks.
The monthly period will restart on the first Saturday of every month.

To take part in the event, submit your tasks with the template provided below within this thread. Some tips on submitting saves also listed below!

The following tasks will currently award 1 tasks with possible bounties upcoming which could award multiple!
Providing a save or state for an open ticket
Resolving a ticket

You can check general progression Here

Community goals
Community Goal 1: Resolve all tickets raised in 2021 (41 tickets in total!)
Community Goal 2: Resolve 100 tickets for the month
Community Goal 3: Resolve all tickets for 5 sets that currently have at least 5 tickets

When one of the above community goals are met we'll then award the Ticket-Buster role to those who contributed on the discord server.
Contribution criteria: Resolved at least 1 ticket from 2021 or obtained at least 10 points this month. For community goal 3, contribution will be providing a save or resolving a ticket for any of the cleared games. After the goal is met, if you clear all tickets for another set or provide full saves that will also count!

FAQ
Q: If an individual achievement has multiple tickets, will providing a save for it count towards each ticket?
A: Yes! And the same goes for developers who resolve multiple tickets for a single achievement as well!
Q: Will we need to complete the required tasks every month?
A: No, this will be an ongoing event and you can take break months. Any tiers which are incomplete will also carry credit over. If you complete 5 tasks one month, you'll then start with 5 tasks completed the following month. For the second tier you'll also carry this over, so if you complete 15 tasks one month, you'll carry over 5 towards the second tier, however to start working on that second tier again you'll need to complete 10 tasks again for the first tier, however you'll retain the 5 progress as a head start.
Q: Can I resolve a Jr. Developers tickets?
A: No, any tickets resolved for an active Jr. Developer will not count for the event. The Ticket Hounds team will happily assist any Jr. Developers will resolving their tickets with Code Reviewer approval however!
Q: Can I resolve ticket for an active developer?
A: Yes, however these would follow standard process AKA you can resolve tickets for any developer that has 10+ open tickets that are at least 2 months old. If any developer is struggling with resolving a ticket however, drop the team a message and we can assist!
Q: Can I collab on resolving tickets?
A: Credit will only be given to 1 developer resolving a ticket unless a collab is authorised prior.
Q: Can I resolve tickets that I've raised myself?
A: Yes, however you'll be limited to 1 task per set - Exceptions can be made depending on circumstances and will be approved on a case by case basis

Template for submissions
Tickets Resolved: 1 (number of tickets resolved)
Saves Provided: 1 save - 3 tickets (number of saves provided and how many tickets this is for)
Tickets: Ticket number using the ticket tag

Tips for submitting saves:
The most ideal solution would be submitting a battery save file rather than a save state, however depending on the game this may need to be a save state.
When naming the files and sending in a message to this account please use the below format
GameName-AchievementName-CoreUsed-VersionNumber
This way it's easier to identify which game and achievement the save is for, as well as which core was used and the version number, so that a developer can use the save more easily.
As long as we know which save is for which achievement though we can update this once received!
When submitting saves for a ticket please ensure these are created using the same emulator as the ticket as otherwise these may not be useful for resolving the ticket and will be subject to not being awarded credit.

New Tickets Resolved: 7
Total Tickets Resolved: 7
Ticket #57842
Ticket #58681
Ticket #56937
Ticket #56934
Ticket #56950
Ticket #56933
Ticket #56949

Provided a state for:

Ticket #59942

Provided a save and state for:

Ticket #58718

Provided a save for:

Ticket #48590

Provided a save and state for:

Ticket #58488

Provided states for:
Ticket #58246
Ticket #58247

Provided states for:

Ticket #55866
Ticket #56108

Provided save and state for:

Ticket #58580
Ticket #60111

New tickets resolved: 5
Total tickets resolved: 5

Ticket #56716
Ticket #56356
Ticket #56491
Ticket #60132
Ticket #60155

New Tickets Resolved: 4
Total Tickets Resolved: 11
Ticket #46941
Ticket #47232
Ticket #51265
Ticket #51266

New tickets resolved: 2
Total tickets resolved: 7

Ticket #55430
Ticket #59364

These 2 for now. Resolved today.

Ticket #59398
Ticket #60501

Oh, one of them is one month old and one is fresh. Don't count them if you don't want but it's still better then leave vulnerability open.

10 tickets
Ticket #59350
Ticket #59352
Ticket #55221
Ticket #55222
Ticket #55223
Ticket #55224
Ticket #55225
Ticket #59460
Ticket #59426
Ticket #47902

New tickets resolved: 1
Total tickets resolved: 8

Ticket #60432