Quantcast
Download
(178 Kb)
Download
Updated: 08/12/18 05:35 PM
Pictures
File Info
Compatibility:
Wolfhunter (4.1)
Summerset (4.0)
Updated:08/12/18 05:35 PM
Created:01/15/17 04:53 PM
Monthly downloads:839
Total downloads:27,166
Favorites:15
MD5:
Categories:Combat Mods, Group, Guild & Friends
4.1
Group Damage Share  Popular! (More than 5000 hits)
Version: 0.2.12
by: decay2 [More]
Description

Please note that the addon is still in beta so don't use it in important raids or other critical situations.
Especially note that this addon will cause issues with the DPS sharing option of FTC.


Group Damage Share is an attempt to provide a feature that was unique to FTC. It uses sirinsidiator's library LibGroupSocket.

It uses pings on the map to comunicate with the addon from another player to transmit your current DPS or HPS values. (for more details on this refer to the description of LibGroupSocket). With Group Damage Share you can watch during the fight how the DPS/HPS of your groupmembers develops.

Please note that this addon cannot show the DPS of group members who don't use this addon and enable sharing.
Setup + Installation:
  • Download and install the addon
  • Create a group
  • Go to the group window and click on "LibGroupSocket sending" so that it says "On"
  • For now settings are spread to two places (in the usual addon settings area): "Group Damage Share" and "LibGroupSocket"
  • If you want to turn sending on permanently you need to install LibGroupSocket as a standalone version. Refer to the description for more details.

Current features
  • Share your DPS or HPS as well as the combat time with your group
  • View DPS/HPS and combat time shared by your group (you don't have to enable sharing on to see the values shared by others)
  • The Icon on the left shows the class and its color the main resource (Magicka/Stamina) of the players
============================================

Planned Features:
  • Show both DPS/HPS in the window at the same time
  • Transmit DPS/HPS alternating so both data is available
  • Implement a standalone DPS meter so it doesn't rely on other DPS addons anymore

Big thanks to sirinsidiator's for creating the library for the data transfer:LibGroupSocket.

Decay2 aka Solinur (Pact EU)
Version 0.2.12
  • API Bump to Wolfhunter (100024)
  • Updated LibGPS

Version 0.2.11
  • skipped

Version 0.2.10
  • Updated libraries. This should allow to use this addon alongside other addons that share information via pings without getting kicked. Some pings will not be send however and it is theoretically possible that pings from an addon won't be sent at all (if another addon is hogging the maximum amount of pings possible).
  • Fixed sending of HPS

Version 0.2.9
  • Try to fix an incompatibility introduced by RaidTools

Version 0.2.8
  • Added brazilian portugese translatiuon by mlsevero. Big thanks!

Version 0.2.7
  • API Bump to Summerset (100023)
  • Update LAM to r26

Version 0.2.6
  • updated internal libraries (used already by Combat Metrics)

Version 0.2.5
  • Fixed an issue where the background transparancy was not recovered correctly after login/reloadui.

Version 0.2.4
  • API Bump to Clockwork City (100021)
  • Updated LibAddonMenu to version 2.0 r25 to fix an issue

Version 0.2.3
  • API Bump to Horns of the Reach (100020)
  • Fixed some leaked global variables.

Version 0.2.2
  • Fixed an issue where wardens were shown with the templar icon.
  • Lib updated

B]Version 0.2.1[/b]
  • Fixed an issue with the shown combat time.

Version 0.2.0
  • This version is now standalone. If used together with Combat Metrics fight tracking resources will be shared.
  • Removed obsolete settings.

Version 0.1.10
  • Reupload with correct manifest file (with correct version number)

Version 0.1.9
  • API Bump to Morrowind (100019)
Optional Files (0)


Archived Files (16)
File Name
Version
Size
Author
Date
0.2.11
178kB
decay2
08/12/18 05:11 PM
0.2.10
178kB
decay2
07/12/18 03:49 PM
0.2.9
176kB
decay2
06/16/18 06:03 AM
0.2.8
176kB
decay2
06/12/18 02:46 PM
0.2.7
174kB
decay2
05/21/18 08:16 AM
0.2.6
173kB
decay2
04/25/18 02:31 PM
0.2.5
88kB
decay2
01/07/18 06:48 AM
0.2.4
88kB
decay2
01/05/18 12:52 PM
0.2.3
83kB
decay2
08/13/17 12:41 PM
0.2.2
83kB
decay2
07/03/17 06:30 PM
0.2.1
83kB
decay2
06/05/17 04:42 PM
0.2.0
83kB
decay2
05/28/17 10:48 AM
0.1.10
72kB
decay2
05/22/17 02:52 PM
0.1.9
72kB
decay2
05/22/17 02:41 PM
0.1.8
72kB
decay2
02/05/17 09:01 AM
0.1.7
72kB
decay2
01/15/17 04:53 PM


