Broker Broken by Today’s Update – Culprit to Remain Nameless

Written by Feldon on . Posted in Game Updates & Maintenance

Despite alarm bells being raised by the EQ2 Testing community on the EQ2 Forums, in /bug, and on Facebook, Monday‘s Test Update has been pushed to the live EQ2 servers with a show-stopping bug:

  • Any item which cannot be equipped is now nameless on the Broker and cannot be searched for.
  • Items which you have listed for sale on the Broker that cannot be equipped are shown as having no name.

This means you cannot search for Dungeon Maker items, Raw Materials, Collectibles, Consumables, basically anything that you cannot equip. You can use Category filters (as shown above), but you cannot refine the search. Every affected item just shows the icon without its name. If you do not have a custom UI, you can roll over the item to see details. An unannounced change to tooltips has been made that breaks them in ProfitUI, DrumsUI, DarqUI, etc.

Your items for sale are also affected:

Update:

Players searching for [eq2u]Krono[/eq2u] will get no respect:

NOTE: Before someone comments, yes I am using a custom UI for my Broker — ProfitUI’s Market Window. But this problem is being seen gamewide in all UIs including the Default.

Commentary

I really have to ask what is the chain of command here on Test vs. Live?

Hero’s Festival went live despite announcements from Kaitheel and a Producer all saying the event was delayed.

Now this show-stopping Broker bug goes Live despite /bug, threads, and Facebook posts saying DO NOT push this Live.

It’s like the Platform guy who pushes things from Test to Live has absolutely no communication with anyone on the game team and just pushes the button on the time/date specified. It’s like Desmond on Lost. He keeps pushing the button but has no idea why.

Trackback from your site.

Comments (18)

  • Electri

    |

    Wondering who will be the first to say, “We told you so”. lol

    Reply

  • badcat

    |

    Sad but true this was reported in test, and they totaly ignored the fact it was broken, and reported.

    Reply

  • Silzin

    |

    WOW this shows an extreme lack of a QC teem and a lack of the ability to Communicate within the over all teem.

    ….just WOW

    Reply

  • Le Clown

    |

    L-O-L

    Reply

  • uncle

    |

    thats alright did you see the post on test update board about items showing they are sold for real money :/

    Reply

  • sands

    |

    They definitely need a more visible method for tracking bugs. Someone set up a public bugzilla site for them. 🙂

    Reply

  • Loch

    |

    So will the excuse this time be the same as the broken CoV? That the wrong code was accidentally pushed through?

    Sure.

    Reply

  • yslrtrg

    |

    Wow… just wow… and yet… not.

    Reply

  • Avianna

    |

    This proves that they do not listen to their customer base on test, and are completely and utterly clueless and the team does not play the game. if they themselves played the game and were on test themselves us as players would be able to better communicate with them and KNOW they see the bug so they would have no excuses. This type of a mistake is inexcusable in my opinion. it is a major bug, one that effects the entire playerbase, and it was reported, bugged, feedbacked, facebooked, twittered, posted on the forums, and still went thru…. What is wrong with this picture? only way to make it more obvious to SOE would be to write it on a 2×4 and cast it upside someones head!

    Whoever is in charge of the bug reports and feedback should be fired over this. No excuse!

    Reply

  • Revekk

    |

    I just don’t get it. Offices of people working on content, expansions, features, loads of community relations people , multiple managers and not one person spent the 5 minutes to even look at the test feedback forum, or if they did not relay the problems on.
    It literally boggles my mind. There is no excuse at all.

    Unintended problems I can see an excuse.

    Reply

  • Arbo@

    |

    Last time i felt some sort of connection to player base was in DoV Beta when a GM ( Klaws or so ? ) is doing some instance runs..

    Reply

  • bhagpuss

    |

    After more than five years playing on Test as my main server, constantly reporting bugs, discussing them on the forums and in-game with numerous devs and QA people, then seeing the very same bugs pushed to Live, I can’t say this surprises me.

    For many years the Test community was frequently vilified for elitism, laziness, or incompetence and seen as a pointless bump in the smooth road of development. In the last couple of years, particularly with Test Copy allowing anyone and everyone to have a go at testing without having to level up a character, I think it’s finally begun to come home to the general playerbase that it’s not finding the bugs that the problem – it’s getting anyone to listen.

    Oh, and didn’t SoE just get an amazing new Testing tool that allows them to correct content on the fly so things like this wouldn’t happen any more?

    Reply

  • daburn

    |

    who cares whos fault it is players only care when it will be fixed like now mabey

    Reply

  • yslrtrg

    |

    @Bhagpuss:

    “Oh, and didn’t SoE just get an amazing new Testing tool that allows them to correct content on the fly so things like this wouldn’t happen any more?”

    Yeah, good call.

    Reply

  • Vex

    |

    @Bhagpuss, welcome to QA. It’s a lovely job that just is there to destroy development.

    Reply

  • Whilhelmina

    |

    I’m all with you on that one Bhagpuss. The worst part is that it’s really a major bug, I thought at least, major bugs would be looked at 🙁

    Reply

  • Ferrek

    |

    Good ole Sony, fix 1 issue, break 2 others lol

    Reply

  • Dark

    |

    Aside from it being reported on test, how in the world does this get past QA..?

    That’s almost Mojang level incompetence.

    Reply

Leave a comment

You must be logged in to post a comment.


Powered by Warp Theme Framework