Hello, this is Project Moon.
We would like to inform you of additional issues that will be fixed in the Scheduled Update on Nov. 12th (Thu) at 12:00 (KST).
Please refer below for details.
< Additional Issues To Be Fixed in the Scheduled Update >
▶ Fixed an issue where a certain Identity was not counted toward a "Mirror Projection / Achievements - Teams (Loadout)" achievement
→ Relevant Achievement: Clear Mirror Dungeon at Floor 5 or higher with 6 or more Office or Workshop Identities in your Loadout at the time of completion (Incompletable by Rental Teams)
- Before: "Jeong's Office Rep Ishmael" was not counted toward this achievement
- After: "Jeong's Office Rep Ishmael" will be counted toward this achievement
▶ Fixed an issue where EXP awarded after combat was distributed differently than intended when "Gregor's Support Identity" was assigned
- Before: Gregor's Support Identity was included in EXP distribution. If deployed in combat, it also received additional combat participation EXP.
- After: As with other Support Identities, no EXP will be distributed to Gregor's Identity while his Support Identity is assigned.
[Design Intent]
EXP earned from a Combat Encounter is distributed among the Sinners. Sinners assigned as Deployed Identities and Backup Identities receive slightly more EXP than those not assigned.
A Support Identity is not intended to receive EXP. Instead, the other 11 Sinners share the EXP.
[Identified Issue]
When Gregor's Support Identity was assigned, Gregor was still included in EXP distribution, so the EXP was shared among all 12 Sinners.
We also found that when Gregor's Support Identity was deployed in combat (as either a combat participant or a Backup Unit), the Gregor Identity equipped before the Support Identity was assigned received additional combat participation EXP, separate from the EXP awarded to the other Sinners.
[Examples of the Issue]
※ The following examples assume a total of 600 EXP earned from a battle with 6 participants. The other 6 Sinners are not deployed as either combat participant or Backup Unit. Decimal values are rounded down.
(1) No Support Identity used
6 combat participants = 59 EXP each
6 non-deployed Sinners = 41 EXP each
(2) Another Sinner's Support Identity assigned and deployed
5 combat participants = 66 EXP each
6 non-deployed Sinners = 45 EXP each
Support Identity = 0 EXP
(3) Gregor's Support Identity assigned but not selected to be either a participant or a Backup Unit
6 combat participants = 59 EXP each
5 non-deployed Sinners = 41 EXP each
Gregor's Identity = 41 EXP
(4) Gregor's Support Identity assigned and deployed
5 combat participants = 61 EXP each
6 non-deployed Sinners = 42 EXP each
Gregor's Identity = 61 EXP
In examples (3) and (4), the EXP awarded to Gregor went to the Manager's Gregor Identity that had been equipped before his Support Identity was assigned. If that Identity was at the maximum level, EXP Tickets were awarded instead.
We also confirmed an issue where assigning Gregor's Support Identity and deploying it as either a Backup Unit or combat participant caused a greater amount of EXP than normal to be awarded.
[Fix]
After the Nov. 12th update, assigning Gregor's Support Identity will no longer award EXP to Gregor's Identity. As with other Support Identities, the remaining Sinners will share the EXP.
[Examples After the Fix]
※ The following examples assume a total of 600 EXP earned from a battle with 6 participants. The other 6 Sinners are not deployed as either combat participants or Backup Units. Decimal values are rounded down.
(1) No Support Identity used
6 combat participants = 59 EXP each
6 non-deployed Sinners = 41 EXP each
(2) Support Identity used, including Gregor's
5 combat participants = 66 EXP each
6 non-deployed Sinners = 45 EXP each
Support Identity = 0 EXP
EXP and EXP Tickets obtained through this issue before the update will not be withdrawn from the Manager's account. Please note that the EXP currencies that have already been given will remain in the account.
We apologize for the confusion caused by identifying this issue so long after the feature was introduced. We will take greater care to prevent similar issues in the future.