Post A Reply Comment Options
Unread 01/16/17, 12:56 PM  
timidobserver

Forum posts: 37
File comments: 300
Uploads: 0
Good work.

It would be awesome if this thing could track and share debuff uptimes as well. It would be awesome to be able to see PoTL, Ele Drain, Akosh, ect uptimes.
Report comment to moderator  
Reply With Quote
Unread 01/17/17, 04:20 AM  
decay2
AddOn Author - Click to view AddOns

Forum posts: 68
File comments: 336
Uploads: 6
Originally Posted by timidobserver
Good work.

It would be awesome if this thing could track and share debuff uptimes as well. It would be awesome to be able to see PoTL, Ele Drain, Akosh, ect uptimes.
I think that's too much data and goes beyond the scope of this little addon. It's possible to do it and maybe I will do it in the future, but for now I want to see how this one works out.
Last edited by decay2 : 01/17/17 at 04:21 AM.
Report comment to moderator  
Reply With Quote
Unread 04/25/17, 04:43 PM  
varousis

Forum posts: 0
File comments: 18
Uploads: 0
UI error - fixed

FIXED:
In LibgroupSocket you have to select a data source (Group damage share). For example FTC or Combat metrics. Mine was empty.
Selecting one and reloading UI and it works now.


Error when start to attack.

user:/AddOns/GroupDamageShare/LGSHandler.lua:267: operator * is not supported for nil * number
stack traceback:
user:/AddOns/GroupDamageShare/LGSHandler.lua:267: in function 'handler:Send'
user:/AddOns/GroupDamageShare/LGSHandler.lua:292: in function 'OnUpdate'

if sendFullUpdate then
dpstime = zo_round(dpstime*10,0)
index = LGS:WriteUint16(data, index, dpstime)
bits = IntToBits(source, 4, nil)
for i=1,4 do
index, bitIndex = LGS:WriteBit(data, index, bitIndex, bits[i])
end
index, bitIndex = LGS:WriteBit(data, index, bitIndex, ismagicka)
end


local function OnUpdate()
handler:Send()
end
Last edited by varousis : 04/25/17 at 04:47 PM.
Report comment to moderator  
Reply With Quote
Unread 04/25/17, 05:29 PM  
varousis

Forum posts: 0
File comments: 18
Uploads: 0
Not showing hps when toggle

Hi,

When i toggle the dps/hps buttong in the addon it only shows the dps. hps stays empty.
even when i toggle the show hps instead of dps in the addon settings.

Best would be if you can see both when toggling always.

A button or keybind to send the dps or hps parse to chat would be awesome too.
Report comment to moderator  
Reply With Quote
Unread 04/25/17, 05:39 PM  
varousis

Forum posts: 0
File comments: 18
Uploads: 0
reset dps timer

When in a group it sometimes shows the dps of the last fight (me) and current fight (other user) (or visa versa) combined? Looks like it doesnt know when a 'new' fight has started or it doesn't reset properly?

Is this because it collects the data from ftc/combat metrics and it depends on that addons combat timeout?

I see you are also the author or one of the authors of cmx. Why not adding a group hps/dps share feature to cmx?

Seems you have a all-in-one addon then?
Last edited by varousis : 04/25/17 at 06:49 PM.
Report comment to moderator  
Reply With Quote
Unread 04/26/17, 01:41 AM  
decay2
AddOn Author - Click to view AddOns

Forum posts: 68
File comments: 336
Uploads: 6
Re: reset dps timer

Originally Posted by varousis
When in a group it sometimes shows the dps of the last fight (me) and current fight (other user) (or visa versa) combined? Looks like it doesnt know when a 'new' fight has started or it doesn't reset properly?

Is this because it collects the data from ftc/combat metrics and it depends on that addons combat timeout?

I see you are also the author or one of the authors of cmx. Why not adding a group hps/dps share feature to cmx?

Seems you have a all-in-one addon then?
Regarding the timing / dps issues, you are right. However I will remove these dependencies in the next version and make this addon standalone.

As of now I don't want to incorporate this into combat metrics. Especially in this case where this is more a proof of concept and a test to see how zenimax reacts to abusing the map ping system for communication means.
Report comment to moderator  
Reply With Quote
Unread 04/26/17, 06:01 AM  
decay2
AddOn Author - Click to view AddOns

Forum posts: 68
File comments: 336
Uploads: 6
Re: Not showing hps when toggle

Originally Posted by varousis
Hi,

When i toggle the dps/hps buttong in the addon it only shows the dps. hps stays empty.
even when i toggle the show hps instead of dps in the addon settings.

Best would be if you can see both when toggling always.

A button or keybind to send the dps or hps parse to chat would be awesome too.
Thanks for reporting. I plan to change it so that both is visible at the same time and the button changes what you send. Adding an option to post a report to chat should also be possible then.
Report comment to moderator  
Reply With Quote
Unread 04/26/17, 07:36 AM  
varousis

