• This is a read only backup of the old Emudevs forum. If you want to have anything removed, please message me on Discord: KittyKaev

Repost from Eluna TBC issue tracker: Player hooks and area trigger hook crashes mangosd.exe

Status
Not open for further replies.

efonius

Enthusiast
I've noticed some of the hooks causes the server to crash, this wasn't always the case, but I am unsure of which changes caused it. Here are some hooks I have tried it with and can confirm crashes mangosd.exe(on windows: freezes the mangosd.exe application, recieves mangosd.exe has stopped working). I don't have any crash logs currently, haven't compiled with debug in mind. However, this can be recreated on some of these hooks(probably other as well, but these are the ones I have tested):

server:
Code:
TRIGGER_EVENT_ON_TRIGGER (24)

player:
Code:
PLAYER_EVENT_ON_SPELL_CAST(5)
PLAYER_EVENT_ON_CHAT(18)
 

DarkAngel

Wiki Author
TBC issue tracker yet you're using mangos?
Last I checked below still worked on TC.
Code:
PLAYER_EVENT_ON_SPELL_CAST(5, function)
PLAYER_EVENT_ON_CHAT(18, function)

Regards, DarkAngel
 

Tommy

Founder
I've noticed some of the hooks causes the server to crash, this wasn't always the case, but I am unsure of which changes caused it. Here are some hooks I have tried it with and can confirm crashes mangosd.exe(on windows: freezes the mangosd.exe application, recieves mangosd.exe has stopped working). I don't have any crash logs currently, haven't compiled with debug in mind. However, this can be recreated on some of these hooks(probably other as well, but these are the ones I have tested):

server:
Code:
TRIGGER_EVENT_ON_TRIGGER (24)

player:
Code:
PLAYER_EVENT_ON_SPELL_CAST(5)
PLAYER_EVENT_ON_CHAT(18)

We'll look into it, thanks for the report.

TBC issue tracker yet you're using mangos?

What? Eluna MaNGOS ETBC Issue tracker. Thought he said TC?
 

Foereaper

Founder
I don't really understand why the thread was created when the issue was reported on the issue tracker..? Kinda redundant..
 

efonius

Enthusiast
I don't really understand why the thread was created when the issue was reported on the issue tracker..? Kinda redundant..

It was empty so I wasn't sure if developers were using issuetracker on repo, so I posted it here as well. The reason I pointed out that I reposted it from the repo was because I didn't want to create unnecessary confusion. I'm sorry for doubleposting it here, I know it's bad practice and would become very inconvenient if every issue were to be reported at both the repository and support forum, If you would like you could delete this thread. I just wasn't sure where to report it.
 

Foereaper

Founder
It was empty so I wasn't sure if developers were using issuetracker on repo, so I posted it here as well. The reason I pointed out that I reposted it from the repo was because I didn't want to create unnecessary confusion. I'm sorry for doubleposting it here, I know it's bad practice and would become very inconvenient if every issue were to be reported at both the repository and support forum, If you would like you could delete this thread. I just wasn't sure where to report it.

It's all okay hehe, we'll take a look at the issue and post back whenever we've checked it out :) But yeah, most core related issues should be posted on the issue tracker, this forum is mainly for setup support or script support :)
 
Status
Not open for further replies.
Top