What does the latest Knighthood ranking notice confirm?
October 13 Temporary Maintenance & Knighthood Boss Battle Ranking Notice was followed by Additional Temporary Maintenance. The original notice was modified on October 12 at 09:32:36 UTC; the follow-up was modified on October 13 at 09:12:39 UTC. Netmarble says the first issue came from Lancelot’s Gauntlets Special Attack, whose Anchor Shot effect could stack across party members.
The first notice scheduled October 13, 05:00–07:00 UTC maintenance. The follow-up added 08:30–09:10 UTC maintenance because attempts and individual cumulative-score rewards did not reset after the first maintenance. Affected records are removed from the current leaderboard, ranking-reward distribution is postponed, and all participants receive the same ranking rewards when they are distributed.
- Maintenance compensation: Star Fragment ×300, claimable after maintenance until October 27 at 14:59 UTC.
- Apology compensation: Knighthood Coins ×50 for players who participated from October 5 at 07:00 UTC through the temporary maintenance; ranking rewards can be claimed until October 28 at 14:59 UTC.
- Individual Cumulative Score: eligible players can receive up to 15 Knighthood Coins in total after the reset recalculation; players already at the maximum during the stated period receive no extra amount.
Article 339 was the initial investigation. Article 340 confirms the cause and ranking remedy; article 341 records the additional reset and sequential reward distribution. Keep the mailbox and in-game reward state as the final check before counting coins as available.
- Read the current notice before planning around rank rewards. Keep the delayed payout out of your spending budget until it appears in the mailbox.
- Keep an ordinary record of participation. Save the server, character, Knighthood, attempt time, score/result screen, and remaining attempts if you need to report a discrepancy. A screenshot records what you saw; it does not guarantee a final ranking or payout.
- Use the official support route for a problem. Describe your own result and expected reward. The notice does not identify a method to reproduce or diagnose, so do not infer one from a score alone.
- Check the maintenance follow-up. Review the record removal, reward scope, eligibility dates, and claim method before changing your group schedule or coin budget.
Is this the Timespace Season 5 compensation notice?
No. Notice 324, Regarding Leaderboard Regular Season 5 Issues, concerns unintended hero use in Timespace Junction. It specifies Season 5 final-ranking reward changes, participation compensation, an October 28 at 14:59 UTC mailbox deadline, and Leaderboard reward changes from Regular Season 6 onward.
Knighthood notices 339, 340, and 341 are separate from the Timespace notice. Articles 340 and 341 announce their own Knighthood compensation and mailbox windows; do not apply the Timespace compensation amounts or eligibility to Knighthood participation. If you also played Timespace, check notice 324 and its mailbox rewards separately.
Boss Battle introduction rules: July 22 snapshot
The following is the historical introduction snapshot from the official Version 1.7 Update Details, updated July 22. It explains the system and what to check in-game; it is not a new decision on the October ranking issue. Confirm the current entry counter, timers, and reward availability before playing.
- Entry and parties
- Knighthood members entered through NPC Haro in the East District of Liones. Parties contained one to five members of the same Knighthood; the leader sent the entry request and all members accepted.
- Attempts and normal reset
- Up to three challenge attempts per week, resetting Monday at 07:00 UTC (15:00 in Shanghai, UTC+8). Individual cumulative rewards and participation rewards also reset weekly under the introduction rules.
- First join versus rejoining
- The first Knighthood joined after the feature opened allowed immediate Boss Battle participation. Leaving and rejoining meant waiting until the next weekly reset. Leaving did not remove the old Knighthood’s recorded score, but departed members could not claim its ranking rewards.
- Score and best record
- Party scores applied equally to all party members. Each member’s ranking used their best score across up to three attempts. The Knighthood’s representative record used its highest individual score, not the sum of every member’s best run.
- Cumulative and participation rewards
- Individual cumulative score milestones had claimable rewards; these were distinct from the personal best used for rankings. Participation rewards depended on overall Knighthood member participation. Check both reward tracks rather than inspect only the leaderboard.
- Combat Class versus Boss Battle ranking
- Combat Class used registered teams. The introduction notice assigned ranking rewards only to the Knighthood Boss Battle’s Knighthood ranking, not to every ranking or member list.
What should members do before and after a weekly session?
- Before joining or changing Knighthood: check the current entry eligibility and whether leaving would affect your next Boss Battle session or reward claim. Arrange a group time before making the change.
- Before entering: check your remaining attempts, the current boss information, equipped weapon/preset, and the group’s shared availability. Confirm everyone is in the same Knighthood and has accepted the entry request.
- After each attempt: record the result and attempts remaining. Inspect your best record and cumulative-score progress separately. Claim any milestones shown as available, then check the participation reward screen.
- Before the mode’s displayed reset: check unused attempts, unclaimed available rewards, and the next group appointment. The July snapshot supplies a normal weekly schedule; a new official issue notice may separately affect ranking handling.
- When a ranking follow-up appears: check whether it changes records, reward distribution, eligibility, or claim deadlines. Update your notes from that announcement instead of importing rules from another mode.
Coordinate this with the daily and weekly account checklist. Raid uses its own key and Weekly Reward system, covered in the Raid rewards guide; Boss Battle attempts are not Raid Weekly Reward claims.
How should I spend Knighthood Coins?
Use the coins actually credited to your account. The introduction shop listed weapon skins, Deathwraith Shard outfit pieces, SSR Magic Crystal Shards, Platinum Ingots, Element Spell Bead Selection Chests, Large Cube Key Bundles, and Weapon Tier Up Material Selection Bundles. The original notice directs players to check prices and purchase limits in-game.
Write down one needed material, its displayed coin cost, and your balance after purchase. Compare a current upgrade bottleneck with a cosmetic you want before confirming. Do not buy around an assumed future ranking payout while the October issue awaits a separate decision.
Knighthood questions
Should I count an expected compensation payment as income?
Only count the Star Fragments or Knighthood Coins after the notice’s eligibility applies and the reward is visible or credited. Delayed ranking rewards are not spendable before delivery.
Do three attempts mean three ranking scores are added together?
In the July introduction rules, the ranking uses your highest attempt score; individual cumulative milestones are a separate reward track.
Is a ranking reset already confirmed?
Article 340 confirms the scheduled October 12 attempt reset plus an additional reset during the October 13 maintenance. Article 341 records a further reset after the first maintenance failed to reset attempts and individual cumulative-score rewards. It also confirms removal of affected records; it does not say that every record is reset or that every score is invalid.
Official article 340 · Official article 341 · Initial ranking-issue notice · Official July introduction rules · October 13 maintenance summary · Systems hub