Known Issue: Story Mode Nodes *Updated (4/13/17)
Comments
-
New McG said:While I appreciate the communication on this, the backtracking on this seems more disingenuous than on some of the recent changes. (For most of which I've tried to be fairly defensive of the devs.)
When the defense to this one is "well, this changed but other bugs didn't get fixed because the UI team is different from the gameplay team", and then after it's universally disliked the story changes to, "oops, no, wait it's an 'issue' to be addressed", that makes it seem like the initial story was a way to try and avoid having to deal with the bug by selling it as a "new feature". It makes it sound as if the UI team had specifically made an effort to explain why the "new feature" had happened, because otherwise it would make the most sense for it to be explained as "it's a bug, we'll get it fixed". It's mildly disheartening as someone who really wants to think the team behind the game has the best intentions, even on seemingly small things.
The backtracking was not to mislead the player base, but rather my correction of the announcement to display the intended appropriate information. Once again, I apologize for any confusion this may have caused.
@Skrofa @mpqr7 [Added as they had asked about this in a previous comment]
22 -
So it's not been mentioned as a bug and not a feature.
That makes me VERY curious. Either...
1) They told Brigby that it was a feature and he relayed that news to unexpected backlash, so they're reverting it.
2) They didn't tell Brigby that it was a bug and he made a topic on his own announcing this sudden change so we know it was something the team knew about and not just a "Spot the changes!" update they tried to slip by us
3) They didn't tell Brigby *anything* and only *now* has he found out about it.
Either way, I get the feeling Brigby got blindsided by this, which is a terrible thing to do to your community relations guy. If something happens within the game that needs pointing out, Brigby should be given the information on it.
Brigby has either been lied to or mis-informed. In any case I want to hope Brigby sends them an e-mail entitled "**** guys!?" and gets this sorted out.
1 -
@Dragon_Nexus
This was not the fault of the development team, but rather my own fault of misreading the information they presented me with. I did make the announcement on my own to inform the players of this change, but the information given was originally intended to be a notice of a bug, as opposed to a new feature.
I have edited the title, updated the original post, and made a few comment replies to explain myself further. (One of which is actually above your post, coincidentally)
9 -
Brigby said:New McG said:While I appreciate the communication on this, the backtracking on this seems more disingenuous than on some of the recent changes. (For most of which I've tried to be fairly defensive of the devs.)
When the defense to this one is "well, this changed but other bugs didn't get fixed because the UI team is different from the gameplay team", and then after it's universally disliked the story changes to, "oops, no, wait it's an 'issue' to be addressed", that makes it seem like the initial story was a way to try and avoid having to deal with the bug by selling it as a "new feature". It makes it sound as if the UI team had specifically made an effort to explain why the "new feature" had happened, because otherwise it would make the most sense for it to be explained as "it's a bug, we'll get it fixed". It's mildly disheartening as someone who really wants to think the team behind the game has the best intentions, even on seemingly small things.
The backtracking was not to mislead the player base, but rather my correction of the announcement to display the intended appropriate information. Once again, I apologize for any confusion this may have caused.1 -
So as I posted - I was correct. It was a bug that was then tried to be covered as an "improvement" only to then realize it was doing what they thought either.
High comedy of errors.0 -
Brigby said:New McG said:While I appreciate the communication on this, the backtracking on this seems more disingenuous than on some of the recent changes. (For most of which I've tried to be fairly defensive of the devs.)
When the defense to this one is "well, this changed but other bugs didn't get fixed because the UI team is different from the gameplay team", and then after it's universally disliked the story changes to, "oops, no, wait it's an 'issue' to be addressed", that makes it seem like the initial story was a way to try and avoid having to deal with the bug by selling it as a "new feature". It makes it sound as if the UI team had specifically made an effort to explain why the "new feature" had happened, because otherwise it would make the most sense for it to be explained as "it's a bug, we'll get it fixed". It's mildly disheartening as someone who really wants to think the team behind the game has the best intentions, even on seemingly small things.
The backtracking was not to mislead the player base, but rather my correction of the announcement to display the intended appropriate information. Once again, I apologize for any confusion this may have caused.
@Skrofa @mpqr7 [Added as they had asked about this in a previous comment]
As I said, I've tried my best to be a neutral party in the discussions of some of the other various changes lately. The message of this one was what threw me, and I'm glad it's just a bug. If nothing else, should a beneficial change to the UI come from this somewhere down the road, it will be worth the hassle. Thanks again, Brigby.0 -
LifeofAgony said:So as I posted - I was correct. It was a bug that was then tried to be covered as an "improvement" only to then realize it was doing what they thought either.
High comedy of errors.4 -
Sorry that I'm dubious of any messages coming from the devs at this point, and while it's nice that brigby is taking one for the team, im not buying.
You believe what you like, and I'll do the same.0 -
Phew.. that's a relief. I don't care how this got mixed up and reported as an intended change, I'm just really glad it turns out to be a bug. Best moment of the day!1
-
bluewolf said:What is the dev's goal? User-friendly UI? Ease in understanding your progress at a glance? If yes, revert to prior or implement one of the many suggestions. Is your goal confusion? Making things unclear for some reason? Leave as is.
The green check mark was widely praised. It makes it easier and more fun to play the game. Again, what is your goal?
Thanks to Brigby for taking resposibility too.0 -
Brigby said:@Felonius
This was a rather recent bug occurrence, so I'm afraid I am not aware of a definitive time-frame for the fix. I will be sure to update everyone should I receive news of a fix date.5 -
@Brigby i am reading your first post (edit version) and it says its a known bug.
But a few comments before you are saying is a rather recent bug occurence.
My english are not very good so i might not understand well but i think these 2 sentences dont fit. No?0 -
nickaraxnos said:@Brigby i am reading your first post (edit version) and it says its a known bug.
But a few comments before you are saying is a rather recent bug occurence.
My english are not very good so i might not understand well but i think these 2 sentences dont fit. No?3 -
Brigby said:@Dragon_Nexus
This was not the fault of the development team, but rather my own fault of misreading the information they presented me with. I did make the announcement on my own to inform the players of this change, but the information given was originally intended to be a notice of a bug, as opposed to a new feature.
I have edited the title, updated the original post, and made a few comment replies to explain myself further. (One of which is actually above your post, coincidentally)
The actual reason is better than the scenario I was envisioning, for sure. I posed in frustration simply because I couldn't believe this 'feature' was a bug and they hadn't actually told you.
I'm much happier to accept human error as a reason for this kind of topic compared to deception. So this is a much better outcome.
Apologies again for casting shade where there was none.
1 -
Brigby said:@Felonius
This was a rather recent bug occurrence, so I'm afraid I am not aware of a definitive time-frame for the fix. I will be sure to update everyone should I receive news of a fix date.
Brigby,Understood. I eagerly look forward to your update. Thanks for the reply and keeping us up to date!
0 -
Thank hell for this revelation. It's refreshing to see so many forum residents retract their claws upon getting a sincere apology from Brigby (the poor bag-man in this situation). That's how you do!
6 -
LordXberk said:Borstock said:I don't like the change, but I will admit to having a hard time figuring out what is so difficult about keeping track of how many times you've cleared a node. I always play in order. That order changes depending on my mood and whether or not I'm competing or just clearing for rewards, but it's an order nonetheless. I rarely look at the clears number at all. I know how many times I've cleared a particular node because I know where I am in the order.
0 -
ejm04 said:Borstock said:I don't like the change, but I will admit to having a hard time figuring out what is so difficult about keeping track of how many times you've cleared a node. I always play in order. That order changes depending on my mood and whether or not I'm competing or just clearing for rewards, but it's an order nonetheless. I rarely look at the clears number at all. I know how many times I've cleared a particular node because I know where I am in the order.
That works for ordered subs. Florida was a mess. Savage Land isn't much better. There are plenty out there that aren't along a straight progression.
0
Categories
- All Categories
- 44.8K Marvel Puzzle Quest
- 1.5K MPQ News and Announcements
- 20.2K MPQ General Discussion
- 3K MPQ Tips and Guides
- 2K MPQ Character Discussion
- 171 MPQ Supports Discussion
- 2.5K MPQ Events, Tournaments, and Missions
- 2.8K MPQ Alliances
- 6.3K MPQ Suggestions and Feedback
- 6.2K MPQ Bugs and Technical Issues
- 13.6K Magic: The Gathering - Puzzle Quest
- 503 MtGPQ News & Announcements
- 5.4K MtGPQ General Discussion
- 99 MtGPQ Tips & Guides
- 421 MtGPQ Deck Strategy & Planeswalker Discussion
- 298 MtGPQ Events
- 60 MtGPQ Coalitions
- 1.2K MtGPQ Suggestions & Feedback
- 5.6K MtGPQ Bugs & Technical Issues
- 548 Other 505 Go Inc. Games
- 21 Puzzle Quest: The Legend Returns
- 5 Adventure Gnome
- 6 Word Designer: Country Home
- 381 Other Games
- 142 General Discussion
- 239 Off Topic
- 7 505 Go Inc. Forum Rules
- 7 Forum Rules and Site Announcements