Indie Dev Rami Ismail describes the console authentication process

Please stop the discourse completely

Just explain. Sony and Microsoft are not responsible for the status of Cyberpunk 2077 on PS4 and Xbox. The “certificate” does not guarantee that the game is “excellent”. We guarantee that the game will not brick it or disable important features.

Currently, industry contracts prohibit talking about the certification process and requirements for a particular platform, so let’s take a look at the general process and concept of “certification”.

Certification does not mean that the game is free of graphic bugs, performance issues, glitches, or that the game is functioning properly. A certificate means that the game must not undermine the console or its ability to use the console, or break rules or trademarks.

Certification includes “Do not show important things off screen”, “Display warning when internet connection is lost”, “Display correct button label”, “Game can be played even if the controller is unplugged and unplugged” Make sure it doesn’t crash. ” “-Something like that.

Certifications are not “textures pop up 5 seconds behind”, “objects are floating”, “game is glitchy, my character is T-posing from the car roof without pants”. It has nothing to do with the certificate, and even if it appears in the certificate, it’s not the job of the certificate.

Authentication as a process is a huge (GIANT!) List of accessible rules and considerations. Submit the game and (a) wait a week to get a list of failed criteria. If the test finds a large number of failed criteria, it may stop the test prematurely and return a partial list.

Then you have the opportunity to fix the problem or request an “exemption”. Generally, the submission process cannot continue unless all test criteria are marked as PASS or WAIVED on the backend.

When it comes to “waivers,” developers basically argue why they believe it is fair to exclude them from the requirements. The platform then agrees or disagrees depending on the game, the situation, and the urgency of clearing the certificate, and the developer’s promise of fix fails with the patch (Day 1).

In some cases, you may find that what you can get an exemption is counterintuitive. Example: Correctly labeling a button is a proof that will definitely fail 100% (as far as I can see)-some might argue that it’s not so important for the game to use a proprietary language. But that’s right.

Anyway-then you submit again and the certificate checks against the huge list of rules again, but skips testing the rules you got “exempt”. If everything is clear, you have the ability to set a release date and you’re ready to go. It also passes the patch certificate.

(It’s all through the worst interface I’ve ever seen in my life. There are no exceptions. The 1980s DOS interface is controlled by ambiguous key combinations that are easy to navigate. Large studios have specialists in managing these release processes.)

The generalized authentication process is described above, but that doesn’t mean it’s almost irrelevant in this case. After all, certificates are a way to prevent the console from bricking, but the game publisher is solely responsible for the quality of the game.

If you’re creating a game where there are too many bugs and the character takes a T-pose and you’re flying naked in the sky while everything explodes at once, the only way to proceed is for the NPCs you need to talk to exactly their own. Hope it’s thrown in the way-but that’s all the certificate rules, it passes the certificate.

After that, it’s up to the publisher to say, “OK, ok, I’ve met all the certification requirements, but the current state of the game does not guarantee launch. It must be delayed or canceled.” They fix things and pass the certificate again.

The platform does not have the magic of “this does not comply with our quality standards”. We do not “approve” that the game is good. It’s up to the publisher to decide whether to shoot for themselves. At your feet with the launch of an extraordinary project.

So what I’m saying is that Cyberpunk 2077 isn’t responsible for being on the platform for “sign-off”.Responsibility lies solely with the person who decides to publish and launch, and the person who participated in that decision-not the developer, QA, certificate, platform.

that’s all. The discourse continues.

Back to top button