› ›

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links

Bug in numbers

cosycosy Member UncommonPosts: 3,228
in Mortal Online

i just took a look on the bug tracker

Art Related Bugs


  • New / Unconfirmed 29

  • Confirmed 1

  • Feedback / Confirmations Needed 0

  • Fixed / Implemented 19

  • Discarded/Not Reproducible 7

  • Duplicate 5

Code Related Bugs


  • New / Unconfirmed 165

  • Confirmed 51

  • Feedback / Confirmations Needed 18

  • Fixed / Implemented 60

  • Discarded/Not Reproducible 31

  • Duplicate 17

Crashes


  • New / Unconfirmed 5

  • Confirmed 0

  • Feedback / Confirmations Needed 4

  • Fixed / Implemented 2

  • Discarded/Not Reproducible 7

  • Duplicate 0

you can make a idea of how many bugs the game have and how fast/slow the bugs are fixed.

Plz note that anyone can fill a bug report and some of the new/unconfirmed bugs can be duplicate

BestSigEver :P
image

Comments

  • QunitillianQunitillian Member Posts: 99

    That is a lot of bugs! I just don't understand how the game can be scored at 6.9 by an mmorpg.com reviewer. Please note that often when they say they have fixed a bug the truth of the matter is that they have not; many of these bugs re-occur with new patches and they have to fix them again.

  • BuniontToesBuniontToes Member Posts: 529

    Actually that is an unbeleiveable small number of bugs.  Thi si snot a good thing.  It means they are either hiding bugs, or thier QA is inept.

     

    Any product/large project will have manu hundreds, if not thousands of bugs at any given time.  Bug that range from :Icon x is exactly the wrong sahde of cornflower blue" to major user impact issues.

     

    Anyone who has been invovled (or run) a competent QA team will  have experience sorting through a LARGE number of issues and deciding impact.  Bugs which have lo impact will not get fixed for the next release.  This is a simple fact of life in teams with finite resources.

  • AjmagsAjmags Member UncommonPosts: 63

    Originally posted by Qunitillian

    That is a lot of bugs! I just don't understand how the game can be scored at 6.9 by an mmorpg.com reviewer. Please note that often when they say they have fixed a bug the truth of the matter is that they have not; many of these bugs re-occur with new patches and they have to fix them again.

     Yep its been the case since Block A .  Its like a revolving mess of bugs that never go away. Its like Gnats online you may kill one but 50 more fly in your face.

    http://www.prophecyguild.net

  • cosycosy Member UncommonPosts: 3,228

    Art Related Bugs

    * New / Unconfirmed 48
    * Confirmed 1
    * Feedback / Confirmations Needed 0
    * Fixed / Implemented 20
    * Discarded/Not Reproducible 8
    * Duplicate 6

    Code Related Bugs

    * New / Unconfirmed 205
    * Confirmed 43
    * Feedback / Confirmations Needed 20
    * Fixed / Implemented 150
    * Discarded/Not Reproducible 65
    * Duplicate 20

    Crashes

    * New / Unconfirmed 16
    * Confirmed 0
    * Feedback / Confirmations Needed 6
    * Fixed / Implemented 3
    * Discarded/Not Reproducible 7
    * Duplicate 0


    a small update from the list seams to be 90 code bugs fixed since my OP

    BestSigEver :P
    image

  • HerculesSASHerculesSAS Member Posts: 1,272

    Most modern software companies (gaming companies included) run with a zero defect policy. It doesn't mean there are no bugs, it's a way to do testing.

     

    Unsurprisingly, SV has no idea what this is.

  • funkmastaDfunkmastaD Member UncommonPosts: 647

    Originally posted by BuniontToes

    Actually that is an unbeleiveable small number of bugs.  Thi si snot a good thing.  It means they are either hiding bugs, or thier QA is inept.

     

    Any product/large project will have manu hundreds, if not thousands of bugs at any given time.  Bug that range from :Icon x is exactly the wrong sahde of cornflower blue" to major user impact issues.

     

    Anyone who has been invovled (or run) a competent QA team will  have experience sorting through a LARGE number of issues and deciding impact.  Bugs which have lo impact will not get fixed for the next release.  This is a simple fact of life in teams with finite resources.

    Haha.  Half this thread is people going "OMG that's alot of bugs, MO sucks!!"... I like where you go "OMG that's not enough bugs, MO sucks" instead.  Not being sarcastic, I honestly got a kick out of it.

  • HanoverZHanoverZ Member Posts: 1,239

    MOs "bugs" are only the tip of the iceberg. it has issues on a core level which may never get fixed.

    I win!!! LOL@U

  • NeoptolemusNeoptolemus Member Posts: 242

    Originally posted by funkmastaD

    Originally posted by BuniontToes

    Actually that is an unbeleiveable small number of bugs.  Thi si snot a good thing.  It means they are either hiding bugs, or thier QA is inept.

     

    Any product/large project will have manu hundreds, if not thousands of bugs at any given time.  Bug that range from :Icon x is exactly the wrong sahde of cornflower blue" to major user impact issues.

     

    Anyone who has been invovled (or run) a competent QA team will  have experience sorting through a LARGE number of issues and deciding impact.  Bugs which have lo impact will not get fixed for the next release.  This is a simple fact of life in teams with finite resources.

    Haha.  Half this thread is people going "OMG that's alot of bugs, MO sucks!!"... I like where you go "OMG that's not enough bugs, MO sucks" instead.  Not being sarcastic, I honestly got a kick out of it.

     To be fair, its unlikely that many people here have done software testing or QA, so its entirely possible that 100 bugs would sound like a lot to to the uninitiated while in fact its the opposite

  • HanoverZHanoverZ Member Posts: 1,239

    Originally posted by Neoptolemus

    Originally posted by funkmastaD

    Originally posted by BuniontToes

    Actually that is an unbeleiveable small number of bugs.  Thi si snot a good thing.  It means they are either hiding bugs, or thier QA is inept.

     

    Any product/large project will have manu hundreds, if not thousands of bugs at any given time.  Bug that range from :Icon x is exactly the wrong sahde of cornflower blue" to major user impact issues.

     

    Anyone who has been invovled (or run) a competent QA team will  have experience sorting through a LARGE number of issues and deciding impact.  Bugs which have lo impact will not get fixed for the next release.  This is a simple fact of life in teams with finite resources.

    Haha.  Half this thread is people going "OMG that's alot of bugs, MO sucks!!"... I like where you go "OMG that's not enough bugs, MO sucks" instead.  Not being sarcastic, I honestly got a kick out of it.

     To be fair, its unlikely that many people here have done software testing or QA, so its entirely possible that 100 bugs would sound like a lot to to the uninitiated while in fact its the opposite

    100 or 1000, does it really matter? What matters is their overall impact on gameplay and the Devs ability/inability  to fix.  Many of MO's "bugs" are really fundamental mechanic problems and limits of the game itself.

    I win!!! LOL@U

  • apomfapomf Member Posts: 2

    And those would be...?

  • TorgrimTorgrim Member CommonPosts: 2,088

    Originally posted by HanoverZ

    MOs "bugs" are only the tip of the iceberg. it has issues on a core level which may never get fixed.

    Such as?

    If it's not broken, you are not innovating.

Sign In or Register to comment.