{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
12/10/2015 6:57:47 AM
79
You a coder?
No?
Piss off...
Balancing a weapon vs slapping a "no access unless X is satisfied" requirement is night and day...
Bitching for the sake of bitching....grow the [b]f[/b]uck up and try to pull your head out of your ass. Shit you know nothing about rarely ever is as simple as you assume it could be
English
-
Edited by Rezinihplod: 12/10/2015 5:49:05 PMBalancing Thorn shouldn't have been hard. Just change the variables. You don't know anything about code do you
-
Im coder and you're telling bullshit , shut up you will look smarter
-
You're coder? Then who was house?
-
"Im coder"
-
That's all what your stupid mind saw ...an missing a ... gg madmax
-
[quote]That's all what your stupid mind saw ...an missing a ... gg madmax[/quote] An missing? Gg
-
I think you shouldn't be using "stupid" as an insult.
-
-
You obviously don't know how coding works. Learn how to get your facts straight noob.
-
Riot Games puts out balancing patches every two weeks. No excuse for Bungie not to have had things balanced before TDB.
-
Riot games is also not developing anything new, you know, like an entirely new sequel. League of Legends was the same 10 years ago as it will be 10 years from now. All they have is new characters every so often and balancing on those new characters they introduce. Poor comparison.
-
Oh sorry, forgot. Riot Game. My apologizes.
-
Yeah, no. If Bungie is smart, they'll have a nice little easy to edit XML or CSV for damage calculations. They make their changes and compile it. Then they boot up their pretty Sandbox and test their heart out. If you think that's harder than adding a boolean with fail safes and testing it, you haven't done much programming.
-
I know nothing of programming and this reply being on the same side of the argument as I am turned me on. You the real MvP
-
I bet you're good with children. Please don't have any when you grow up.
-
If it's so easy to add in, why didn't they do it before the update release then?
-
Probabltly because they didn't know it was going to happen. They aren't just gonna allow a bug in the game just for the sake of it
-
I know, just playing devils advocate, it's not as if it was the only thing released in the update, small bugs are bound to get through.
-
Edited by H1jAcK: 12/10/2015 8:53:49 AM[b][i]Tinfoil Hats at the Ready![/i][/b] Or did they? Maybe their goal was to let this knowledge leak, have people steal some items and like them, then make their only option to keep those items be to pay up. Kind of a teaser situation, but way more underhanded. Okay, you can take your hats off.
-
It's a possibility for sure, but I hope that's not the case. Either way, I won't blame them for putting in this patch quickly.
-
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.
-
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.
-