Forum posts: 0
File comments: 18
Uploads: 0
Re: Re: Not showing hps when toggle

Thank you very much for the quick response!
Looking forward to the next update!
Report comment to moderator  
Reply With Quote
Unread 05/10/17, 01:53 PM  
varousis

Forum posts: 0
File comments: 18
Uploads: 0
Message limit error

Having the addon enables gives regulary message limits error (which results in getting dropped/kicked from the server) when doing a dungeon or trail. Even when I set the update time to 2000ms.

Questing/delves, even with 2-man is no problem so far.
Report comment to moderator  
Reply With Quote
Unread 05/10/17, 03:57 PM  
decay2
AddOn Author - Click to view AddOns

Forum posts: 68
File comments: 336
Uploads: 6
Re: Message limit error

Originally Posted by varousis
Having the addon enables gives regulary message limits error (which results in getting dropped/kicked from the server) when doing a dungeon or trail. Even when I set the update time to 2000ms.

Questing/delves, even with 2-man is no problem so far.
I experienced this myself once when combining it with sharing resources (magicka/stamina) using JoGroup or GroupResources. Apparently only one of them or Group Damage Share can be used. Maybe one needs to implement a throttle into both to not exceed the average 1 message per second which could be the lmit for map pings.

Additionally FTC has a DPS sharing option, so if you run this as well you might get a similar issue.
I'd really wish we would get some means to communicate in addons. But so far I feel Zenimax doesn't like the idea.
Last edited by decay2 : 05/10/17 at 03:57 PM.
Report comment to moderator  
Reply With Quote
Unread 05/22/17, 07:26 PM  
Kyoma
AddOn Author - Click to view AddOns

Forum posts: 62
File comments: 136
Uploads: 6
Re: Re: Message limit error

Originally Posted by decay2
Originally Posted by varousis
Having the addon enables gives regulary message limits error (which results in getting dropped/kicked from the server) when doing a dungeon or trail. Even when I set the update time to 2000ms.

Questing/delves, even with 2-man is no problem so far.
I experienced this myself once when combining it with sharing resources (magicka/stamina) using JoGroup or GroupResources. Apparently only one of them or Group Damage Share can be used. Maybe one needs to implement a throttle into both to not exceed the average 1 message per second which could be the lmit for map pings.

Additionally FTC has a DPS sharing option, so if you run this as well you might get a similar issue.
I'd really wish we would get some means to communicate in addons. But so far I feel Zenimax doesn't like the idea.
We should probably add a trottle to LibGroupSocket itself instead of in each handler seperately. Especially since Raid Notifier has ulti sharing in it now. I'll look at it tomorrow, wont be a huge problem but I'll need to make sure the handler doesn't keep queuing things while it waits for its turn on the big pile of pings.
Report comment to moderator  
Reply With Quote
Unread 05/23/17, 02:39 AM  
decay2
AddOn Author - Click to view AddOns

Forum posts: 68
File comments: 336
Uploads: 6
Re: Re: Re: Message limit error

Originally Posted by Kyoma
Originally Posted by decay2
Originally Posted by varousis
Having the addon enables gives regulary message limits error (which results in getting dropped/kicked from the server) when doing a dungeon or trail. Even when I set the update time to 2000ms.

Questing/delves, even with 2-man is no problem so far.
I experienced this myself once when combining it with sharing resources (magicka/stamina) using JoGroup or GroupResources. Apparently only one of them or Group Damage Share can be used. Maybe one needs to implement a throttle into both to not exceed the average 1 message per second which could be the lmit for map pings.

Additionally FTC has a DPS sharing option, so if you run this as well you might get a similar issue.
I'd really wish we would get some means to communicate in addons. But so far I feel Zenimax doesn't like the idea.
We should probably add a trottle to LibGroupSocket itself instead of in each handler seperately. Especially since Raid Notifier has ulti sharing in it now. I'll look at it tomorrow, wont be a huge problem but I'll need to make sure the handler doesn't keep queuing things while it waits for its turn on the big pile of pings.
I asked sirinsidiator about this yesterday but so far he didn't respond. But that would be the prime solution. It doesn't handle FTC though which seems to me to be the main competitor in this field. For now I increased the message timeout to 2s
Last edited by decay2 : 05/23/17 at 02:40 AM.
Report comment to moderator  
Reply With Quote
Unread 05/28/17, 11:37 AM  
Kyoma
AddOn Author - Click to view AddOns

Forum posts: 62
File comments: 136
Uploads: 6
Re: Re: Re: Re: Message limit error

Originally Posted by decay2
Originally Posted by Kyoma
Originally Posted by decay2
Originally Posted by varousis
Having the addon enables gives regulary message limits error (which results in getting dropped/kicked from the server) when doing a dungeon or trail. Even when I set the update time to 2000ms.

