{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/13/2018 11:08:07 AM
2
Yep! And to all the whiners "I paid for the game blah blah blah, it's broken blah blah boohoo", WOW goes through months of beta test and releases with bugs! It's -blam!-ing normal, and if you don't think so then I invite you to write this much code and have it bug free!
English
-
Go play your broken game fella instead of talking trash.
-
They added complex changes to a simple Daily vs Weekly reset system and didn't test them properly. The changes fell at the first hurdle. It is absolutely Bungies's fault, a major error and that is why they are fixing it ASAP
-
It beggars belief that they didn’t find these problems when they tested it. Oh wait a minute they didn’t test as they leave that to the player base to find the problems as usual.
-
I never said it wasn't bungies fault. I said no matter what it is, something with this much code is going to have bugs! Even if you spend months testing as I already pointed out! Again, I invite you to write millions of lines of code and have it bug free!
-
Edited by GrayWulf25: 9/13/2018 11:45:04 AMIt isn't writing millions of lines of code from scratch though. It is specific incremental changes to an existing code base. Each area of change should have a test plan. If you are changing the reset system then you have to test that over a number of weeks in a UAT environment. The fact it failed in the first week of release strongly suggests it wasn't tested to any degree, or the testers are incompetent
-
@GrayWolf I've made a game before, and I can easily say that it's not any easier to work from existing code, even if it was made from you. The job is just as hard as the first time around unless there is a repetitive nature to the task, such as making a carbon copy of an item with only name changes. There's always going to be bugs and the testing is always done. That's why the game doesn't crash when the dlc drops and why it isn't a broken mess. The problem is that Bungie is working off of extremely old code that they made at the beginning of the game. You can try making an update this size and not having any problems with your code while working off of something you haven't touched in 2 years. The changes were also complete overhauls to the entire system, which is similar to making it from scratch so your argument becomes invalid.
-
Firstly. Bungie has been making games for decades. They should know what they are doing. Secondly. I think you should ask them for a job. Thirdly. The game is still broken.
-
The code changes over time. Java 9 is a complete change from Java 8 for the module system that they implemented. There are multiple classes that are new and multiple that have been deprecated for the fact of the new classes handling the same tasks more efficiently or just doing something else that is more used.
-
I'm a professional software engineer and have worked in the games industry for...lets just say, a large US games publisher. I've developed 3D games myself using Unity and C# The entire purpose of object-oriented coding on which most games are based is [b]reusability[/b]. We don't re-invent the wheel and start from scratch. We refactor existing code and extend existing classes to make it all much easier. My argument is pretty simple and not in anyway invalid. They changed the reset system to have some complicated soft resets that were not quite daily or weekly, and they failed. Big issues that you would expect any kind of rudimentary testing to find. That's it.
-
I know that Object-oriented is about reusability, it was the first thing I noticed when I taught myself and learned extensions. The point I was making was that they practically remade their system for resets and the bugs are entirely expected for the first week. My opinion on their decision is that they made a good improvement for the game by adding rolling resets. The code did have to be changed drastically to allow them to add the rolling resets though, which makes the point of my first comment still valid. Although on the other points brought up by the community, the change to infusion was a complete blindside, which tbh is a bad idea with the change to their drop rates, and the exotic drop rate change was needed, although they went too far by removing the three of coins, which was perfectly balanced for the game as it was.
-
The reset bugs were not “expected for week one” that is a ridiculous statement. Professional studios have teams of testers. The changes should be unit tested and integration tested and finally QA tested to avoid disasters like this
-
@GrayWolf If you work as a software engineer you should know that testing environments are completely different from actual working environments for different platforms. The test environments are completely controlled to pose minimal problems with the code for the programmers, but working environments aren't as controlled. I ran into the problem with my coding when I tried creating an exported version of my game. The exported version didn't run as well and had many bugs that weren't in the test environment of Eclipse. There's a world's difference between actual use and testing. I personally expected the reset glitch to happen, mostly because of the new UI changes, and the fact that they reworked the resets. There was bound to be some error between the changes.
-
And as for the test teams, not every company will have the same funding for their testing. I would expect a large portion of the budget for Destiny and Destiny 2 went into their graphics and the upkeep on their servers. They probably wouldn't have 3 or 4 teams to do testing on their game, and give feedback. Also not to mention that they do still have the time constraints to work with, which would also require the testers to give immediate feedback for the entire thing unless they finished very far in advance.
-
Hahahahaha are they still using a Spectrum Sinclair system. Keep defending a broken game.
