Guild icon
KQM | Genshin Impact
suc-n1-bug-misconceptions-and-workarounds
19 messages
Ticket Tool BOT Mar 16, 2022 8:14 PM
@BowTae - As an author, it is your responsibility to complete the ticket

Guidelines
- Name your ticket with $rename <ticket name>
- When you are ready to submit the ticket, compile everything into one message following the format below. Then type $close or click the button; the ticket will automatically be moved to be reviewed.
- The ticket will be scrapped if: No activity >1 week or open for >1 month.
Write-up Format
Theory/Finding/Bug: Title of your submission

Evidence: Explanations with calculations and/or Youtube/Imgur proofs

Significance: Conclusion
BowTae Mar 16, 2022 8:15 PM
Not sure if this is something that would go into the TCL, but I just felt like making it.

Sucrose N1 Bug Misconceptions and Workarounds

Finding:
Sucrose N1 bug is a real bug, however it is often misunderstood and sometimes incorrectly used as the reason for N1 not coming out.
There are ways to consistently avoid the bug and have it not be an issue.

What is the N1 bug?
Sucrose N1 will sometimes disappear. However, this only happens when continuing her normal attack string.

The original TCL entry:
https://library.keqingmains.com/evidence/characters/anemo/sucrose#sucroses-n1-attack-can-in-some-situations-cease-to-exist
The key point that is usually missed is "Attacking quickly with Sucrose". The bug happens when doing multiple presses. If you input N1 with a single click, you will not get this bug.

I've seen claims of N1 bug happening with just N1, but I haven't been able to reproduce this nor seen evidence. If someone has any evidence of it, please post it and I would be happy to be wrong.
(edited)
Sucrose
Evidence:
100 Sucrose N1s in a row, done with a single press each time, with the bug never happening.
https://youtu.be/rXClvuy1ihE
(edited)
BowTae2
100 Sucrose N1, no bug
10 Sucrose N1E in a row, with N1 coming out every time.
https://youtu.be/LT4ATEHs2yA
BowTae2
10 Sucrose N1E and a bunch of N1s, no bug
The N1 bug, to show that it exists and that my game isn't hacked.
https://imgur.com/Avfx7EG
Common situations:
1. I did Suc N1E and N1 didn't come out. https://imgur.com/HcR1LoM
- Two things could've happened here.
1. You pressed E too early after pressing N1, which canceled your N1 before it could come out. This is something that every character can do and is a normal game mechanic.
2. You mashed to do N1 and got the N1 bug.
2. I did Suc N1 only and the N1 didn't come out. https://imgur.com/RCJCEeE
- You dash/jump canceled too early, which is something that can happen to every character and is a normal game mechanic.
(edited)
Note: N1 can take longer to come out in a few situations, which may be the reason why you canceled too early
1. Doing a buffered N1 after dashing takes longer. This is not the original N1 bug, but is another separate annoying issue/bug. https://imgur.com/GYDRZtY
2. Your press for N1 was too long. For catalyst users, the N1 animation doesn't begin until you release your press, since holding puts you into CA windup animation. https://imgur.com/p9NmnHg
3. You mashed to do N1 and got the bug, then canceled N2 before it could come out.
(edited)
How to avoid the N1 bug:
1. I want to do Suc N1
- Click once to do N1, do not mash, and make sure you don't dash/jump cancel too early (or just don't cancel it)
2. I want to do Suc N1E
- Click once to do N1, then press E with enough delay for N1 to hit. Do not mash to do N1.
3. I want to do Suc N2+
- Click once to do N1, wait a tiny bit, then continue pressing to do N2 and up. This avoids the bug, but can make your attack string slightly slower without good timing. https://imgur.com/8tRwDlb
(edited)
Significance:
N1 bug is real and very annoying, however there are consistent ways to work around the issue.
TLDR: stop mashing
BowTae Mar 16, 2022 8:31 PM
will close this in 24 hours in case i made a mistake somewhere
NZPIEFACE Mar 16, 2022 8:41 PM
looks good to me
┌─── reply to message (953748792270782506)
Madrigal Mar 16, 2022 8:48 PM
but 🐒
Ticket Tool BOT Mar 17, 2022 9:08 PM
Ticket Closed by @549848745928556556
Support team ticket controls
Steno Mar 23, 2022 4:24 AM
"...another separate annoying issue/bug" I should bring that back
Anyways verified
CQLQRS Mar 26, 2022 11:47 PM
verified
Ticket Tool BOT Mar 29, 2022 10:51 PM
Transcript Saving