-
-
Notifications
You must be signed in to change notification settings - Fork 669
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
feat: fear condition #542
feat: fear condition #542
Conversation
Your pull request looks great, I approved the execution of the checks. I'll take a closer look later, but from what I've seen, everything seems ok. |
SonarCloud Quality Gate failed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, excellent PR!
Tested here, feared condition working fine restricting for party members, but still have some issues/restrictions for the condition itself, i'll point here:
- Fear condition when activated, should remain for 6 seconds;
- After being feared, when the condition finishes, you should have 10 seconds "cooldown" until you can get feared again;
- When feared, you should not be able to use any spell, nor equip amulets/rings (at the pr sometimes you can use spell, and can equip items anytime)
I'll add the pull as a draft until the author decides to analyse it and, if necessary, fix the problems. |
Sorry for the delay, I have been stuck on some work-related topics. I will try to work on it this week! |
@dudantas @guispiller Could you test again? For other contributors looking to test, just add the following attack to a monster {name ="fear", interval = 2000, chance = 100, range=7, effect=CONST_ME_MAGIC_RED, target=true} |
…llCheck function. Akk recommended this function to ensure no spell can be casted.
Tested! Functional! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking great, just a few suggestions
Severity Code Description Project File Line Suppression State when try build :/ |
you must be using some mixture of prs or something, because the compilation checks are passing normally |
maybe version? 13.11 |
character dont walk after feared, just stuck! but conditions of heal, time, etc still working correctly |
You need to test on the pull request branch only. The error you have is not related to the pull request itself, but its implementation. |
I merged 3 branches.. this (fear_condition), test (client 13.11), and missing_bosses, it works! |
This PR is stale because it has been open 45 days with no activity. |
Do you consider that the system is ok to be merged? Now we no longer have the changes to int64_t, which should make it easier for the system to implement. |
how add fear condition in attack of monsters? |
nevermind |
Please, test again with my last commit. 11892d6 |
SonarCloud Quality Gate failed. |
The Fear Condition is a status condition that makes the affected creature lose control of their movements for a short period of time. During this period, the affected creature randomly moves around in various directions, unable to perform any other actions. This condition is usually brought about by certain spells or monster effects.
The Fear Condition is a status condition that makes the affected creature lose control of their movements for a short period of time. During this period, the affected creature randomly moves around in various directions, unable to perform any other actions. This condition is usually brought about by certain spells or monster effects.
The Fear Condition is a status condition that makes the affected creature lose control of their movements for a short period of time. During this period, the affected creature randomly moves around in various directions, unable to perform any other actions. This condition is usually brought about by certain spells or monster effects.
Description
Implement fear condition.
Type of change
Checklist