-
Notifications
You must be signed in to change notification settings - Fork 254
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
Sin Spell - Massacre #84
Comments
Let's create a road map to fix spells and other known bugs in the main source code. |
Some additional information based on discord discussions: ...IF.. any of those massacred mobs die, the massacre trigger loops back to the start and applies the same, this means that mobs inflicted with a previous massacre can also be re-massacred, its a guaranteed infinite loop of death until all connect mobs are killed, but can be started by a single kill with no limitations. The damage amount also continues to grow through each iteration of the loop, if you have packed maps or huge lures, it's not uncommon to see damage values in the 100k-1mil range |
Does it make sense to make it only trigger when the player kills a mob through direct attack? |
I think it would be better scaled if there was a way to cap the total targets, or potentially only allow a mob to be massacred once in a chain. some sort of condition check to show a mob has already received a 'massacre' attack recently |
Sounds good too, I will work on this spell soon and test what solution could be the most optimized and balanced. |
Drasterically lowering the magic power of this skill seems to fix the main issue. It takes a percentage of the damage over the HP of monster you just killed, and passes that to the next monster ignoring their defences. So if a monster has 200 HP, you do 300 damage, 100 damage will be passed to the next monster. If you reduce the power of this skill to say 5% each level, then only 5 damage of that 100 would be passed to the next monster. Try that adjustment, and if it doesn't help comment again and I can take another look at a different approach. |
There's an issue with the base version of this code that can allow a player under certain circumstances to cascade the effects across a map doing increasingly more damage. During testing, we managed to almost do a full map wipe due to the way it can cascade onto additional targets.
I'm pretty sure it should have both an upper damage limit and a total cascading targets limit. either way, as it stands it can be (and apparently has always been) exploited.
The text was updated successfully, but these errors were encountered: