Not all Flash media is the same. You see, the interactivity in Flash relies on a language called ActionScript. In 2006, ActionScript 3 came out with new features. Alas it was backwards-incompatible with AS2 and so not everyone was to keen on it. It wasn’t until the release of Flash Professional CC (2013), that authors were required to switch to AS3.

This has made Flash emulation quite a challenge. Understandably, Flash emulators have had to choose between prioritising AS2 and 3. For example the emulator Shumway focussed on AS2 (with some AS3 support) and Lightspark focussed on AS3. Unfortunately, Shumway hasn’t been updated in ages and Lightspark isn’t browser-based.

On the other hand, Ruffle, a relative newcomer to the Flash emulation scene has been picking up speed. Written in Rust and sporting WebAssembly, it runs wicked fast and cross-platform! Though Rust’s focus has too been mostly in one direction, namely AS2, they have started to make progress on AS3 well. Below is an abridged version of an announcement shared on the Ruffle Discord Server by our friend Nosamu.

The first few ActionScript 3 games are finally playable in Ruffle, Demos below! One of the first fully-playable games is Not To Scale, a simple but clever photo puzzle! You can try it out right now on Newgrounds: https://www.newgrounds.com/portal/view/575849/format/flash?emulate=flash

Even more exciting, the beautiful minigolf game Wonderputt is now mostly playable with the Ruffle desktop app! The first hole is quite tricky due to collision bugs, but a fix is in progress, along with web performance improvements.

Watch our #announcements channel for updates in the coming weeks! As always, you can download Ruffle from https://ruffle.rs/#downloads.

But wait, there’s more – Ruffle web builds now have a fancy loading animation! If you own a website, now is the perfect time to update Ruffle! No longer will your visitors be greeted with a blank white screen while waiting for Ruffle to load. Check out the animation:

Also, if you’d like to add your own flair to the loading screen or disable it altogether, there are a few customization options: preloader, --preloader-background, and --logo-display. For more information, see our wiki.

And finally, we’re looking for help developing an official Ruffle app for Android! If you have experience with Rust development targeting Android, please check out @szőlő’s WIP repository: https://github.com/torokati44/ruffle-android and join the development thread: Native Android App.

Do you have a favorite Flash game you just wish you could play right now? It’s not emulation, but Bluemaxima’s Flashpoint collection might be able to run what you are looking for right now. Be sure to also check out our Flash Player Emergency kit for more tips on Flash after its end-of-life.

Kicking things off, Flash speedrunners Conor and Slush Puppy are hosting Flash Marathon 5: Revival of Flash this Saturday (February 20 at 13:00 UTC) at ttv/flashmarathon! The marathon will feature classics such as Cat Mario, Henry Stickmin: Fleeing the Complex and Papa’s Hot Doggeria.

A full list of games can be found on the marathon schedule available at: https://horaro.org/flashmarathon5/schedule. Also pay their Discord Server a visit while you are at it!

In other news, Flash Forward Jam has been extended into February. The goal of the jam is to make a game or (interactive) movie in Flash, to showcase Ruffle‘s emulation capabilities.

Tom Fulp himself recently submitted an entry together with a few other Newgrounds veterans. It’s called Drop Cannon and is probably the most unconventional matching game you haven’t played yet.

Speaking of game jams, one jam has recently concluded: Grow-On Jam, a jam dedicated to Grow series creator On Nakayama (EYEZMAZE). Although none of the games submitted were actually made in Flash, they were all themed around On Nakayama’s games.

Welcome to Grow-ON Jam, a celebration of the work of indie veteran developer On Nakayama (ON/EYEZMAZE), notable creator of the GROW series of Flash and mobile titles. Over twenty years ON has published dozens of freely available titles to a wide audience, and founded a unique genre of gentle games with layered progression systems.

If you’re feeling nostalgic after playing through all the submissions, you might also want to visit the jam’s Discord Server.

The jam has also brought attention to On Nakayama’s poor health, which has led to him requiring a heart surgery in 2019, which he is still recovering from. The good news is that things seem to be getting better for him based on recent Tweets.

Want to play through the original Grow games, but can’t run Flash? Check out the Flash Player Emergency Kit for tips and info on how to run Flash files post-EOL!

Many members of the Flash community have come up with workarounds to continue to run .swf files in the post-EOL era. Read on to find a workaround that best suits you!

Do you still use Flash Player? Data Horde is conducting a survey to see how frequently people continue to use Flash Player even at the very end of its lifespan. It would mean a lot to us if you could spare 5-10 minutes to complete a very short survey.

Emulation:

It’s still possible to run Flash Media (.swf files) without actually using Flash Player. Two mature Flash Player emulators are Ruffle (ActionScript 1&2) and Lightspark (ActionScript 3). Ruffle even has an online demo if you’d like to see it in action before installing.

You can find a more thorough list of emulators in the Flash Player Emergency Kit.

Chrome Flags:

If you’re using any version of Google Chrome, up to and including Google Chrome 87, you might not have to install anything at all! You should be able to continue to use an older version of Flash Player which was immune to the effects of the EOL Killswitch.

Simply run Chrome with the --allow-outdated-plugins flag:

# On Windows:
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --allow-outdated-plugins

# On Mac:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --allow-outdated-plugins

# On Linux
google-chrome --allow-outdated-plugins

# For instructions on how to specify flags on other systems see http://www.chromium.org/developers/how-tos/run-chromium-with-flags

Downgraded Firefox:

In addition to the EOL killswitch, Adobe have gone out of their way to remove downloads for previous versions of Flash Player from their website. That being said, there are ways to acquire a past versions of Flash Player, immune to the EOL killswitch.

An out-of-the-box solution is to install Waterfox, a modern fork of Firefox which also supports a lot of legacy features including Flash Player. Another option is Basilisk, up to version 2020.11.25 anyway.

If you would rather stick to a more traditional approach, u/Cifra85 made a Reddit post on how to install a portable Firefox Browser which comes bundled with an older version of Flash Player:

If you’re concerned about incompatibility, another option is Firefox 78 ESR (Extended Support Release) which will continue receiving updates until September of this year.

Modify Configuration File:

Edit:

Adobe has made it no secret that they intend to offer a killswitch workaround for enterprise customers, via their partner HARMAN, starting February. Leave it to the online Flash community to discover it in January!

Edit 5 May 2021: Consider installing FlashPatch, a tool which greatly simplifies the steps described below.

Spider, an Adventure Quest fanatic, was one of the first people to discover that all it took was a couple of modifications to a configuration file!

If you’re not on Windows, mms.cfg goes in /Library/Application Support/Macromedia on Mac and /etc/adobe/ on Linux. For more details on mms.cfg see Flash Player 32’s manual (page 41).

Flash Player Projector:

Using the Flash Player projectors, it’s possible to run .swf’s outside of a browser, with some minor limitations. Strangely projectors for Windows, Mac and Linux have not been removed from from Adobe’s website and are still available.

Flash Player projectors can be downloaded from Adobe’s Flashplayer Debug Downloads Section, and mirrors can be found on the Wayback Machine and the Internet Archive.

Alternative Ways of Running Old Versions of Flash:

Another unique solution is to use the Cloud Browser Puffin, which can render Flash content remotely. Do note that Puffin is not free on every platform.

As a final workaround, you can try running an old version of Flash Player outside of a browser. Although there are a number of third-party archives out there, setting these up can be non-trivial.

Instead we would highly recommend Bluemaxima’s Flashpoint, a Flash game/animation Browser of sorts which comes with a built-in older version of Flash Player.

We hope you were able to find a solution that works for you. If you have any comments or suggestions let us know at [email protected].

Now go on and spread the word! Tell all your friends and family how they can continue to use Flash Player even in 2021!

