Ruffle nightly fixes AVM1 serialization for better Flash preservation

Ruffle’s July 1 nightly tightened AVM1 serialization, fixing how top-level date, XML, and display objects were written out, while also changing the serializer helper path and refreshing the rust-flash-lso dependency. That is invisible work on the surface, but in a Flash Player emulator written in Rust, it is exactly the kind of plumbing that keeps old menus, cutscenes, minigames, and oddball web content from falling apart.

The build fits a clear pattern across the most recent nightlies. June 30 tightened recursive serialization and cleared a Rust security advisory. June 29 corrected the URL used when SWFs were loaded through Loader.loadBytes. June 25 added Stage3D test updates and a batch of core cleanup changes. Taken together, those changes show Ruffle spending its time inside the emulation core rather than on showier feature work.

That matters because a large slice of Flash history lives in places where correctness beats flashiness: old web portals, advergames, school projects, and one-off artistic pieces that depended on obscure ActionScript behavior. When serialization is wrong, save data can disappear, scripted state can break, and embedded content can fail in ways that are hard to spot from a screenshot. The July 1 changes target exactly those failure points by making AVM1 handle its objects more faithfully and by nudging the serializer’s support code into better shape.

The result is the sort of upgrade preservation fans actually feel when they load a stubborn SWF today. A game that used to forget state between screens, or a site element that choked on a serialized object, has a better shot at surviving intact across browser, desktop, and archival workflows. Ruffle is not just chasing compatibility for the sake of a changelog entry here. It is still chipping away at the tiny runtime details that decide whether old Flash content merely opens, or actually behaves the way it did when people first played it.