Wow omg in a beta theres a glitch that needs to be noted and fixed...Its almost like this is exactly the sort of issue beta's are designed for...-_-
English
-
Ever hear of testers before a beta? Guess not
-
too bad bungie never even fixed their first game over 3 years of play; and that this glitch was an old glitch that existed in the last game that they patched, but then left in the new game
-
LET'S BURN EVERYTHING
-
Go and learn how to code a game then realise how you inputting 1 line of new code can make 10 glitches, the fact they've changed so much about D2 and got so few actual glitches let alone a glitch that they should know how to fix is something you should be thankful for more than complaining its a repeated like its something obviously preventable.
-
they get paid to do this mistakes, especially old mistakes, are not a pass this franchise has been on the drawing board for 11 years; to have massive, completely game breaking glitches at this stage is laughable, which it is, especially an already known glitch from D1 returning
-
-_- you really are clueless...so in your mind when you have to work or in school and get told you have to have a piece of work ready by a certain deadline but you have to get a draft in of your work a week before that deadline, that draft is 100% perfect with no mistakes...-_- Dont be an idiot. And as i explained yes it is an old glitch HOWEVER it has been created by a NEW piece of code which makes it a different issue to tackle than someone just going oh this didnt work in D1 but im sure it will in D2. Its bascially D1, x is creating glitch y D2 change new loadout, z is now creating glitch y. Yes it is an old glitch but its being created by something new so its not an old mistake its a old glitch from a new issue -_-. Again learn how to code and you'll realise how lines of code can cause issues in totally unrelated area's to the ones your coding.
-
1.) When my teacher assigns me homework and I have 3 1/2 years to complete it, and then asks for a draft 1 month before it's due? -blam!- yes! I absolutely demand it have no errors!! Especially errors that refute the entire balance of the assignment. (You're an idiot, kupo.) 2.) You entirely just made that up out of thin air. It uses the mount/activation loop to keep the super in eternal animation and effect. There is absolutely no code difference other than in this build they left the previous patch out. That's how he figured it out so fast. It's old. 3.) I don't have to know how to code a game to expect a franchise leader who was paid over a half a billion dollars to do the job right, to have a proper finished job. They aren't Joe and the Amateurs in your momma's basement, they are -blam!-ing Bungie Studios.
-
Bungie has already stated their engine is extremely hard to work with. On top of that, a small mistake in any type of code will disrupt the code and produce error messages.
-
Millions of dollars, should invest in a better engine
-
1. Your moronic considering you dont know how to code a game yet think 3 years means it shouldnt have any errors...You do know games like COD have 3 studios working on a game once every 3 years just to get a game out that works let alone doesnt have any glitches in it -_- Games take more than 3 years to develop and build let alone test and fix any issues. There will be glitches and issues going into the next year because its not as simple as 'oh i added 2 rather than subtracted my bad' 2. AS I SAID ITS NOT ABOUT THE FACT ITS AN OLD GLITCH ITS NEW LINES OF CODE MESSING UP OLD LINES! Lets put it in simpler terms for you and take a kids game like minecraft then you might understand. Minecraft is constantly updated, in a recent updated a few months back they added 64 new blocks to the game, plan blocks nothing fancy all that needs is a seperate line of code surely. Those new lines of code for the blocks caused glitches for example of enemies not dropping their loot.......What does that have to do with coding for blocks you ask? NOTHING but coding isnt as simple as seperate files on your computer controlling different aspects of the game, its all interlinked, so funnily enough YES 1 new line of code can have the effect of re-introducing an old glitch through different methods, its a really simple concept to understand. You want it really dumbed down then you can have this example, Cause, the PS scratches your disk because the PS is faulty - Result - Game doesnt work. Cause you scratch your disk for the lols - Result - Game doesnt work. See how it can work now, 2 different issues causing same problem old or not. 3. Again knows nothing about coding, expects people to get it perfectly right first time because money solves all issues regardless of skill, problems or time needed to solve everything. You want a perfect game on release? Return every game you ever brought and wait and extra year for the time the developers would have wanted it to come out.
-
Thank you for destroying OP. Dude has no clue