Even with Adobe having recently ended support for Flash Player, Newgrounds and many other websites want to preserve the tradition of Flash development and media, hence the name Flash Forward, a look into Flash’s future. This jam challenges game devs to develop a Flash game (or interactive movie), in 2021, long after Flash’s heyday.

The good news is that there are still tools for developing Flash media, such as HaxeFlixel which supports .swf exports, and Flash Player emulators such as Ruffle.

Here’s the rules:

• Make something interactive with Flash, either a game or interactive movie, which could include an animation collab with a cool menu interface, or something with decisions / alternate endings.

• Make it with ActionScript 2 and confirm it works via Ruffle before publishing. You will see a “Test with Ruffle” link on your preview page. Ruffle is what we use to run Flash on NG without the Flash plugin, you can read more about it below!

• Upload any time in January and tag it “Flash-Forward-Jam” to participate!

The jam will have three award categories:

• Game (Top 7 Ranked), with a grand prize of $700 and an interview with Newground’s own TheInterviewer.
• Movie with Interactive Element (Top 3 Ranked), with a grand prize of $200 and an interview with TheInterviewer.
• Best Mobile-Friendly Entry (Game or Movie), a $100 prize for the entry which works best on a smartphone, it wouldn’t be Flash Forward without overcoming some demons after all!

For more details see: https://www.newgrounds.com/bbs/topic/1460728

Good luck and Flash on!

Do you still use Flash Player? Data Horde is conducting a survey to see how frequently people continue to use Flash Player even at the very end of its lifespan. It would mean a lot to us if you could spare 5-10 minutes to complete a very short survey.

Contents:

• Why is there a kill switch built into my Flash Player?
• What does the Flash Player kill switch do?
• Browser Support for Flash Player
• Google Chrome
• Mozilla Firefox
• Other Browsers
• Workarounds

Why is there a kill switch built into my Flash Player?

Adobe has decided to retire Flash Player, which means no more updates. Adobe has stated their reasoning behind the inclusion of this kill switch is to “help secure” users, seeing as Flash Player might still have undiscovered security vulnerabilities.

In doing so, Adobe hopes to no longer be liable for any damage caused by vulnerabilities present in Flash Player, by making Flash Player outright unusable. Overkill? Kind of. For more details see Update: 12 Day Grace Period on the Flash Player Killswitch

What does the Flash Player kill switch do?

Here is an in-depth preview of the effects of this kill switch. When accessing Flash content in a web browser, if your system time is set to January 12, 2021, 12:00AM (midnight) or later, Flash content will be replaced with a Flash information button. Note that if you have already loaded Flash content before this time, you will be able to continue viewing it until you reload the webpage in your browser.

While you roll over the widget, it shows a blue outline.

While you left click the widget, it turns blue.

Right clicking still works as normal for a Flash applet.

Clicking the icon opens a new tab to the URL https://www.adobe.com/go/fp, which redirects to https://www.adobe.com/products/flashplayer/end-of-life.html (Adobe’s End-Of-Life info page) as of this writing.

Browser Support

Browsers will also be removing support for the Flash plugin. The following updates are scheduled to remove Flash support in common browsers:

• Chrome 88 (Windows 7, 8.1, 10): 1/19/21
• Firefox 85 (Windows 7, 8.1, 10): 1/26/21
• Edge 88 (Windows 7, 8.1, 10): week of 1/21/21
• Safari 14 (macOS 10.14, 10.15, 10.16/11.0): 9/16/20
• Windows Preinstalled/Internet Explorer/Edge Legacy (Windows 8.1, 10): optional update in early 2021 and recommended a few months later

Most of the browser updates simply drop support for loading the Flash plugin.

The Flash component is fully removed in Chrome 88. Flash Player permissions are removed from site content settings, and clicking on a Flash download link no longer prompts the user to allow Flash (the link functions as a normal).

Chrome Specifics

If a website specifies fallback HTML code, it is displayed.

If a website does not specify fallback HTML code, Chrome 88 replaces Flash components with a message stating “Adobe Flash Player is no longer supported”. Nothing happens when attempting to right click the widget.

