Guilty Gear Strive source code leak explained: Season 5 characters discovered

Jam GG strive season 5

Guilty Gear Strive’s source code got leaked as a result of a hack, with new data about the game getting leaked online in one of the most egregious leaks in fighting game history.

Not only did this build have the remaining Season 4 characters in it, it also contains new moves for many members of the cast and the entire Season 5 line up. A fifth season wasn’t even officially confirmed yet, but files show early concept art and moves for another year of content.

Additionally, this build has a fully-playable version of Unika, the next character coming in the Season 4 pass, as well as Lucy from Cyberpunk: Edgerunners being revealed for the first time. She’s playable as well in this build, though her animations are somewhat incomplete and clearly still in development.

But who’s coming in Season 5? And how did this build get out and into the wild in the first place? Here’s what we know about the leaks for Guilty Gear Strive.

How did Guilty Gear Strive’s source code get leaked?

A hacker claimed to have hacked into Arc System Works’ internal servers, saying it was “easy” to get access and dropped the game’s source code, complete with a build that had Season 5 content early in development. They just dropped the game files in a public Discord and disappeared.

The leak contains almost a terabyte of uncompressed data, along with three different builds of the game from various stages in development according to the original leaker.

Related

It’s an unintended look at the future of the series, but also a reassuring one for fans considering it was up in the air whether or not S4 would be the last big content drop and Lucy would be the last new character.

Now, it’s almost certain that we’ll be getting more out of Strive despite the game having been out for years already. It’s great news for fans of the game who want a bit more out of it before the next entry.

That said, the source code being leaked presents a possible security risk for players and could result in RCE (remote code execution) hacks, although the chances of this happening are fairly slim and those playing the game shouldn’t be worried. That said, it does make building cheats for the game much easier and could cause issues with online play.

It was also discovered that a model of Super Saiyan Goku is, for some reason, a “load-bearing file”, meaning Guilty Gear Strive literally cannot launch unless his model is in the game. No one has any clue why this is the case.

Which characters are coming in Season 5?

Considering that everything in the build (outside of the fully playable version of Unika) is in early development, the nitty gritty details of new character moves won’t be discussed here. There’s a good chance that all of it gets drastically changed before this new content drop sees the light of day, anyways.

However, the Season 5 roster line up is almost certainly set in stone. Here’s who you can expect to see in Season 5:

Note: All art used here is from past Guilty Gear titles and not the leaks.

Jam Kuradoberi

Jam’s the furthest alone in development of the bunch, with her already having several of her moves in the game files and some early concept art. She’ll likely be the first Season 5 character that gets shown off, with the rest following in an order that’s yet unclear.

None of the other new characters are playable in the current version that’s been leaked, and it’s entirely possible that they’re still leftover files from Xrd or works in progress that ultimately end up getting scrapped.

Kum

Answer

Raven

New Arc System Works game?

Within these files was a game that Arcsys haven’t even announced yet titled “Project: Watari”. It’s targeting a November 25, 2025 release date according to dataminer collective XOX Leaks, and it may be Switch 2 exclusive at launch.

That’s everything we know about the Guilty Gear Strive source code leaks and most of the new Season 5 information. Arc System Works have yet to comment on the contents of this leak, and everything here should be taken with a grain of salt.

Page was generated in 0.10128688812256