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

make_timeline ignores empty-name combatants #18

Closed
wexxlee opened this issue Dec 25, 2023 · 1 comment · Fixed by #19
Closed

make_timeline ignores empty-name combatants #18

wexxlee opened this issue Dec 25, 2023 · 1 comment · Fixed by #19
Labels
bug Something isn't working

Comments

@wexxlee
Copy link
Collaborator

wexxlee commented Dec 25, 2023

Initial discussion in quisquous#5943.

make_timeline is ignoring abilities from combatants with empty names because ignoredCombatants includes an empty string ('') as a combatant to be ignored. Removing that element from the array fixes the issue. But I'm not sure whether that's something we should do, or if there's history on why we ignore empty-name combatants when making a timeline.

In the case of the Aloalo log (and I imagine most if not all cases where an ability is used by an empty-name combatant), the ability used also does not have a name, so make_timeline will only generate "--sync--" lines anyway. I think there's a couple options:

  1. Leave as-is. On the off-chance an empty-name combatant uses an ability that might be relevant for timelines or triggers, we'll let whoever is coding it figure out what's going on and manually add lines on the (remote) off-chance they are needed.
  2. Add empty-name-combatant timeline entries, but only if a named ability is used. Minor improvement to the above that could catch a future edge case where we'd want the timeline entry. Seems low-probability, but it's arguably better than the current state.
  3. Include abilities from empty-name combatants. This will eliminate the gap, but leaves more work for those creating timelines to identify and remove these syncs if not useful.

I think I lean toward option 2, but I don't feel very strongly about it. If no one else has an opinion, that's probably what I'll do.
(cc: @JLGarber )

@wexxlee wexxlee added the bug Something isn't working label Dec 25, 2023
@JLGarber
Copy link
Collaborator

Well, that has been there since the beginning. I don't think we need to worry too much about what was originally intended given that it's just sort of always been that way.

I think you're right that option 2 is a good compromise. There's the potential for future content that would be more understandable under option 3, but I think if there's a comment in-line explaining the rationale, that should be good enough. (Plus, there will be the PR linking to this issue for further explanation, so it should be simple enough for future timeline work to reference this.)

wexxlee added a commit that referenced this issue Dec 28, 2023
Closes #18.
(ref discussion in quisquous#5943).

Instead of ignoring all abilities used by combatants with an empty name
field, `make_timeilne` will now include entries in the timeline and the
timeline ability table if the empty-name combatant uses a named ability.
github-actions bot pushed a commit that referenced this issue Dec 28, 2023
…#19)

Closes #18.
(ref discussion in quisquous#5943).

Instead of ignoring all abilities used by combatants with an empty name
field, `make_timeilne` will now include entries in the timeline and the
timeline ability table if the empty-name combatant uses a named ability. 58e9a9a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants