Page 1 of 1

API - Threat Situatuation

PostPosted: Fri Oct 09, 2015 9:00 am
by JAYMC
Blizz has brought in the functions about the threat in patch 3.x.
Yeah its true, that you can math the threat out, but its just calculated and i think, its group/raid general, not mob-based calculated in KTM.

My idea now:
Is there any possible way to enhance the blizz api without client-patches?
I think on the way of an internal channel like addons do.

API - UnitDetailedThreatSituation (reference)


btw: there is a spoiler tag missing. ;)

Re: API - Threat Situatuation

PostPosted: Fri Oct 09, 2015 11:10 am
by Athene
100% possible but too many players to handle the API calls I think.

On my old TBC server we had a .debugthreat command that displayed in the chat our real threat on the target and we used this command to debug the whole threat mecanism thanks to Omen and Dtm, but it was heavy load sometimes and we were not 7K+ :(

Re: API - Threat Situatuation

PostPosted: Sat Oct 10, 2015 6:08 am
by zerf
Possible ofc, in fact, as Athene mentioned, mangos has such functionality built in for debugging. All you would need is to define new API and have a way to interact with it from client side + create addon that uses this API.

Unlikely to happen though, since there are many other things that need fixing :)

Re: API - Threat Situatuation

PostPosted: Sat Oct 10, 2015 7:14 am
by JAYMC
The old MaNGOS-svn is down. Has any1 an actually repo of it?

Re: API - Threat Situatuation

PostPosted: Sat Oct 10, 2015 7:58 am
by zerf
Why you need old mangos svn? cmangos.net ;)

Re: API - Threat Situatuation

PostPosted: Sat Oct 10, 2015 8:28 am
by JAYMC
I'm out of the scene since about 6-7 years ;)

Re: API - Threat Situatuation

PostPosted: Sat Oct 10, 2015 4:56 pm
by Stalk
This server is derived from Mangos Zero (not cmangos)

https://github.com/mangoszero

Re: API - Threat Situatuation

PostPosted: Sat Oct 10, 2015 6:39 pm
by zerf
CMangos is not a mangos version, but fork of original codebase (versions zero, one, and so on) due to drama that occured a while ago. Nobody commits to mangos repo anymore, cmangos is where it's at (regardless if you originally forked from mangos or cmangos).

Re: API - Threat Situatuation

PostPosted: Sun Oct 11, 2015 4:21 am
by Stalk
zerf wrote:CMangos is not a mangos version, but fork of original codebase (versions zero, one, and so on) due to drama that occured a while ago. Nobody commits to mangos repo anymore, cmangos is where it's at (regardless if you originally forked from mangos or cmangos).


I never said anything about versions. Mangos Zero was also not the original codebase from which CMangos was derived. They have separate development paths and separate issues with respect to bugs.

Re: API - Threat Situatuation

PostPosted: Sun Oct 11, 2015 5:38 am
by zerf
I know, but read that discussion. JAYMC was not aware people have moved to cmangos, his question has nothing to do with actual version this server is using (on top of that, it might have been changed so much that it wouldn't matter anyway).

Back to original discussion ... I see another problem with this, having correct threat meter is not "blizzlike" (which might be a problem, since it seems there won't be any character related services available that were not part of the game back then, for example race change).