Cheat Engine

[AylinCE]

Saying goodbye to Flash in Chrome

Today, Adobe announced its plans to stop supporting Flash at the end of 2020.

For 20 years, Flash has helped shape the way that you play games, watch videos and run applications on the web. But over the last few years, Flash has become less common. Three years ago, 80 percent of desktop Chrome users visited a site with Flash each day. Today usage is only 17 percent and continues to decline.

This trend reveals that sites are migrating to open web technologies, which are faster and more power-efficient than Flash. They’re also more secure, so you can be safer while shopping, banking, or reading sensitive documents. They also work on both mobile and desktop, so you can visit your favorite site anywhere.

These open web technologies became the default experience for Chrome late last year when sites started needing to ask your permission to run Flash. Chrome will continue phasing out Flash over the next few years, first by asking for your permission to run Flash in more situations, and eventually disabling it by default. We will remove Flash completely from Chrome toward the end of 2020.

If you regularly visit a site that uses Flash today, you may be wondering how this affects you. If the site migrates to open web standards, you shouldn’t notice much difference except that you'll no longer see prompts to run Flash on that site. If the site continues to use Flash, and you give the site permission to run Flash, it will work through the end of 2020.

It’s taken a lot of close work with Adobe, other browsers, and major publishers to make sure the web is ready to be Flash-free. We’re supportive of Adobe’s announcement today, and we look forward to working with everyone to make the web even better.

POSTED IN: CHROME

=======================================
https://www.blog.google/products/chrome/saying-goodbye-flash-chrome/
=======================================


Flash Hackers will enter a new era.
Is this an end, or a beginning,
We'il see it soon.

Adobe stopped production of 64-bit Flash Player.
Currently it only produces 32 bit Flash Player.

However, in 32-bit browsers, for some games,
With the "Java memory leak", the game fails to load.

Game companies are gradually leaving the Flash infrastructure.
OpenGL is becoming widespread.

We will see the progress together.
Or: How the Cheat Engine will handle this process.

"End Flash Player"

[atom0s]

Not sure if you noticed, that blog post was from 2017. This has been an on-going thing for a while now to discontinue Flash due to the constant flaws and security holes/risks it has. HTML5 was being made to replace it and bring similar functionality to the browser with much better security.

In terms of what it means, just means that hacking games on the browser will shift from altering Flash files/variables to hacking Javascript instead. (Much easier anyway.) Means nothing for Cheat Engine since it doesn't affect or directly relate to it at all.

Further technologies are being developed as well to do more in-depth things on a browser. For example, WebAssembly will be allowing browsers to run full renderable games and tech from a browser with ease. This is something that we can see replacing HTML5 for gaming sooner or later with the depth and control it allows to be used for rendering since it uses (currently) OpenGL.

[AylinCE]

This is a very powerful and reassuring comment.
Thanks for your support @atom0s ..

But, I still can't reach:
For example, in OpenGL, WebGL or HTML5, SWF files.
It's like, Game servers are moving away.

Hopefully, OpenGL, WebGL or HTML5
removers (Decompiler) will be produced.

[atom0s]

Game servers aren't going anywhere. New tech doesn't mean less features or removal of things like servers. The current web stack of tools includes things such as web sockets as well as requests in general. A game can make a full connection to a server via a web socket, or it can do manual requesting as needed as if it were just any other AJAX/JavaScript based thing.

You can see this kind of stuff in action/example here:
https://www.websocket.org/echo.html

A lot of games use this already for their various types of clients, including existing Flash games that also support a desktop app version of their client or an HTML5/JavaScript rewrite.

WebAssembly is also able to do network connections as needed to connect to a server based on web sockets in the same manner. WebAssembly allows the loaded modules to talk to the browsers API layer (ie. it's script engine like Chromes v8 JavaScript scripting etc.) which gives it access to said web sockets. So in the same regard, a game made with WebAssembly can also connect to a server the same way as that example I linked above. Just with a little different coding to bind and wrap the connection between the different layers and tech.

[Corroder]

[AylinCE]

I follow the Corroder, he dominated road to SWF.
But @ atom0s, your information is very deep.
Great ,, you tell by examining all the details.

Thanks for this lighting and your encouragement.