[DiscordArchive] Well it should be prevented by the if condition?
[DiscordArchive] Well it should be prevented by the if condition?
Archived author: Vel • Posted: 2023-11-22T22:53:58.250000+00:00
Original source
Well it should be prevented by the if condition?
Archived author: Vel • Posted: 2023-11-22T22:54:47.724000+00:00
Original source
It behaves like even after the minion is unsummoned, it still somehow preserves it in the minionList and after second run, it executes UnSummon() even tho the minion doesn't exists and it crashes.
Archived author: Vel • Posted: 2023-11-22T22:54:58.574000+00:00
Original source
But this shouldn't happen.
Archived author: Vel • Posted: 2023-11-22T22:55:08.422000+00:00
Original source
I just need a way to prevent it but I have no ideas.
Archived author: Kris • Posted: 2023-11-22T23:00:36.639000+00:00
Original source
Depending on what checks you have in the unsummon function, if the minion isn't attached to a player even though it is supposed to be and you then try to detach it, that could be a problem. If I had no idea, I'd start checking if a summoned minion exists after every time you summon and unsummon.
Archived author: Vel • Posted: 2023-11-22T23:06:49.746000+00:00
Original source
UnSummon is TrinityCore default function
Archived author: Kris • Posted: 2023-11-22T23:33:19.038000+00:00
Original source
What sort of crash do you get in the logs? Or does it just return something it shouldn't? Haven't worked with summons so I'm a bit at a loss, sorry.
Archived author: Srzm • Posted: 2023-11-23T12:49:01.813000+00:00
Original source
Did you try debugging the issue? Knowing that this function causes the crash is huge to start debugging.