Old Daka's Serve Again zeta not working properly - Video with proof [ Edited ]

[Thereunto]

Product: Star Wars: Galaxy of Heroes
Platform:Apple iPhone
What type of device are you experiencing the issue with? IPhone 6
OS Version IOS
Ally Code: (Find it here: http://bit.ly/AllyCode ) 991562329
What type of issue do you have? Gameplay
How often does the bug occur? Every time (100%)
Summarize your bug Old Daka's Zeta'd ability for "Serve Again" is not working as advertised. It states that Old Daka gets 10% max health (stacking) until the end of the encounter for each ally revived while daka is active. However, that is not the case. In a nightsister battle against a phoenix, I had a total of 44 ally revives while daka was active until the last time I used daka's heal (which is supposed to heal for exactly 50% of daka's health and the only way to verify if the max stacking health is working). However, with a a base of health of 23196, the final healing was only , my final healing was only 39433 giving daka a max health of 78866. This means not all revives were counted (20 were not) though they should've. It also means that the 10% max health is only based on her original starting health, so for each revive my health was only going up 2320. However, because it is stacking, it should be based on her current max health, not starting health.
Steps: How can we find the bug ourselves? Use a nightsister team with talzin as lead, with maxed abliities and old daka with serve again zeta'd and use a low level zombie and spirit, (this is just to maximize revives) with a fifth nightsister. Also review this video where I got the data from above: https://photos.app.goo.gl/0IDbj44QcBAqOUKd2
Connection Type Wifi
Please select your region North America
Country USA
‌
Below is the data I collected from this battle: https://photos.app.goo.gl/0IDbj44QcBAqOUKd2 however, it is apparent in most all Nightsister Battles. As you can see from the data below I counted 44 revives, yet the game only gave me credit for 24 revives, on top of that, the max health increase was only based on the starting max health and not the current max health. (Please note, I did not get to test the revives from Talzin's Spirit Blade Assault): The discrepancies for how many revives the game calculates are highlighted in yellow. In the screenshot below I have broken down the count for each revive based on the different type of revives. Daka Revives are revives from when daka uses her aoe healing ability, Zombie revives are when the zombie revives on it's own, Talzin A Revive is when a defeated nightsister revives during another nighsister's basic attack and then is defeated. Talzin D Revives are when nightsisters are revived during another nightsister's basic attack but that attack results in the death of the opponent so they are not defeated. In effect, the severe lack of this ability from working as advertised  essentially makes this zeta'd ability worthless (it has made absolutely no noticeable difference in squad battle rank, in fact it has done more harm than good based on my current strategy). Side note: in this battle, every revive the game counts, adds ~2320 max health to old daka.
 
 

[EA_HighCommand · Accepted solution]

Hi @Cubiczars and thank you for the follow-up.

Usually, when we've flagged something as a bug, for review or further investigation, we don't follow up on the subject, since this means our part is done. It is then up to the studio team to decide as to how and when something is being fixed. You can get an update from the patch notes HERE. As for Old Daka's unique ability "Serve Again", we've tested this today and it worked as intended. Every time another ally was revived, she gained 10% max health.

[Cubiczars]

So I watched through the video and can confirm what he is saying at least up to a certain point (didn't catalog the entire video, got to about 6mins in).

1) Daka seems to be gaining 10% of her STARTING max health not her subsequently higher max health on each revive (2320 per revive) so linear growth instead of exponential (likely intended but certainly not the way the description reads)

2) The game is definitely not counting a certain type of revive, specifically the Mother zeta revive on basic attack.

3) There seems to be some form of Mother zeta revive that does count but it looks like it is an edge case dealing with the double attack Acolyte double revive possibly.

To analyse this I charted the revive count vs the expected heal amount and also charted which kind of revive to get an idea of where the bug was at. The break down is as follows:

1) 1st Heal:   11598   Revives: 0  Mother Zeta Revives:   0   Expected heal:   11598

2) 2nd Heal:   13918   Revives: 3  Mother Zeta Revives:   1   Expected heal:   15077(or 15078 if round is always up)

3) 3rd Heal:   17397   Revives: 6   Mother Zeta Revives:   1   Expected Heal:   18557

4) 4th Heal:   23196   Revives: 8   Mother Zeta Revives:   1   Expected Heal:   24356

5) 5th Heal:   28995   Revives: 23  Mother Zeta Revives: 9   Expected Heal:   38273(or 38274 if round is always up)

The heal that doesn't fit the pattern quite right is heal number 5.  If you calculate out the expected heal for 14 revives you get 27835 (23 - 9 Mother zeta heals == 14) but what the actual heal amount was fits what we expect from 15 revives.  Unfortunately with number of revives between heals jumping so high and so many different types of revives happening in that time period (bunch of single Mother zeta revives from daka, and at least one double revive from the Acolyte where both survive due to the enemy dieing) we have a situation where A: I could have over counted B: there is some sort of edge case where one revive counts and another doesn't.  So having 9 instead of 8 could either be my error or some special case but given how consistent it was at the beginning and being off by only one revive with the 5th heal I feel like the bug can be narrowed down to looking specifically at cases where the Mother zeta is causing the revives.

