What Did Kabam change in 8 hours?
JT_Wrexz26
Member Posts: 57 ★
Do we get no Notes or anything letting us know what ya'll did for the 8 hours the game was down? Is it a secret? It seems to me like nothing changed? Moon Knight, Black widow and other Evade champs still seem to be evading WAY more than they should.... my specials are still being Blocked after finishing with a Medium attack (which is very... very annoying). I still lag REALLY BAD when my alliance hits the help button for me while im grinding arenas? So what exactly did ya'll change for 8 hours??
3
Comments
Or they could, you know, maintain their servers and change whatever hardware needed to be changed.
That's what maintenances are for.
If they need to change something in the codes, that would be updates.
yup several people have said it as well ...i mean its kinda self explanatory in a way ..
I think most of the people there were hackers if im not mistaken?
And I heard they installed a slightly larger wheel.
hacker ? lol
i think This has been due to sanctions
They are not able to cope with the government ...
oh ok i just was unsure why they did it thanks for the good info
In simple terms, it is time consuming process and a lot can go wrong during these refreshes. I bet we all want to play the game, but it does need timely maintenance to be running as expected.
I have worked in Game Dev for nearly 15 years, here is something you may be missing.
In regards to MCOC...
Maintenance is for Server Maintenance.
Bugs that cannot be fixed on the server side are fixed (as much as possible) in the monthly patch / update.
I encourage everybody to ignore the original post and stay in school kids.
If you are taking some sort of game design courses, find someone on the faculty that has worked in the industry and ask them if developers *ever* touch the live servers.
You don't fix bugs during maintenance, because you don't touch anything during maintenance. Programmers fix bugs Monday through Friday during their normal work day on development systems. They also add new features to the software, again on dev systems. At some point they freeze changes on dev and get it ready for deployment. They are supposed to test it and verify it is production ready. And then they make a deployment package for the software and go home. That's it: the developers involvement ends.
The package gets sent to operations where they push that unto the production systems during maintenance windows where they shut everything down, push the updates, and then bring everything back up. The ops people are not generally developers, and in any case they have no authority or access to the game code. They put the packages in the deployment directories and hit the button. Then they start everything back up, make sure things appear to be running correctly, and go back to playing Halo in their offices.
This separation between dev and ops is pretty much the standard in large scale multiplayer gaming systems. Developers don't get to touch the live systems, so they can't "fix" anything on them. They basically fix bugs as part of making version 17 of the software, and the only way they fix problems in the game is by giving someone version 17 and telling them to overwrite version 16 with it. That's all they are allowed to do.
Why they do is is another long story that I'm sure the faculty can explain to you.
Also, if you are taking classes in "game programming" *and* design, good luck to you. Almost nobody actually does both except one man indy shops. And its rough out there.