Was probably done more manually than automatically. So this type of stuff are expected. The only reason they chose to do this method this time was probably because “no one” hatched for goliath, making the job doable. With hazuki egg, being a new release on top of the “exploit” being “abused” immediately on egg release, i suspect there were too many people to go over manually
Again. I did not abuse anything. Goliatherion was the only mythic I have not awakened from the banners that were out on that day. That’s why I was rolling for it. And my intention was to wake it up as I did on the next day when the egg pool was corrected and banner time was extended.
I didn’t say it for you bro, it was just a joke. Don’t take it personally, Still 1000 gems would be nice lol
Since stuff like this is happening and we have no way of checking hatch history to confirm what the numbers should actually be (unless we record hatches ourselves), I think the best option here would be a gem refund.
Now this looks very messy and non-transparent.
5 Likes
“Just when I think you can’t get any dumber… you do something like this… AND TOTALLY REDEEM YOURSELF.”
Can anyone name that movie?
I do think Exu is spot on here, I’ve also come around to this conclusion.
1 Like
Let’s say if @Coltraz and @GMagic didn’t hatch all 30 packs and stopped at 20-25 packs and they didn’t get the beetle only got the rozaliz and standard pool myths. In this case they will say there was not the monster that was on the poster and not in the egg pool. Will that be considered as hazuki banner mishap? Will that be viable for refund? And I’m just asking this out of curiosity and it doesn’t mean to offend anyone in any regard.
Monster odds in the Egg List are generated automatically by our system first, by calculating how many monsters are in the pool. Then, we implement the entire chunk of text into the game. If the pool is incorrect, the odds will be incorrect as well.
The issue this time is that the featured monsters in the Goliatherion banner were overridden by Rozaliz’s. It was essentially just another Rozaliz banner, and had nothing to do with the hatching odds.
In fact, the reason some users were able to hatch all the way to the pity counter and get Goliatherion was because the pity count did NOT reset, even if they hatched the wrong ‘featured’ monster, Rozaliz. Players actually had a better chance of getting a featured Mythic in this banner than in the other egg banners.
4 Likes
These later rewards were duplicate reward entries that failed to be claimed the first time, since all rewards can only be claimed once. We noticed this after some players pointed it out here and fixed them.
This had nothing to do with hitting pity or not because, for sure, the monsters were not there. That’s why we sent them the monsters they wanted to hatch as the compensation.
We sent you the wrong product, so we will send you the correct one again, and you can keep the wrong one.
Like I said in the previous post, the pity timer in this banner actually served as an extra bonus since it didn’t reset after hatching the wrong featured monster.
2 Likes
You also hatched and didn’t get refund 
Well now wait, this is misleading and I think totally misses the point. Respectfully, I’m failing to see how it isn’t outright false? Maybe I’m missing something?
Players weren’t hatching the Goliath banner to get a featured mythic from another banner. We physically couldn’t get Goliath until the pity timer. Just because Rozaliz was a “featured mythic” from another banner that was thrown into the pool with standard mythics doesn’t mean you got the featured you hatched for.
If I hatch 10 packs, get a Rozaliz egg (that would have been the Goliath shard I wanted), then hatch another 20 packs to pity, it doesn’t matter what that 10th pack gave me if it wasn’t Goliath. It could have been any standard mythic. That’s how backwards broken the egg was - the coded “featured” mythic here didn’t count toward the pity - but it still resulted in hella more hatches than otherwise would have taken place.
1 Like
You are totally right. That’s why we sent the featured you hatched for as the compensation.
1 Like
What i believe he meant to say, if the banner was correct and he got lucky he would not go all the way for pity timer
For example if i was one shard away from awaking and got the dinosaur girl in my first pack and did not know that the banner was was glitched i would have stopped at the first pack as that would be my stop point but since the banner was glitched, that resulted in spending an extra 29 packs to get the last shard, which would not have been my intention to do if things were correct
Rip for all those that went all out in the hopes of a gem refund
If you already knew the egg was wrong, what was the reason or motive for going all the way to the pity timer?
You know the game has 3000+ monsters at this point and not everyone knows if the banner is glitched or not, specially the new players or returning players
1 Like
I totally understand your point. We couldn’t identify the abusers among them, which is why we decided to let players keep the wrong monsters they hatched as part of the compensation for the gems spent.
1 Like
I understand the approach you have went with and i believe its the first time you do this approach, i would also believe many tried to abuse this because in the past a gem refund was given
1 Like
Well first, I think Coltraz and I’s point, that I think some people are seeing, is that we literally would have stopped hatching a multitude of eggs earlier. We burned gems at something that we had no idea wasn’t actually there and we had no way of knowing that at the time.
Separately, as far as the initial decision that was made:
I don’t doubt that the decision maker’s intentions were pure in letting people keep whatever they hatched, but they essentially made the judgment for the players that the players would rather
- Keep the things they weren’t actually hatching for and lose all the resources they spent along the way
As opposed to:
- Have their resources back and lose the things they weren’t even hatching for.
I, and others, think that is the wrong decision and it feels weird to have it made for us when it’s not our coding error that caused this.
And honorable mention, thirdly, the solution structure of number 1 above being botched didn’t help the trust level either.
2 Likes
From Coltraz’s first reported post, it seems very clear that the egg was wrong, and many forum users were already aware of it at that time. What I’m questioning is the motive behind hatching all the way to the pity timer after knowing the egg was wrong.
I really appreciate that you and Coltraz did it just to try to figure out what was going on… I’m just not sure how many people would be okay with us refunding all the gems to the players who helped us test the egg all the way to the pity timer.
We issued a gem refund for the Hazuki banner because the issue was that E.D. Gul was supposed to be on the banner instead of G.F. Sunflower. They are completely different rarity monsters with different hatching rates. We could not compensate every E.D. Gul that players hatched with a G.F. Sunflower at that time.
Last day of egg, and someone like coltraz hatches to pity more often than not probably.
1 Like