Results 1 to 10 of 12

Thread: Elezen Hair

Hybrid View

  1. #1
    They ask for the information because they can't file the bug report with the dev team without it? Because its SOP for any Q/A procedure in a large company, or a company with multiple offices? Because you never know just what the real problem is?

    As someone who has been a tech for many years, I can attest to the need for it - even though sometimes it seems stupid (and sometimes IS stupid). At the very minimum it is because by getting all the information they cover their back sides. In a best case scenario they uncover some hidden bug or really off-the-wall problem with the information that we think is useless. Either way, it is due diligence. If you must complain about the process, I suggest poking at SE people who set the policies, not the Mods that are trying to help us out, but must follow the rules in order to keep their jobs.
    (1)
    Pooka Pucel - Sanctus Refero - Besaid - http://www.sanctusrefero.com/

  2. #2
    Player
    Frein's Avatar
    Join Date
    Aug 2011
    Posts
    652
    Character
    Frein Mannis
    World
    Ragnarok
    Main Class
    Arcanist Lv 50
    Quote Originally Posted by origamikitsune View Post
    As someone who has been a tech for many years, I can attest to the need for it - even though sometimes it seems stupid (and sometimes IS stupid).
    It almost surely is stupid this time. He may almost as well have asked when he last ordered pizza.

    Pointless bureaucracy is one of the most infuriating things in this world, company policy or not. It does not produce any value for anyone yet costs time and effort for no reason. I'm sure the devs, who are (hopefully) human, are able to process normal text without the need for rows of pointless data. Surely the community staff is capable of creating characters within the game and are also perfectly capable of testing this themselves, evaluating if the hair is indeed overly animated, and forwarding the feedback. This is extremely unlikely to even be an actual bug.
    (0)

Tags for this Thread