Other Chromium-based browsers, including the current versions of Edge, Opera, and Vivaldi are expected to behave similarly.

Chrome also plans to block Flash from loading in previous versions of Chrome by marking the component as outdated (you can view the components manager in Chromium-based browsers at chrome://components).

After loading a page and approving Flash permissions, you will get a message bar similar to this, stating that “Adobe Flash Player was blocked because it is out of date”.

Right-clicking on the Flash widget provides a few options:

Clicking “Update plugin” goes directly to Adobe’s Flash Player End-Of-Life page. Clicking “Learn more” opens the URL https://support.google.com/chrome/?p=ib_outdated_plugin, which redirects to Google’s Flash Player End-Of-Life support article.

After clicking “Update plugin”, returning to the tab with the Flash player widget reveals a new message on the Flash player widget: “When finishes updating, reload the page to activate it” [sic].

As of this writing, the “Run this time” option functions as intended: it allows Flash player to run once, but accessing Flash content after reloading or navigating to another page requires clicking the button again.

Attempting to update the Adobe Flash Player component from Chrome’s component manager at chrome://components reveals no available updates.

This particular method of blocking Flash appears not to be currently active in other Chromium-based browsers at this time.

Note: Loading a custom PPAPI Flash Player DLL through command-line flags to Chrome does not seem to fix the problem, but further testing (including with older and modified versions of Flash) is needed. A sample command would be "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disable-bundled-ppapi-flash --ppapi-flash-path="<path to Flash Player DLL>". Note that you should fully quit any existing instances of Chrome before using this command by entering chrome://quit in the address bar, and that you can verify the command flags and Flash DLL used the current instance of Chrome by visiting chrome://version. Using a custom Flash DLL Flash path seems to cause Chrome to always report the Flash version as 11.2.999.999. Special thanks to @krum110487 and @nosamu from the Flashpoint Discord server for providing this information.

Firefox Specifics

Flash support is also entirely removed in Firefox 85. The plugins manager at about:plugins no longer lists Shockwave Flash, even if it is installed on the system.

In Firefox 85, if a website does not specify fallback HTML code, nothing replaces the Flash widget.

If fallback HTML code is specified, it will be displayed.

While Firefox 85’s lack of warning or user notification of missing Flash content when there is no fallback HTML code may seem weird, it is likely that this behavior follows the HTML standard more closely.

Other Browsers

Internet Explorer and Edge Legacy aren’t expected to exhibit any special behavior for the Flash shutdown, however, on January 12, 2021, Microsoft is expected to release an update to remove the preinstalled Flash player used by those browsers from Windows 8.1 and 10.

Workarounds

The Flash Player kill switch will break your Flash Player, but there are still workarounds to continue to view/interact with Flash Media after January 12!

There are many projects such as Ruffle and Flashpoint to ensure compatibility and preservation of Flash media, so hang onto your .swf’s!

For a thorough list of workarounds and other resources see this page.

Suggestions? Contact [email protected]

Update January 22, 2021: Linked new EOL killswitch workarounds.

Update January 11, 2021: Added screenshots and additional information for Chrome’s interface for marking the Flash Player component as outdated. Added a note that loading a custom Flash Player DLL in Chrome does not seem to prevent the block.

Special thanks to @themadprogramer for expanding the context for the article, adding a video, providing workarounds, and linking related Data Horde content.

Long ago the 3 Books on Nickelodeon’s Avatar: The Last Airbender website provided a comprehensive guide to the world of Avatar, but everything changed when the site was shut down…

As can be seen above, ATLA used to have an interactive encyclopedia of its own in the form of a massive Flash page. Fans of the show could see Aang and his crew’s travels on the world map, with every point representing the location of a particular episode. You could read up on the events, the geography and the history of the world!

But as the years went by, the contents of this compendium have fallen into obscurity. Besides a few screenshots on Avatar Wikia, a less-interactive fanmade archive of the website is still available. The Lost Lore of Avatar Aang is a Tumblr blog contains the entirety of the text entries, and a very good portion of the images from the original website.

With the death of Flash Player upon us, archivists have initiated a hunt to find (or rebuild) a working version of the interactive Flash version of the website.

-Why did we name it Avatar “yield”?

-Well we were trying to muster up an army to force nick to reupload the game!

Actual Conversation on the AYP Discord Server

The team have been collecting and piecing together WayBackMachine snapshots, tracking down mirrors of minigames and are hoping to contact the series creators who were involved in the making of the Avatar website.

They still have a lot to do, before they save anyone. But I believe the Avatar Yield Project can save the World!

If Avatar the Last Airbender meant something to you, or if you’re only a lost media connoisseur, join the team! Click here to join the Avatar Yield Discord Server.

Be sure to also check out the Welcome to Republic City Tumblr archive, which is more or less the Legend of Korra equivalent. (Interactive version mirrored here, also available on Flashpoint)

Do you still use Flash Player? Data Horde is conducting a survey to see how frequently people continue to use Flash Player even at the very end of its lifespan. It would mean a lot to us if you could spare 5-10 minutes to complete a very short survey.

Adobe is retiring Flash Player at the end of December, as you have likely heard. That means ending updates, ending support and unusually removing any and all downloads. What might be news to some readers is that recent updates have introduced a killswitch into Flash Player, which will be used to disable any Flash Player you may have installed prior to the End-Of-Life Date.

Adobe has updated their information page recently, announcing a grace period before the killswitch activates. While the removal of downloads and other End-Of-Life decisions will come into effect on January 1, the killswitch which will block any further use of Flash Player won’t activate until January 12.

Adobe has cited “helping secure users’ systems” as their reasoning:

Why is Adobe blocking Flash content from running in Flash Player beginning January 12, 2021?

Since Adobe is no longer supporting Flash Player after the EOL Date, Adobe will block Flash content from running in Flash Player beginning January 12, 2021 to help secure users’ systems. Flash Player may remain on the user’s system unless the user uninstalls it.

The EOL info page now also keeps track of browsers as they begin dropping Flash Player support, starting with Apple’s Safari.

While it is still disheartening to see that Adobe is determined to kill Flash Player at all costs, it is at least worth appreciating their attempts in making the process more transparent, thus allowing people to adapt accordingly. Here’s hoping the Flashpoint team will make the most out of this bonus time.

Are you adversely affected by the end of Flash Player? Be sure to check out the Flash Player Emergency Kit for useful resources!

It currently boasts over 7 million views and 10 thousand favorites on Newgrounds, has been mirrored on hundreds of sites and has several thousand user generated levels. Suffice to say, the game has had a lasting impact on a lot of people.

As you may know, support for Flash Player comes to an end this December. But the Super Mario 63 community has taken the necessary steps to survive the end of Flash Player. So in honor of Flashcember, here’s a brief history of what SM63 is, was and will be in the near future…

Humble Beginnings

Believe it or not, the inspiration for Super Mario 63 was a fan-made spritesheet of all things. Sprite artist Flare, had edited Mario sprites ripped from Mario and Luigi Superstar Saga to give Mario his water pack F.L.U.D.D., in the style of Super Mario Sunshine. Intrigued, Runouw decided to make a 2D Mario Sunshine of his own. But who was Runouw?

Runouw is not the username of a person, but in fact a team! Twins Robert and Steven Hewitt to be exact. For over a decade, the duo have used the name Runouw to upload games, videos and sprite-art to various websites. Generally for their games, Robert oversaw programming and Steven the art design.

So Runouw got to work to make their own 2D Mario Sunshine and they debuted their first demo titled Super Mario Sunshine 128 in November 2006. Although the inspiration in Super Mario Sunshine was still very much there, Runouw had decided to incorporate mechanics and assets from other Mario games as well. Right from the get-go, the game featured levels from Super Mario 64 and spin-attacks a la Super Mario Galaxy.

Over the course of the next 3 years, this game would evolve into the SM63 we all know and love today. Updates that followed introduced new levels, power-ups and of course, the beloved level-editor. The name was changed to Super Mario 63 in 2008 and you might have unknowingly also played earlier versions of the game. A thorough version history is available on Runouw wiki for any readers who want to compare the gameplay across different versions.

Super Mario 63 Classic

The most popular, and likely most familiar, version of SM63 (aka SM63 1.4) was first released on SheezyArt on June 26th 2009, followed by the Newgrounds version one day after. You have your basic premise: Bowser kidnaps Princess Peach and it’s up to Mario to save her. Instead of Stars, you’ll be collecting Shine Sprites like Super Mario Sunshine. Couple this with perfect controls, superb level design and some very creative rehashing and you have a game which is already a ten. But it was the Level Designer which really cranked it up to 11.

The level editor allowed players to make their own levels by combining, and placing items Runouw had already programmed. Tiles, enemies, sling stars etc. While not everything in game was available in the editor (such as the lack of event-triggers), it probably had 95% coverage. You could reposition, replicate or repurpose anything you saw in the game with zero programming knowledge! And even better, you could share your levels on a portal where people could rate or comment.

Ingeniously, the level editor was very well-tied into the main game! Besides the Shine Sprites, SM63 had a second collectable: Star Coins. Unlike Shine Sprites which were required to progress the story, the Star Coins were off the beaten path and were needed for unlocking new features. Most notably, unlocking Luigi and new tilesets in the level editor. If you saw lava, which was unavailable by default, in someone else’s custom level, you had to go back to the main game and hunt down some tricky star coins to be able to unlock it for yourself. Or likewise, if you blindly played through the main story while ignoring the level editor, you would constantly be notified whenever you unlocked a new tileset, encouraging you to try it out.

It was really after this version of SM63 was released that the forums on runouw.com came to life, because people needed to register if they wanted to be able publish their levels on the portal. Although it had been used to share levels directly (via save/load codes) and talk about development prior to the 1.4 release, with the game’s popularity Runouw’s audience grew quite a bit. Before they knew it, the forums were frequently having level design and art contests.

Interim

Following the astounding success of SM63, Runouw was determined to keep making more games. While not all of these projects were successful (notably a canned Super Smash Bros. engine and Star Fox engine), they seem to have sought out a style of their own. Only a few months after SM63, came GT & the Evil Factory, a real-time RPG similar to Megaman Battle Network, with entirely original (albeit simplistic) character designs.

Runouw’s legacy is, funny enough, called Last Legacy. First released in 2013, LL took a lot of influence from Zelda II and was a 2D action RPG with some interesting mechanics. Almost as a call-back to the SM63 days, the player has the ability to terraform tiles using their mana. LL (and Null Space) also featured their own level editors, although neither were as popular as the SM63 editor. A third chapter to LL has been in development for a few years now, but it’s unlikely that it will ever be released seeing as Runouw seems to have lost interest.

Between GT and LL, Super Mario 63 received a final update, sometimes referred to as 1.5 or the 2012 version. But more commonly this final version is taken to be the canonical Super Mario 63 and the 2009 version is referred to as SM63 Classic.

The 2012 version also introduced some changes to the level portal, which migrated ratings/comments to the forum. The 2009 portal was dubbed the classic version and the archive sports an astounding 45,000 levels, a few times more than the modern SM63 portal. That being said, the modern portal also has its advantages, such as being able to jump right into levels from the forum without having to copy lengthy level-sharing codes. Finally, Runouw made an .exe version of the game also available, freeing SM63 from the clutches of Adobe, at the cost of no longer being cross-platform.

From then on, Runouw wasn’t actively involved in the development of SM63 any further, having relegated the role to the forum community who kept organizing events all the while. An unfortunate event was when Nintendo, who hadn’t taken any issue with the game in its heyday, decided to issue a Cease & Desist on SM63 in 2013. This resulted in the Newgrounds version of the game being taken down and jeopardizing the runouw.com version. Couple that with the death of SheezyArt that same year and you had a recipe for disaster.

During these dark days, the player-base of the game was severely crippled and any sense of community outside of the forums was nonexistent. The saying goes that it’s darkest before the dawn, and in hindsight this C&D would prove to be a trial by fire. The retaliation of the determined community in those days will inadvertently lead to SM63 surviving the Flash Player killswitch!

The Super Mario 63 Renaissance

Contrary to initial fears, Nintendo didn’t take any further action against the runouw.com version of SM63 or the forums. So for the next two years the forum community kept the fire burning. When Discord came around, they became early supporters starting a server called PixelLoaf in early 2015. Later that same year, the C&D on SM63 would expire, at least bringing back the Newgrounds version of the game.

After helping found PixelLoaf the Runouw brothers would slowly fade out of sight, presumably since they were continuing their education. From then on, PixelLoaf gradually replaced the forums, becoming the new SM63-central. Level design contests continued, and speed-running which was considerably much less popular during the forum days started to gain a lot attention, eventually splitting off into a server of its own.

So seeing as Runouw had ended development, where did that leave PixelLoaf? The community had been testing the limits of the level editor for years at this point, so of course the next step was modding the game.

There’s also a WIP project to introduce a new level editor, which does not depend on Flash.

So much for Super Mario 63! Let’s talk spiritual successors.

Super Mario 127 is a continuation of SM63 led by SuperMakerPlayer and other community members. Oh boy do the visuals and gameplay look good! It doesn’t use Flash, it’s being made in Godot! And of course people are already speed-running it:

Another continuation of SM63 is, Super Mario 63 Redux lead by @ShibaBBQ. Where SM127 is a modernization of SM63, SM63R aims to be a more of a remake from the ground up. So that means controls more akin to SM63 and other features to improve the gameplay experience without changing the core mechanics around too much.

It’s funny how Super Mario 63 started with a spritesheet, and now, years later, Super Mario 63 inspired an artist to make spritesheet of their own.

On that note, Runouw made a brief comeback recently. Seeing as the forum activity had moved to Discord they’ve frozen the forum and are now redirecting people to the server. Before vanishing off the face of the internet once more, Runouw finally uploaded the full Source Code of SM63 to GitHub. It’s safe to say SM63 couldn’t be in a more secure place than it is today.

What the future holds

The old levels might need some organizing and the search function of the level portal definitely needs fixing. But at least levels from over 10 years ago are still up and online. The forums might be dying, but the Discord server active as ever. In fact they recently rebranded themselves as Hazy Mazy Café.

When January comes around, Super Mario 63 will still be playable through the .exe version. And what’s more, Flash Emulation is coming along nicely. You should expect to be able to play the game on Newgrounds or the Internet Archive with Ruffle. Bugs? Thanks to Runouw graciously sharing the full source code testers and developers will have the perfect reference pinpoint issues in their Actionscript implementations.

Not only has SM 63 outlived flash, through fan-sequels like Super Mario 127 and Super Mario 63 Redux, I’d say we have a lot more good news to hear about.

Long story short, the SM 63 community has set a great example by showing the world how to go around walls that you can’t bring down. Time will tell what the future holds, but things are looking bright!

Imagine never being able to play the one game you enjoyed so much as a kid. The thought of a beloved game being lost would scare most gamers: Mario Kart gone without a trace, Sonic and Knuckles thought to be a fever dream. However impossible this may seem, for many this has become a scary reality. In the world of web games, the internet is an ever-changing place. A game can be played one minute and gone the next, leaving only mere mentions of it from a few people, stranded in an ancient forum, hosted on a potato.

Because web games can be lost so easily, there are a lot of people searching for their web game white whale. Enter the Hunters of Flashpoint. We aim to find what others consider lost: from Postopia breakfast bonanzas to games that are generally considered to carry curses. Hunters find the weirdest nonsense you thought was a fever dream. See, web games are fairly unique, in the sense that they can easily be put on multiple sites with little to no effort. As a result, many web games were hosted on thousands of different sites, plenty of which are carbon copies of each other. Such an effect is a double-edged sword. Flash developers have had their works stolen time and time again, which is bad for business. However, when that original site goes down because the creator decided that it just didn’t live up to their expectations, the game runs the risk of being lost to time. Luckily, some Iranian fellow has your back seeing as he stole the game 3 days after it went up.

With the nature of our work, some of the games we have found have some interesting stories behind them. One Hunter who goes by the online username of ‘Steviewonder’ curated the 28 Weeks Later movie tie-in game, not realizing we thought it lost. Another of Stevie’s stories happened during a time he was scouring open Dropbox accounts, where he found a lost game hidden in the files of a random person from another country. A version of the King.com Luxor game was found on a Chinese site, miraculously working with all assets. I myself am a fairly new face to the project, but even I have my stories. I was able to find South Park: Big Wheel Death Rally (screenshot in the thumbnail) on a site called joflash.hu, which is a Hungarian site that for some strange (but lucky!) reason was not using the broken embed every other site had used. The owner of joflash.hu had instead taken the .DCR and all its assets and ported them to their site, bypassing the problem everyone else who stole the game had when the embed died. Much more recently though for me was a game by the name of Pebbles Popstar, one of the lost Postopia games. This game turned up on a site that I won’t directly mention due to the fact it hosts copyrighted material. (I will say though it’s a Polish filesharing site themed around hamsters, which should be all the info you need.)

However, odd locations on the internet isn’t the only place lost games have turned up. Computerdude77 asked an unusual question to the Flashpoint staff one day: could games be extracted from an old Internet Explorer web-cache? Turns out, after some effort, yes, yes we could. Hearing this information, Computerdude77 took it upon himself to search through the web cache of his grandmother’s computer in hopes of finding some games he played as a kid. Boy, did we get lucky. Many a lost game was found, and a few games that were already in Flashpoint but incomplete were finished thanks to Computerdude77’s work.

Not all hunting goes smoothly though, and there have been more than a few blunders. One time I spent 3 days working on tracking down a game from the Flashpoint Lost Games list. Everywhere I looked for this game it was missing some assets or it hadn’t been copied properly. After 3 days I finally found a copy of it. I was so excited. I posted my findings in the Hunter Lounge, only to be told that the game had been found months ago and curated with a different name. Nobody had marked in on the sheet as found, so I had spent days looking for a game that was already rescued. But hey, those things happen when volunteering one’s own time to save history. These examples are why we need more folks to come together to help save the web games of our collective childhoods. Adobe ends support for Flash in 2020, and when that happens so much more will be lost. It is a race against time, and we need everyone.

If you would like to find out more about this strange and fantastic project, just check out the community spotlight for more info, or if you’re already sold head on over to the website or Discord Server!

The simplest of Flash games is composed of one file ending with the .swf extension (Small Web Format, previously called ShockWaveFlash). That file contains all of the code and assets (such as artwork, audio, fonts, etc.) and it’s playable using a plugin called Macromedia Flash Player, which was later renamed Adobe Flash Player after it got purchased by Adobe. The coding language that is used is ActionScript, and graphics are usually vector, which is different from your usual image.

Instead of having an image made out of pixels, vector graphics will instead have information on the lines that form the image. That means you can scale a vector and never have to worry about the image becoming blurry because instead of scaling an image made out of pixels, you are scaling an image made out of lines. This will also in some cases reduce the file size.

Speaking of SWF, there are many other uses for Flash content. You have Flash movies, which are animated cartoons, and applets, which are small applications that are integrated in a webpage. Even online video players once used Flash!

Discontinuation of Adobe Flash Player

Flash Player was once the most used and the most needed plugin for your web browser. You couldn’t browse the web properly without Flash Player because tons of things needed it. In recent years though, Flash has declined in usage and Adobe is planning on killing the plugin at the end of 2020.