Questing/delves, even with 2-man is no problem so far.
I experienced this myself once when combining it with sharing resources (magicka/stamina) using JoGroup or GroupResources. Apparently only one of them or Group Damage Share can be used. Maybe one needs to implement a throttle into both to not exceed the average 1 message per second which could be the lmit for map pings.

Additionally FTC has a DPS sharing option, so if you run this as well you might get a similar issue.
I'd really wish we would get some means to communicate in addons. But so far I feel Zenimax doesn't like the idea.
We should probably add a trottle to LibGroupSocket itself instead of in each handler seperately. Especially since Raid Notifier has ulti sharing in it now. I'll look at it tomorrow, wont be a huge problem but I'll need to make sure the handler doesn't keep queuing things while it waits for its turn on the big pile of pings.
I asked sirinsidiator about this yesterday but so far he didn't respond. But that would be the prime solution. It doesn't handle FTC though which seems to me to be the main competitor in this field. For now I increased the message timeout to 2s
Btw, it might be good to add a few lines to your handler like this:
Lua Code:
  1. local function NumCallbacks()
  2.     local registry = LGS.cm.callbackRegistry[ON_DATA_CHANGED]
  3.     callbacks = registry and #registry or 0
  4. end
  5.  
  6. function handler:RegisterForUltimateChanges(callback)
  7.     LGS.cm:RegisterCallback(ON_ULTIMATE_CHANGED, callback)
  8.     NumCallbacks()
  9. end
  10.  
  11. function handler:UnregisterForUltimateChanges(callback)
  12.     LGS.cm:UnregisterCallback(ON_ULTIMATE_CHANGED, callback)
  13.     NumCallbacks()
  14. end
  15. ...
  16.  
  17. function handler:Send()
  18.     if(not saveData.enabled or not IsUnitGrouped("player") or callbacks == 0) then return end
  19. ....
  20. end
The main reason is that it will stop the handler from sending if there are no addons using it. This becomes especially needed when the user has addons that use multiple different handlers. What these lines effectively allow is multiple handlers to be loaded (e.g. through the manifests) without issues as long as only one handler has callbacks. I guess it is mainly a temp fix/workaround but it feels a bit more user-friendly by letting the addons themselves (also) have an option to use it or not.
Last edited by Kyoma : 05/28/17 at 11:39 AM.
Report comment to moderator  
Reply With Quote
Unread 05/28/17, 03:54 PM  
decay2
AddOn Author - Click to view AddOns

Forum posts: 68
File comments: 336
Uploads: 6
Re: Re: Re: Re: Re: Message limit error

Originally Posted by Kyoma
Btw, it might be good to add a few lines to your handler like this:
Lua Code:
  1. local function NumCallbacks()
  2.     local registry = LGS.cm.callbackRegistry[ON_DATA_CHANGED]
  3.     callbacks = registry and #registry or 0
  4. end
  5.  
  6. function handler:RegisterForUltimateChanges(callback)
  7.     LGS.cm:RegisterCallback(ON_ULTIMATE_CHANGED, callback)
  8.     NumCallbacks()
  9. end
  10.  
  11. function handler:UnregisterForUltimateChanges(callback)
  12.     LGS.cm:UnregisterCallback(ON_ULTIMATE_CHANGED, callback)
  13.     NumCallbacks()
  14. end
  15. ...
  16.  
  17. function handler:Send()
  18.     if(not saveData.enabled or not IsUnitGrouped("player") or callbacks == 0) then return end
  19. ....
  20. end
The main reason is that it will stop the handler from sending if there are no addons using it. This becomes especially needed when the user has addons that use multiple different handlers. What these lines effectively allow is multiple handlers to be loaded (e.g. through the manifests) without issues as long as only one handler has callbacks. I guess it is mainly a temp fix/workaround but it feels a bit more user-friendly by letting the addons themselves (also) have an option to use it or not.
I have a look at it tomorrow.
Report comment to moderator  
Reply With Quote
Unread 06/11/17, 03:09 PM  
Sikamoar

Forum posts: 0
File comments: 1
Uploads: 0
Addon UI Error

Anyone have an idea how to fix this UI error? I've tried switching the settings of the height and width with no luck. I tried reinstalling the addon and turning off my other addons with no luck.

The error states:

"BackdropControl: Invalid width(0) or height (0) supplied. Both must be larger than zero and powers of two.

Thanks!
Last edited by Sikamoar : 06/11/17 at 03:10 PM.
Report comment to moderator  
Reply With Quote
Post A Reply



Category Jump:

Support AddOn Development!

You have just downloaded by the author . If you like this AddOn why not consider supporting the author? This author has set up a donation account. Donations ensure that authors can continue to develop useful tools for everyone.