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

Some pledge combo fixes #3934

Merged
merged 2 commits into from
Jan 6, 2024
Merged

Some pledge combo fixes #3934

merged 2 commits into from
Jan 6, 2024

Conversation

ghoulslash
Copy link
Collaborator

Minor pledge combo fixes

  • Sea Of Fire damage checks battler is alive
  • Reset pledgeMove field at end of turn in case a canceller stops the combo'ed move

@AlexOn1ine
Copy link
Collaborator

ghoul could you maybe look into issue #3589 for pledges? Skeli asked me to do an AI damage calc after the first pledge move has been chosen so that the second battler sees the increase in damage but i wasn't able to do it.

@ghoulslash
Copy link
Collaborator Author

ghoul could you maybe look into issue #3589 for pledges? Skeli asked me to do an AI damage calc after the first pledge move has been chosen so that the second battler sees the increase in damage but i wasn't able to do it.

I'm not great with AI logic but can look to see if CFRU has anything on it

@AlexOn1ine
Copy link
Collaborator

ghoul could you maybe look into issue #3589 for pledges? Skeli asked me to do an AI damage calc after the first pledge move has been chosen so that the second battler sees the increase in damage but i wasn't able to do it.

I'm not great with AI logic but can look to see if CFRU has anything on it

It has less to do with AI logic but more with the way damage calcs are done in the expansion (which is only a problem for pledges). Since the calcs are ran at the start of the turn the second battler will never see a corresponding pledge move as a 150BP if the first battler has chosen one.

Right now this is purely handled through AI logic (which tbh is enough for me) but it is probably better if the AI sees the correct damage? Though if there is no easy way for it without rewriting stuff I'm not sure how crucial it is. I'm 100% sure GF doesn't even handle it if they couldn't handle Dragon Rage lol

I would say I merge this PR and if you got something a new one can be opened, if not it's also fine.

@AlexOn1ine
Copy link
Collaborator

AlexOn1ine commented Jan 6, 2024

ghoul could you maybe look into issue #3589 for pledges? Skeli asked me to do an AI damage calc after the first pledge move has been chosen so that the second battler sees the increase in damage but i wasn't able to do it.

I'm not great with AI logic but can look to see if CFRU has anything on it

It has less to do with AI logic but more with the way damage calcs are done in the expansion (which is only a problem for pledges). Since the calcs are ran at the start of the turn the second battler will never see a corresponding pledge move as a 150BP if the first battler has chosen one.

Right now this is purely handled through AI logic (which tbh is enough for me) but it is probably better if the AI sees the correct damage? Though if there is no easy way for it without rewriting stuff I'm not sure how crucial it is. I'm 100% sure GF doesn't even handle it if they couldn't handle Dragon Rage lol

I would say I merge this PR and if you got something a new one can be opened, if not it's also fine.

I should mention that the during the actual damage everything is fine.

@AlexOn1ine AlexOn1ine merged commit 396f2c9 into rh-hideout:master Jan 6, 2024
1 check passed
@ghoulslash ghoulslash deleted the be/pledge branch October 20, 2024 22:45
@AsparagusEduardo AsparagusEduardo added category: move effect Pertains to move effects bugfix Bugfixes labels Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix Bugfixes category: move effect Pertains to move effects
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants