Sith marauder marquee event last tier doesn't drop shards

[Poison1806]

Product: Star Wars: Galaxy of Heroes
Platform:Android Phone
What type of device are you experiencing the issue with? Samsung galaxy s7
OS Version 7.0
Ally Code: (Find it here: http://bit.ly/AllyCode ) 744-797-174
What type of issue do you have? Missing Rewards
How often does the bug occur? Every time (100%)
Summarize your bug Last tier of sith marauder's marquee event did not provide any shards (same issue as holdo and rose marquee)
Steps: How can we find the bug ourselves? Check mine marauder. He is now 0/30 after completion of all tiers of the event.
Connection Type Mobile
Please select your region Europe
Country Slovakia

‌

Attached sceenshot is reward from last tier rof the event.

[jedilord1 · Accepted solution]

there are no shard-rewards for the last tier in any marquee event i can remember (also holdo and rose)
for the current marquee event (sith marauder) you only get shards as reward from tier I to tier III, and no shards for the last tier

[jedilord1 · Accepted solution]

there are no shard-rewards for the last tier in any marquee event i can remember (also holdo and rose)
for the current marquee event (sith marauder) you only get shards as reward from tier I to tier III, and no shards for the last tier

[Microfe]

and no players below 79 not getting extra 15 shard this time

[cheddarbobbyz]

I had the problem too

No shards

[UoJCAM]

It is also dropping only 1 mod when it is supposed to drop 3.

[KMichaelKillls]

I'm also getting 0/30 (so 50 shards total) after completion of all tiers. It's unclear if this is intentional or not, but after what happened with the last marquee I believe the official statement was that we should end up with 15/30 for characters that unlock at 2 stars, and 20/25 for characters that unlock at 1 star (FO executioner). Also, the bonus tier rewards say it should drop 3 mods but completing the event only rewards 1 mod.

[RevanComingSoon]

What a joke. Back to back bugs and they could care less.

And still no addressing the chimaera exploit. Fixed by ignoring . Like most of these "accepted solutions"