This repository has been archived by the owner on May 20, 2023. It is now read-only.
[Bug]: Number of summons is exceeding the maximum stablished. #380
Labels
Type: Bug
Inconsistencies or issues which will cause an issue or problem for users or implementors.
Comments
tiothiago
added
the
Type: Bug
I think this is not the solution, possibly the solution is to fix the other function and not create a new one. |
Merged
9 tasks
|
@tiothiago, you can test the pr #381? |
dudantas
added a commit
that referenced
this issue
Jan 26, 2022
Fix for the issue #380 and #389 - Variable "monster.summons" renamed to "monster.summon" - Improved the "registerMonsterType.summon" function. The "monster.maxSummons" was changed to be inside "monster.summon", thus facilitating development - Added new table "summons" inside of "monster.summon" - Added the "count" in the "monsterType:addSummon" function - Fixed somes summons with "Demon2" name to "Demon" - Removed "monster.summonCost", the correct is "monster.manaCost" - Fixed a bug in the "registerMonsterType.light" function - Fixed bug in the familiar behavior - Modified all monsters for new style of summons
ghost
mentioned this issue
3 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What happened?
General Murius, for exemple, has a maximum number of Minotaur Guards set as 2. Same thing for Minotaur Archers.
Yet, it happens to be that General Murius is summuning up to 4 Minotaur Guards or 4 Minotaur Archers, clearly a bug somewhere in monster.cpp
How to Reproduce?
Just summon General Murius.
Relevant log output
No response
Attach any relevant file
Version
12.x (Default)
What OS are you seeing the problem on?
Windows 10
Code of Conduct
The text was updated successfully, but these errors were encountered: