> ## Content Index
> Fetch the complete content index at: https://www.morganyte.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Seven Deadly Sins: Origin Removes Boss Battle Rankings After Lancelot Skill Bug
- URL: https://www.morganyte.com/seven-deadly-sins-origin-removes-boss-battle-rankings-after-lancelot-skill-bug/
- Published: 2026-10-14T00:41:14.000Z
- Updated: 2026-10-14T00:47:11.000Z
- Description: Netmarble has corrected a Lancelot skill bug affecting Knighthood Boss Battle rankings in The Seven Deadly Sins: Origin, with compensation announced for players.
- Author: Nova
- Tags: Gacha, Gaming, News

## Key Takeaways

- **A bug involving Lancelot's Gauntlets** caused the Anchor Shot effect to stack unintentionally.
- **Netmarble is removing affected Knighthood Boss Battle records** because the bug influenced competitive results.
- **Ranking rewards have been postponed,** with equal ranking rewards announced for eligible participants.
- **A second maintenance concluded at 09:10 UTC on October 13** after the initial record reset failed.

The Seven Deadly Sins: Origin is correcting competitive rankings after a bug involving Lancelot's Gauntlets allowed an unintended combat effect to stack during Knighthood Boss Battles.

Developer Netmarble addressed the issue in an October 13, 2026 maintenance announcement, confirming that affected battle records would be removed and ranking rewards postponed while the results were corrected.

To address the impact on participating players, Netmarble also announced plans to distribute equal ranking rewards to eligible Knighthood Boss Battle participants, rather than relying on the compromised standings.

A second maintenance period was required after an initial attempt to reset the affected records did not work as intended. That follow-up maintenance concluded at 09:10 UTC on October 13.

The issue highlights how a single skill interaction can affect competitive rankings, particularly when rewards are tied to recorded battle performance.

## What Caused the Lancelot Ranking Bug?

![](https://storage.ghost.io/c/eb/c3/ebc34dba-226d-448a-8bd7-25a7ee135adf/content/images/2026/10/image-37.png)

The problem involved the Anchor Shot effect applied by Lancelot's Gauntlets Special Attack.

According to Netmarble, the effect could stack across party members when it was not intended to do so. This allowed players to obtain Knighthood Boss Battle scores through an unintended interaction.

Lancelot had joined The Seven Deadly Sins: Origin on October 8 as part of the Version 2.2 update, which introduced the character with multiple weapon options.

Because Knighthood Boss Battle rankings depend on recorded performance, the skill interaction compromised the fairness of the leaderboard. Netmarble consequently decided to remove affected records rather than preserve the resulting standings.

## Who Qualifies for Compensation?

Netmarble outlined several forms of compensation, each with different eligibility conditions and claim deadlines.

## October 13 Compensation and Reward Deadlines

| Reward                             | Eligibility                                                                     | Claim Deadline           |
| ---------------------------------- | ------------------------------------------------------------------------------- | ------------------------ |
| 300 Star Fragments per maintenance | Maintenance compensation                                                        | Oct. 27, 14:59 UTC       |
| 50 Knighthood Coins                | Boss Battle participants from Oct. 5, 07:00 UTC until Oct. 13 maintenance       | Check in-game mail       |
| Equal ranking rewards              | Participating Star Guardians                                                    | Oct. 28, 14:59 UTC       |
| Up to 15 Knighthood Coins          | Eligible cumulative-score participants, accounting for rewards already received | Distributed sequentially |

Deadlines are in UTC. The official notices announce reward arrangements but do not establish that every delayed reward has already been delivered.

Players who participated in Knighthood Boss Battle between October 5 at 07:00 UTC and the October 13 maintenance qualify for the announced 50-Knighthood-Coin apology compensation.

The individual cumulative-score adjustment works differently. Netmarble will account for rewards already obtained and distribute any remaining eligible rewards, up to a total of 15 Knighthood Coins for that reward track. Players who already received the maximum will not receive additional coins from it.

The developer also listed 300 Star Fragments as compensation for each of the two maintenance periods. Players should check their in-game mail and observe the applicable claim deadlines.

## Why Was a Second Maintenance Necessary?

The original October 13 maintenance was scheduled from 05:00 to 07:00 UTC to correct the Lancelot interaction and adjust the affected leaderboard.

However, after maintenance ended, Knighthood Boss Battle attempts and individual cumulative-score rewards had not reset properly.

Netmarble consequently performed a second maintenance, beginning at 08:30 UTC and concluding at 09:10 UTC.

The developer confirmed that the game was available again afterward and that the additional maintenance addressed the failed reset. It also announced that individual cumulative-score rewards would be distributed sequentially.

## What Should Players Do Now?

Players who participated in the affected Knighthood Boss Battle period should check their in-game mailbox for maintenance compensation and any applicable Knighthood Coin rewards.

They should also review their Boss Battle attempts and cumulative-score rewards following the resets.

The most important deadlines are October 27 at 14:59 UTC for maintenance compensation and October 28 at 14:59 UTC for the delayed ranking rewards.

Although the two maintenance periods are complete, Netmarble's announcements do not confirm that every delayed ranking reward has already reached eligible players.

The incident has been addressed through a skill fix, leaderboard corrections, and a compensation plan intended to prevent bug-affected scores from determining competitive rewards.