Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ningguang frame adjustment #687

Merged
merged 14 commits into from
Aug 17, 2022
Merged

Ningguang frame adjustment #687

merged 14 commits into from
Aug 17, 2022

Conversation

skippi
Copy link
Collaborator

@skippi skippi commented Aug 10, 2022

Frame adjustment for #209 .

skippi added 7 commits August 9, 2022 23:43
Useful for intentionally destroying the construct.
Also added handler for choosing the next attack type according to RNG.
We still have some work to do with checking her idle -> CA frames, or
even her repeat CA frames. But this will work for 90% of her configs.
Also refactored out usage of Tags where possible.
@skippi skippi marked this pull request as draft August 10, 2022 08:19
skippi added 2 commits August 10, 2022 03:21
It still won't work since the parser is incorrect, but now the
conditionals are in correct format.
Adding these for people who want to check if parts of the burst miss.
skippi added 4 commits August 12, 2022 17:40
Particle ICD shorten name and fix conditional matching.
Ningguang's burst shards snapshot as soon as the burst activates. The
shards that come from the screen have a separate snapshot mechanic.
Ningguang only uses two of her charge attacks if she follows her NA with
a CA. It follows as below:

- Left/Twirl NA -> Left CA
- Right NA -> Right CA

The twirl CA is only used when CA is casted standalone. CAs outside of
the NA pattern are chosen by random.
@skippi skippi marked this pull request as ready for review August 13, 2022 01:10
From what Koli and I perceive, Ningguang has a state machine-like
pattern for her idle CAs. These are based on the previous normal attack.
@srliao srliao merged commit c034382 into genshinsim:main Aug 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants