Lorem ipsum dolor sit amet, elit eget consectetuer adipiscing aenean dolor

Spin Me Right ‘Round

Google cache to the rescue! Using:

http://webcache.googleusercontent.com/search?q=cache:https://community.gemsofwar.com/t/spin-me-right-round/72024/1

Shows no mention about the event chest at all. Mmmm ninja edits.

My own ninja edit: The devs updating their post is fine imo. I only posted this so no one can claim the post always mentioned Weaver.

11 Likes

The AW discussion deserves to be everywhere ; it deserves an ongoing messy discussion because the compensation decision isn’t fair; and smacks of an actual lack of respect for the player base; so it will be posted everywhere; it messy; its a suitable response to post it everywhere because it remains your messy issue. Its your current Augean Stables; clean it up properly.

12 Likes

I find it super weird to edit it after the fact, tbh :sweat_smile:. Definitely feel the ‘super shady’ comments or that it rubs the wrong way. Like NerdieBirdie said,

Seriously. If it was apparently as clear as it needed to be, and no compensation is needed – why?

Edit: I guess maybe for next time, as a precedent? But still, weird.

2 Likes

True. The edit should have been transparent that it was an edit.

Changing the docs sooner rather than later is always good. Looks like the post was updated by Tues (I can’t get an exact time), so at least it was helpful for anyone checking the forums starting then.

It absolutely does not help anyone who already rolled, or anyone who saw the post pre change and rolled later, or anyone who doesnt visit the forums and shouldn’t have to because this info should be in game anyway.

Everyone who rolled Monday to Fri needs to be compensated.

6 Likes

So I guess “our final response” was before you realised that the community wouldn’t let this go. Also trying to Edit your old posts so they now - a couple of weeks after, fit what you intended is really making it look like a cover up.
Also stop saying all was working as intended - that is not the issue and you know it. Trying to use politician method to talk around the problem, trying to stear the attention away from the fact that you did not COMMUNICATE that Yvendra was exclusive to event chests too.

Please no one should go personally after Kafka or Jeto or Omniusman. They post as they are told, and isn’t a personal statement from them. So be angry, and disappointed at 505 or Ip2, but do not go after the man/woman posting for the company.

14 Likes

Yet another batch of posts, mine included, got moved out of the current thread to be buried in this one :roll_eyes:

3 Likes

Same with one of mine. Weird since not all were moved.

I suspect that important person’s are following this thread and this thread a lone. So Kafka is doing what she can to catch all important feedback in her eyes (knowing most will fall through the cracks) and consolidating it here.

I really doubt it’s “to bury” anyone’s thoughts. They can (and have) deleted or edited posts before. So if they wanted to censor thoughts. They easily could.

4 Likes

True! On one hand, just one thread for the almighty is good for them. On the other hand, conversation should occur everywhere to be seen by everyone, namely the player base.

1 Like

Sheesh. Having my comment moved actually feels really bad.

Relative to all the other nonsense. Everything is relative.

2 Likes

Censorship would further ignite flames, so diffusing threads by breaking them apart/rearranging them seems preferable, while continuing to not address the issue.

When the playerbase starts to move towards ‘settling’ what was seen as stealing a few days ago, the company knows it’s on track to get away with its practices once again.
:stuck_out_tongue: :vulcan_salute:
#DevilsAdvocate

4 Likes

For those not wanting to wade through the whole thread, here’s the summary so far:

I’ve received feedback suggesting that most players still aren’t aware of the discounted Arachnean Weaver and the conditions that apply. It doesn’t look like IP2 isn’t going to make good on their claim of notifying all players, so you might want to inform your guild members of this offer. Possibly also make them aware that IP2 owes them proper compensation for secretly removing Arachnean Weaver from events chests.

image

8 Likes

“in all fairness” I’ve never seriously debated quitting Gems of War until now.


For YEARS brand new Mythics don’t show up in event chests.

This BULL SHIT about 3 years ago has yet to be proven to exist as more than a thought and no ACTUAL Dev has cited what troop has released that way.

So congratulations after 5 years of loyalty. I have lost all faith in you devs and if I continue to play it’ll be 100% because of my guild mates.

For full context here you go:

But trust me it doesn’t read any better.

Give @Saltypatra a raise. Do whatever you need to get her back. Y’all clearly need a FULL TIME PUBLIC RELATIONS agent. Because this has been a complete cluster frank train wreck from the start all the public comments are making it worse more than better.

1 Like

Maybe Salty and the new community team could join up and form ‘The Semantic Four - Superheroes of PR’.


Paraphrasing 2018’s Pharos-Ra-Gate:

Community: “Pharos-Ra isn’t in event chests, what’s going on?”
Salty: “Pharos-Ra is in event chests.”
Community: “Hasn’t dropped for anyone after a million keys.”
Salty: “I only said he’s in event chests, I didn’t state his drop chance ;)”
Community: “0% drop chance and ‘not in chests’ are the same thing, this is just semantic yoga and you’re detracting.”
Salty: “Technically I never lied though, best kind of not lying! LOL checkmate.”


Also, War Coins are in the list of tasks eligible for the adventure board! We’re just not telling you the odds of them appearing (0% and they need to be triggered manually, LOL checkmate agaaaaain :clown_face:).

11 Likes

Please don’t forget to let your voices be heard on your respected app stores for Gems of War reviews as well.

9 Likes

Ah, right. I’d been meaning to do that.

1 Like

that convo reminds me of this

9 Likes

For those curious.

By the way, they never reimbursed Yasmine’s Chosen attempts. The official line was that this same issue did not occur with Yasmine’s Chosen, but it was also admitted that they didn’t have logs going back that far and didn’t have any way to compensate. Not having logs going back that far means they themselves had absolutely no way to verify if Yasmine’s Chosen was or wasn’t in chests, but somehow they knew the issue probably didn’t occur with Yasmine’s Chosen, so I guess its a good thing everyone just trusted them on that at the time.

After a different, unrelated drop issue about a year later was (again) correctly called out by the data sent to the client, it was unceremoniously removed under the grounds that it was “old and inaccurate” despite getting updates pushed consistently as the chests contents changed and constantly being used to call out drop issues.

FYI, I have at least one DM exchange where I brought a drop error (a minor change I just happened to notice, but I paid them the courtesy to not have it blow up publically) to the attention of the devs quietly citing these logs, they admitted and fixed the error (it was apparently an issue with how the new tool they used injected drop rates), and thanked me for bringing it to their attention. Well, a certain dev I later added to the conversation verified explained and fixed the issue, as my original point of contact stated directly and unequivocally to me that they had not changed the drop rates and then explained to me how drops work and then ignored my follow up attempts. I’m not going to name names here because this part is irrelevant, but this is the same sort of procedure I’ve gone through with many different participants any time drop rates are brought up.

Now, I know that the data sent to the client was not ever “proof” of drop rates because this data wasn’t actually used to roll drops, but there was a ton of circumstantial evidence to support that they were both generated by the same source (case in point: there is no universe where a dev would manually continue to update this unused list correctly week to week for years through all of the various minor drop rate changes, and even through big intended changes like when event keys finally switched from “mostly kingdom” to “kingdom only” this list remained accurate). I know that, if this tool, for example, existed during the delve portal drop rate fiasco, it probably would not have correctly reported the “true drop rates” either because in that case the mechanism for rolling the drops was malfunctioning and the data fed to generate said drops was technically “correct”, ie,. it would have received the same data being sent to the client to be shown in the drop rate box, which was incorrect for delve portals for over a year.

Just pointing this out because after all this, it took us months after that to even get a drop rate box in game at all (which is subject to some pretty unfortunate rounding on some of the displays that is very much statistically significant), and it was readily admitted to be a CYA measure in a dev QA. We continued to have drop issues after this (most of them being something being in chests when it shouldn’t, having varying resolutions from “yeah just keep the thing” to “heres 2 VIP keys but lose the thing no wait I mean actually lets trade it for another thing of the same rarity and keep the 2 VIP keys” to “what drop error?”). And after all this there is still no way for players to do their due diligence and check, in game, if something is on a drop table or not, and what kind of odds they have to pull it. There also used to be a countdown timer to show exactly when the next chest change would be that was also removed.

As an aside, I’m not even sure if this is still a thing or not because I don’t generally do a lot of event chest pulls, but in the past if an event troop was in both the glory pack and event keys at the same time, it was given triple weight over other troops in the event keys. Meaning if the event troop is epic, on average you’d pull 3 of that epic per one of every other one. This was confirmed by a dev on the forums here at some point as being a thing (good luck even finding the post, I believe it was by Nimhain), but it is still not nor has this ever been properly communicated in game.

So yeah, you should probably not let this one slide.

I hope people get to trade their Archproxy drops for Weaver drops eventually, but the ultimate outcome of this either way needs to be to have the tools in place to make sure that:

  1. A “misunderstanding” like this can never happen again, by having an extremely visible notification about every time chest contents change and a way to check exactly what the drops are at any given time.
  2. Any “misunderstanding” (ie, a contradiction in any official source such as forum news/in game event news, etc) and actual drop rates contradict has very unequivical evidence of what it was supposed to be so no weaseling can happen of “well actually this was intended and nothing we said before explicitly contradicts we wouldn’t make this change, and not tell anybody”. Given the circumstances of “Weavergate” even if the drop tool in game could unequivocally state that weaver was not in chests, it is still a problem that there is years of precedence of everything functioning one way, all official help articles gave no indication there would be a change, and there was. However, if the players could have at least done their due diligence and seen before they spent keys that weaver wasn’t there, such a situation would be far more amenable to a compromise. That and far less people would have been affected because the information would have spread faster because of it being in game.

Again, the mistake isn’t that it happened, its failing to correct the circumstances that caused it. Here we are, years later, and players still can’t check what is and isn’t in chests at any given time and we can no longer even tell the next and last time contents were changed, and most resources are worded just vaguely enough to not give any relevant information. Intentionally keeping people ignorant of drops and then blaming them for being ignorant as “it was working as intended all along” (and anyone on this forums having seen the last few years of bug reports at least knows how much weight those words carry) just simply won’t cut it here. This, or something like this, will happen again, so long as the circumstances for it remain.

24 Likes

Cyrup. (I’ll name her. :slightly_smiling_face:)

2 Likes

Very much this. And since we seem to be heading straight towards the still distant next fiasco, here’s something that can be referenced once it hits.

Without wanting to sound too mean, even just posting the News post each week appears to be a challenge of surprising difficulty level. Sometimes there isn’t any News post at all, sometimes it shows up broken, sometimes it talks about things from weeks past. It’s always up to the community to point out the mistakes to get them corrected, because there apparently isn’t any proof-reading at all. And you really believe that you’ll be able to inform us properly about events chests when the need next arises? Seriously?

The “engineer” solution for this is to make it fail-safe. Pick how event chests behave by default, without human interaction, make that canon. Describe in detail how it works, as an individual announcement. Adjust all Game Guides accordingly, especially those linked from the chest screens. Don’t set this up in a way just about guaranteed to fail, and once it predictably does go claiming that you only promised to “be looking at doing things”.

18 Likes