{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
12/10/2015 7:38:35 AM
7
I am a [b]software engineer[/b] ([i]programmer[/i] will do) and I will tell you straight-up the word "coder" is an insult.
Fixing the book is actually more difficult than balancing weapons.
To fix the book you have to add a check to the book (a bool) to see if the player bought it. That's simple enough but you also have to add that same check to the actual player's account. That's the bit that gets complicated. You can't just throw in "HasBoughtSRLBookOne=1" when someone ponies up the micro-transaction. You have to add the functionality to buy the book, store the purchase on the account, put in redundancies in case of power/communications loss (but that has to be stored in an encrypted file with a redundant hash so someone couldn't just sign off line, add that bit of code, and sign on). You also have to define the various variables. All in all, given the state of the code (Bungie admits it's sloppy) you are looking at a lot of bugs.
To balance weapons it depends on how far ahead Bungie thought. If they were smart all the weapon stats are in an XML document and they just have to modify those and rebuild. If they were idiots they'd have to find the instances where the values are defined, modify, and rebuild.
Weapon balancing software side is easy; adding a whole new feature like this book is not.
English
-
To be fair, Bungie had significant motivation to fix something that directly effects their bottom line, so they would likely put a lot of effort into that (they could easily justify paying overtime or bonuses if doing so makes the company far more money). With a weapon patch, they don't have as much to gain with an immediate fix. There's also the fear that messing with guns could have a negative outcome in terms of balance. Since they don't have an obvious financial reason to make a change quickly, they will naturally take their time to be sure that their fix is "the right" fix. So it's likely less about the actual coding, and more about feeling okay about taking their time testing something before rolling out any weapon changes. They are also focused on new development, but likely dropped that temporarily to fix something that hurts their pocket books. Quite frankly it's a business decision on where to allocate resources. I can't think of many businesses that wouldn't have all hands on deck to fix something that could cost the company an enormous amount of income. Or perhaps this: (Warning, do not click if you love Bungie) [spoiler]Another sketchier possibility is that the free books were planned and not a mistake at all, and they had a "update patch" premade before releasing the initial December update. They could have done this in hopes of getting some people who wouldn't have bought the book initially to buy it after getting the rewards. I hope that's not the case, but it is a possibility. It also would explain how they were able to "fix" it so rapidly. [/spoiler]
-
It's funny how most are ignoring your argument. Those desticles are quiet now.
-
Meh, most of the kids on these boards are under 16 and think "video game coder" is an actual job. I probably destroyed a few dreams with that post.
-
-
A lot of their weapon balancing patches rely on gathering data from crucible. That is why it takes so long, not a programming constraint.
-
-blam!- out of here you ain't no programmer and I'm sure everything you said is bullshit. Fixing the book is harder than balancing weapons? You expect anyone with half a brain to believe that?
-
Edited by Xuh: 12/10/2015 2:18:10 PMAnd I don't really know if people should listen to you if your status is "I'll leave your mfing bitch naked."
-
I don't see what my status has to do with the content of my post?
-
Because you're acting like you know quite a bit about coding. I'm just pointing out how your status points makes what you're saying less believable.
-
All you need is common sense to know what he said is bs
-
Really mate, how is that? What does "common sense" prove to you that I'm talking "bs"?
-
Probably the fact that you're trying to tell us that weapon rebalancing is easier than changing one simple thing. It's pretty obvious you either straight up lying or bending the truth to fit your stance
-
Edited by VisageOfAnAngel: 12/10/2015 6:12:41 PMWeapon balancing is changing one simple thing (XML file(s) with weapon stats). Properly implementing a fix to the book requires many, many things which I have detailed in the prior post. You are just some little kid trying to act cool. Bugger off now.
-
I'm the little kid trying to look cool? Your shit tier lies are only surpassed by your shit tier name calling. Give me one good reason if it only takes five minutes to Blaine everything like you say then why didn't bungie do it? Why would they prolong it. I'll wait for your obviously bullshit response
-
That's true. I'm trying to be neutral with it. [spoiler]I'm just more or less stating my opinion, and I just wanted to point out how the status just changes the believability of what you're positing.[/spoiler]
-
It is harder.
-
Edited by Chit Chat: 12/10/2015 12:24:55 PMNice. However I was under the impression that they wanted to patch things all at once which is why it took so long. It was a huge patch after all. Also assuming they were working on parts of TTK as well. They did apologize for it and said that patches will be more regular now. Especially with the live team because they smooth out the process of approving such changes and it's more streamlined now. So maybe the code wasn't the issue, but the testing and approval process slowed things down. I just find it hard to believe that people really think Bungie employees go to work everyday to just sit on their bums lol. They're always working on something.
-
Ok I'll agree that changing global weapons values and single weapon values is much easier. However testing the changes is a much longer process than testing if the book works.
-
Not really, testing the changes is rather simplistic. There'd be a debug mode in the game for development. This can range from something as complex as floating damage markers like RPGs use or a few lines in the GUI all the way to a simple log that gets output and read after the fact. The code for weapon damage works, balancing them is just quite literally changing numbers. Sure, it may be a lot of trial and error but it's not complicated and not anywhere near as time consuming as adding in an entirely new network feature.
-
It's easy but takes a long time. Checking if a payment was successfully is just checking it works, checking if everything is balanced is a longer process. Seen plenty of games where they boost a stay (in this example magic attack) didn't fully test it and mate became the meta.
-
[quote]Checking if a payment was successfully is just checking it works[/quote]Obviously you ignored the entirety of the third paragraph.
-
That implies bungie tested the OP pulse rifles we have now which means either they don't test shit or they're ok with imbalanced guns Either way, it's shit
-
And if they do test the weapons are those tests performed against real life players or bots.
-
Exactly. Kids have no idea what they're talking about. Good post.
