🛈 Announcement
Greetings! The Division forums are now archived and accessible in read-only mode, please go to the new platform to discuss the game
  1. #1

    Take the word "fix" out of the patch notes.

    Don't use that word. I'm serious and not just whining.

    I can respect you saying "we're trying" or "we're working on it". If you say you "fixed" an issue, that means the issue no longer exists (for anybody). That never happens. Ever.

    So, seriously, don't use the word "fixed". That small step will actually go a long way with maintaining respect with the player base.

    Imagine it as if it were your car. You take it to a mechanic because it's broken. You go to pick it up... One of these scenarios will upset you more than the other.

    1. The mechanic says, we think this was the problem and this is what we did. Bring it back if the problem persists. The car dies on your way home, so you take it back like the mechanic asked.

    2. The mechanic says "we fixed it". The car dies on your way home. You don't take it back to that mechanic. You find a better one. You might even sue the first for money stolen from you.

    The difference was a word. Think about it.
     3 people found this helpful
    Share this post

  2. #2
    Your car has a flat tire and the garage says we think it's the petrol tank and attended to that.

    Your friend says it's a flat tire I fixed it for you but your suspension may be damaged.

    If any issue in an area can be positively identified and rectified, saying it is fixed is a reasonable claim. Adding a modifier that the initial repair may have knock-on effects that may latter affect some other component would also be reasonable.

    If a developer identifies a faulty line of code, script or database entry and rectifies that fault. Claiming it is fixed is reasonable. Given the interaction of such, knock-on effects may be a consequence.
    Share this post

  3. #3
    hyper---sniper's Avatar Senior Member
    Join Date
    Jan 2014
    Location
    SCOTLAND
    Posts
    2,984
    Originally Posted by Adam_Sanderson Go to original post
    Your car has a flat tire and the garage says we think it's the petrol tank and attended to that.

    Your friend says it's a flat tire I fixed it for you but your suspension may be damaged.

    If any issue in an area can be positively identified and rectified, saying it is fixed is a reasonable claim. Adding a modifier that the initial repair may have knock-on effects that may latter affect some other component would also be reasonable.

    If a developer identifies a faulty line of code, script or database entry and rectifies that fault. Claiming it is fixed is reasonable. Given the interaction of such, knock-on effects may be a consequence.
    Well if i went to a garage with a flat and they said it was my petrol tank , and i drive a diesel , i would not go back to them and would make sure everyone knew what kind of garage they are ,

    So what you are saying is the devs do not know a tyre from a petrol tank .lol you may be correct as they seem to fix the wrong bugs , no wait.. they do not fix they add more..

    I would like a looked at , or in progress , not fixed , as it never is fixed , or when one is fixed more pop up ?... so yes we go round in circles , but most bugs are not bad , just fix the bad ones not , and stop giving priority to bugs that give us a little fun..
     1 people found this helpful
    Share this post

  4. #4
    BioXTC's Avatar Senior Member
    Join Date
    Mar 2019
    Posts
    1,052
    In your car example, it's not the wording that mattered. It's what they did after they discovered whatever they had done hadn't properly fixed it. Same applies to Massive. If a fix doesn't work or breaks something else, then they should own up to it and go back to working on it. Attaching a disclaimer to everything does nothing to fix the problem, it's just window dressing.
    Share this post

  5. #5
    Originally Posted by Adam_Sanderson Go to original post
    Your car has a flat tire and the garage says we think it's the petrol tank and attended to that.

    Your friend says it's a flat tire I fixed it for you but your suspension may be damaged.

    If any issue in an area can be positively identified and rectified, saying it is fixed is a reasonable claim. Adding a modifier that the initial repair may have knock-on effects that may latter affect some other component would also be reasonable.

    If a developer identifies a faulty line of code, script or database entry and rectifies that fault. Claiming it is fixed is reasonable. Given the interaction of such, knock-on effects may be a consequence.
    What?
    Share this post

  6. #6
    Oatiecrumble's Avatar Senior Member
    Join Date
    Jan 2016
    Location
    London
    Posts
    4,850
    Originally Posted by mckrackin5324 Go to original post
    What?
    His always replying like that, very confusing but at the same time very interesting to read....
     1 people found this helpful
    Share this post

  7. #7
    Originally Posted by mckrackin5324 Go to original post
    Imagine it as if it were your car. You take it to a mechanic because it's broken. .
    I am an OS/infrastructure engineer. We use car analogies all the time, mostly because cars are the sum total of many components working together. However, your analogy doesn't apply. You are not taking your PC or console to a Massive developer for him to examine. It doesn't matter that you think you have the same PC or the same console as someone else or that your "specs" are correct or meet the requirements.

    When you tell a developer something is wrong with your program (game in this case) if they can't look in your system, they have to look in theirs. And if what you say is broken in your system is not broken in theirs, they have to break theirs to reproduce your error. And it may be that they can reproduce your error, but the way they broke their system, is not what's broken in yours.

    You want a car analogy? 2 people can each buy a car that is exactly the same as the other. Within a day, something will be different between the 2 cars. And every day that goes by, the cars will become more and more different.

    You are probably thinking about big changes like wheels, tires, etc. But no. If one driver sets the radio to 75.5 FM and the other to 100 FM, that's a difference. One drives 10 miles home, the other 20, that's a difference. Speaking in terms of cars, those differences are negligible. Change a comma to a semicolon in code, see what happens. One system running a program sharing resources with other programs vs a system running a program not sharing resources, that's 2 different environments.
     1 people found this helpful
    Share this post

  8. #8
    Aced_100's Avatar Senior Member
    Join Date
    Aug 2020
    Location
    Melbourne, Australia
    Posts
    532
    Originally Posted by III_Hammer_III Go to original post
    When you tell a developer something is wrong with your program (game in this case) if they can't look in your system, they have to look in theirs. And if what you say is broken in your system is not broken in theirs, they have to break theirs to reproduce your error. And it may be that they can reproduce your error, but the way they broke their system, is not what's broken in yours.
    That may be the case for PC's with their myriad of different components, my PS4 though should act the same as other PS4's, and if people complain about the same problem it's most likely the game not the console. And it would be much much much easier to work it out on a PS4 for example.
    Share this post

  9. #9
    Adze.'s Avatar Senior Member
    Join Date
    Jun 2016
    Posts
    1,005
    Originally Posted by Adam_Sanderson Go to original post



    If a developer identifies a faulty line of code, script or database entry and rectifies that fault. Claiming it is fixed is reasonable. Given the interaction of such, knock-on effects may be a consequence.
    A D M the wh9-le p0in.t of f1xi ng somt ing is n at to ard m0o.re bug-g-s... surely?

    Or should I say

    01110100 01101000 01100101 00100000 01110111 01101000 01101111 01101100 01100101 00100000 01110000 01101111 01101001 01101110 01110100 00100000 01101111 01100110 00100000 01100110 01101001 01111000 01101001 01101110 01100111 00100000 01110011 01101111 01101101 01100101 01110100 01101000 01101001 01101110 01100111 00100000 01101001 01110011 00100000 01101110 01101111 01110100 00100000 01110100 01101111 00100000 01100001 01100100 01100100 00100000 01101101 01101111 01110010 01100101 00100000 01100010 01110101 01100111 01110011 00100000 01110011 01110101 01110010 01100101 01101100 01111001 00111111

    LOL
    Share this post

  10. #10
    dagrommit's Avatar Senior Member
    Join Date
    Jan 2003
    Location
    Pedestal of truth
    Posts
    5,099
    Originally Posted by Aced_100 Go to original post
    That may be the case for PC's with their myriad of different components, my PS4 though should act the same as other PS4's, and if people complain about the same problem it's most likely the game not the console. And it would be much much much easier to work it out on a PS4 for example.
    There are three different PS4 models. Each of which could be running different system software from yours. Your PS4 may also be operating under different environmental conditions, thus affecting its performance.

    And that's before you get into bugs with the game itself, where many factors can affect the state of your game world vs someone else's.

    Originally Posted by mckrackin5324 Go to original post
    I can respect you saying "we're trying" or "we're working on it". If you say you "fixed" an issue, that means the issue no longer exists (for anybody). That never happens. Ever.
    Anyone who's ever developed or tested software for a living is laughing at this comment.

    And before someone else inevitably claims Div 2 is the buggiest game ever: https://www.rockpapershotgun.com/202...lorant-update/
    Share this post