[Thereunto]

Looks like my initial image got removed after I edited the title, so I'm just posting it in as text. It includes my count and analysis, the major discrepancies for me were on the 2nd, 6th, 8th, and 9th heals. These occurred at the 1:05 time mark, the 6:31 time mark, and the 10:07 time mark. The second heal I counted 3 revives yet only 2 were given credit for. The 6th heal I counted 14 revives, yet only 5 were given credit for, on the 8th heal 5 revives were counted and only 2 were given credit for, and the 9th heal I counted 12 revives and only 5 were given credit for. 

	Max Health	Healing	Daka Revives	Zombie Revives	Talzin A Revives	Talzin D Revives	Total Revives	Time of Daka Heal	# of Actual Revives Game Uses since Last Heal	Total Revives since Last Heal
1	23196	11598	0	0	0	0	0	0:47	0	0
2	27836	13918	1	1	1	0	3	1:05	2	3
3	34794	17397	1	2	0	0	6	1:39	3	3
4	39432	19716	0	2	0	0	8	2:23	2	2
5	46392	23196	0	3	0	0	11	2:49	3	3
6	57990	28995	0	4	8	2	25	6:31	5	14
7	62788	31314	0	2	0	0	27	7:09	2	2
8	67268	33634	0	2	3	0	32	8:35	2	5
9	78866	39433	1	4	7	0	44	10:07	5	12
Totals as of 10:07	78866	39433	3	20	19	2	44	10:07

[Thereunto]

I've analysed two more battles, and it appears that the zombie revivals are mostly getting accounted for correctly, the Talzin's Great Mother leadership ability (and possibly spirit blade assault) is not getting counted properly, and there may be issues when multiple allies get revived in one turn.

this battle shows Talzin's leadership ability not getting counted in the revives: https://photos.app.goo.gl/2GDGsnmGEp4zfZhA3

Second Battle	Max Health	Healing	Daka Revives	Zombie Revives	Talzin A Revives	Talzin D Revives	Total Revives	Time of Daka Heal	# of Actual Revives Game Uses since Last Heal	Total Revives since Last Heal
1	23196	11598	0	0	0	0	0	0:45	0	0
2	27836	13918	0	2	1	0	3	1:17	2	3
3	30154	15077	1	0	2	0	6	1:50	1	3
Totals as of 1:50	30154	15077	1	2	3	0	6	1:50

Third battle https://photos.app.goo.gl/Jzd14A8VSotpi7f32

3rd Battle	Max Health	Healing	Daka Revives	Zombie Revives	Talzin A Revives	Talzin D Revives	Total Revives	Time of Daka Heal	# of Actual Revives Game Uses since Last Heal	Total Revives since Last Heal
1	23196	11598	0	0	0	0	0	0:35	0	0
2	27836	13918	0	1	0	0	1	1:02	1	1
3	34794	17397	1	2	2	0	6	1:51	3	5
4	39432	19716	1	1	3	0	11	2:33	2	5
5	48712	24356	2	3	3	0	19	4:02	4	8
6	53350	26675	1	1	3	0	24	4:31	2	5
Totals as of 4:31	53350	56675	5	8	11	0	24	4:31

[PremierVenoth]

Agreed, I did the Zeta and it definitely makes her tougher, but I was hoping it would make her a little more beastly like assajj.  Thank you for running the numbers to confirm what I had a vague suspicion on.

Glad this, too, has come here to the Answer's graveyard to die and never get addressed.  Like all the other NS bugs that have been lodged.  Apparently if you can't get 500 people to comment on your bug it, it doesn't really exist.

[CG_Kozispoon]

Hiya,

Our team is investigating this issue, but we'll need to deep dive on this one, so please bear with us.

[scuba75]

My best guess, and maybe this will help the dev's @CG_Kozispoon look into it, is that it doesn't look if someone is revived till turn end which the ones revived from MT lead ability are killed off before the end of the turn. If you notice in the battles NS revived by MT lead do not get the offense/defense up from daka unique when revived with MT lead until the end of the turn if they stay revived, if they pop up and go back down they don't get the Offense and defense up.

[Thereunto]

Any updates to the status of this bug? Is there any more information you guys need to reproduce this?

[Thereunto]

This is a weekly update requesting status information for this bug. I never heard back previously if you need additional information on it or not. This bug is still a major issue for my main squad team. 

[Thereunto]

Any updates on the status of this bug? I've essentially had a worthless zeta for the last few months. If there aren't any plans to fix this zeta ability, I'd really just like it removed and the materials refunded please. The nightsisters have been my main and favorite team since Talzin came out but the amount of bugs they contain and lack of interest in fixing them has been so demoralizing, I may as well just jump ship and join the emperor teams like everybody else...