CrossCode

CrossCode

Developers
	Radical Fish Games
Publishers
	Deck13
Engines
	NW.js
Release dates
Windows	September 20, 2018
macOS (OS X)	September 20, 2018
Linux	September 20, 2018
Reception
Metacritic	86
OpenCritic	84
IGDB	81
Taxonomy
Monetization	One-time game purchase, DLC
Microtransactions	Cosmetic
Modes	Singleplayer
Pacing	Real-time
Perspectives	Bird's-eye view
Controls	Direct control
Genres	ARPG
Art styles	Anime, Pixel art
Themes	Amusement park, Medieval, Sci-fi, Space

General information

Official Discord server

Official wiki

GOG.com Community Discussions

GOG.com Support Page

Steam Community Discussions

Availability

Source	DRM	Notes	Keys	OS
Official website
GOG.com
Green Man Gaming
Humble Store
itch.io
Microsoft Store
Steam		Can be played without Steam.
Discord (unavailable)

A demo is available on Steam and the official site. It is from 2016 and is not representative of all the settings available in the full game.

Monetization

DLC and expansion packs

Name	Notes
Ninja Skin	A ninja styled costume for Lea. Originally exclusive to Indiegogo backers.
ManLea Skin	A skin that swaps Lea's gender.
A New Home	A post-endgame expansion that adds new areas and bosses.

Microtransactions

Type	Notes
Cosmetic	An outfit originally given to backers of the game on Indiegogo. Is strictly cosmetic.

Essential improvements

Skip intro videos

Use CrossCode intro skip

Game data

General/Audio settings

Assist settings

Configuration file(s) location

System	Location
Windows	%LOCALAPPDATA%\CrossCode\cc.save
Microsoft Store	%LOCALAPPDATA%\Packages\DECK13.CrossCodePC_rn1dn9jh54zft\LocalCache\Local\CrossCode\cc.save
macOS (OS X)	$HOME/Library/Application Support/CrossCode/Default/Local Storage
Linux	$XDG_CONFIG_HOME/CrossCode/Default/cc.save

It's unknown whether this game follows the XDG Base Directory Specification on Linux. Please fill in this information.

Save game data location

System	Location
Windows	%LOCALAPPDATA%\CrossCode\cc.save
Microsoft Store	%LOCALAPPDATA%\Packages\DECK13.CrossCodePC_rn1dn9jh54zft\LocalCache\Local\CrossCode\cc.save
macOS (OS X)	$HOME/Library/Application Support/CrossCode/Default/Local Storage
Linux	$XDG_CONFIG_HOME/CrossCode/Default/cc.save

Save game cloud syncing

System	Native	Notes
Discord
GOG Galaxy
Steam Cloud
Xbox Cloud

Video

Video settings

Graphics feature	State	WSGF	Notes
Widescreen resolution			See Resolution.
Multi-monitor			See Resolution.
Ultra-widescreen			See Resolution.
4K Ultra HD
Field of view (FOV)
Windowed
Borderless fullscreen windowed		Fullscreen mode is always borderless.
Anisotropic filtering (AF)
Anti-aliasing (AA)
Vertical sync (Vsync)		See the glossary page for potential workarounds.
60 FPS and 120+ FPS
High dynamic range display (HDR)		See the glossary page for potential alternatives.

• 

  Interface settings (1/2)

• 

  Interface settings (2/2)

Resolution

Native resolution is 568x320, a 71:40 aspect ratio resolution.

The Display Type setting controls how the internal rendered resolution should be scaled and displayed on-screen.

• Original results in a centered 568x320 image, regardless of selected pixel size.
• Double results in a centered 1136x640 image, regardless of selected pixel size.
• Fit maintains the original aspect ratio and applies anamorphic scaling, resulting in either letterboxing or pillarboxing depending on the width and height of the screen area.
• Stretch ignores aspect ratio, and stretches the internal render resolution to fill out the whole screen area.

Both Fit and Stretch display type options results in a slight smoothing/blurring effect over the scaled image on essentially all modern display resolutions. This is a consequence of the interpolation that is necessary to fit/stretch the internal render resolution into what ends up being an unevenly matched target pixel grid compared to the source pixel grid.

The Pixel Size setting controls the internal render resolution before the selected Display Type scaling is applied. Increasing the pixel size can result in a sharper image when using high-res displays.

• 1x results in the internal render resolution being 568x320.
• 2x results in the internal render resolution being 1136x640.
• 3x results in the internal render resolution being 1704x960.
• 4x results in the internal render resolution being 2272x1280.

Integer-ratio scaling

Using a mod that adds the Integer display type and 5x and 6x pixel sizes, it is possible to achieve pixel-perfect integer-ratio scaling for the game even on 4K monitors.

Compatibility with future patches is not be guaranteed.

Use CrossCode-IntegerScaling to add new pixel sizes and an integer-based display type

Open the CrossCode-IntegerScaling GitHub page. Select Clone or download followed by Download ZIP. Extract the Install-IntegerScaling.ps1 PowerShell script from the archive to <path-to-game>. Right-click on the file and select Run with PowerShell. After the patching have finished the file can be removed, although it might need to be re-run after a game update to reapply the patch. Launch the game and navigate to the video settings menu. Select Integer as the Display Type, along with the appropriate Pixel Size. 1x results in the game being rendered at and displayed as 568x320. 2x results in the game being rendered at and displayed as 1136x640. 3x results in the game being rendered at and displayed as 1704x960. 4x results in the game being rendered at and displayed as 2272x1280. 5x results in the game being rendered at and displayed as 2840x1600. 6x results in the game being rendered at and displayed as 3408x1920. 4K HiDPI users who do not see any difference between 4-6x need to use the /force-device-scale-factor=1 command-line argument to prevent the game from applying DPI scaling to the game window. Restart the game to properly allow the change in pixel size to take effect. Notes To undo the patching applied to the game files, run the Uninstall-IntegerScaling.ps1 PowerShell script. The video settings menu can be made inaccessible after the mod have been removed if the save file still refer to the custom video options. Open the general settings menu and click B Reset all settings to restore the original video settings to be able to access the video settings menu again.

Input

Gamepad settings

Keyboard and mouse	State	Notes
Remapping
Mouse acceleration
Mouse sensitivity
Mouse input in menus
Mouse Y-axis inversion
Controller
Controller support
Full controller support
Controller remapping		Can only swap functionality of bumpers (LB/RB, L1/R1) and triggers (LT/RT, L2/R2).
Controller sensitivity
Controller Y-axis inversion

Controller types

XInput-compatible controllers
Xbox button prompts		Set Gamepad Icons to Xbox
Impulse Trigger vibration

PlayStation controllers
PlayStation button prompts		Set Gamepad Icons to DualShock
Light bar support
Adaptive trigger support
DualSense haptic feedback support
Connection modes	Wireless (Bluetooth), Wired, Wireless (Bluetooth) V2 tested.

Generic/other controllers

Additional information
Button prompts		Manually changed through the Gamepad Icons setting.
Controller hotplugging
Haptic feedback
Digital movement supported
Simultaneous controller+KB/M

• 

  Keybindings (1/2)

• 

  Keybindings (2/2)

Audio

General/Audio settings

Audio feature	State	Notes
Separate volume controls		Music, Sound
Surround sound		2.0
Subtitles
Closed captions
Mute on focus lost		Pause when unfocused is an option available as well (defaults to On).
Royalty free audio

Localizations

Language	UI	Audio	Sub	Notes
English
Simplified Chinese
German
Japanese
Korean
Brazilian Portuguese				Fan translation.
Russian				Fan translation.
Spanish				Fan translation.

Issues fixed

Controller issues in Steam version

In Big Picture mode, go to Controller options and set Steam Input to "forced off"

Game content does not display correctly in fullscreen (Linux)

A version change that updated NW.js for Linux to a newer version has caused issues in displaying fullscreen (no issues in Windowed) in some Linux environments.

"This issue is because we updated the NW.js version recently for Linux, using the newest version. We did this so gamepad works on Steam Deck, where the game also runs fine otherwise. You can manually downgrade to an older Version of NW.js..." (Lachsen (developer)

The most recent version of nwjs that does not cause the issue is nwjs-v0.50.3

Take a working version of NWJS (https://dl.nwjs.io/v0.50.3/nwjs-v0.50.3-linux-x64.tar.gz) and extract + overwrite it over the game contents directory (CrossCode/game/). Additionally, rename nw (from the extraction) to CrossCode

Force Steam Linux Runtime (Linux and SteamOS)

By default only the Steam Runtime 1.0 is shown on the list of compatibility tools as Steam for Linux itself relies on it. For other versions, such as 3.0, to show up in the Compatibility Tool menu it might be needed to interact with its library page at least once (such as verifying its files).

The Steam Deck by default will use Proton even though a Linux version is available. While this might work well enough, in some circumstances this might cause issues that can be fixed by forcing the "Steam Linux Runtime" compatibility tool which will force download of the Linux build.

Usage of the Steam Linux Runtime can also fix some possible conflicts between the game (which uses Chrome underneath) and the system (native or flatpak runtime) libraries.

Enter game properties and set Steam Linux Runtime
Open the Library page for CrossCode Open Properties Enter the "Compatibility" tab Mark the checkbox "Force the use of a specific Steam Play compatibility tool" Select "Steam Linux Runtime 1.0 (scout)", or any other desired Steam Linux Runtime variant

Broken achievements on native Linux build

This issue doesn't happen when running the Windows version via Proton under Linux, only the native Linux build is affected.

Devs are apparently aware of the issue but it might take a while for a proper fix.

When the devs updated to nw.js 0.63.1 (based on Chrome 100.0.4896.127) they didn't update Greenworks (the library which provides Steam integration for Node) properly, which broke Steam integration (i.e. broken achievements).

The change was likely motivated from, among other things, an update for Chrome 99 which improved support for the emulated Xbox controller Steam Input creates under Linux (possibly motivated by the Steam Deck).

The devs are apparently aware of the issues but will only be able to deal with it once they are done with their next game .

This basically leaves a few possible solutions for this. Either:

• Downgrade nw.js to a version compatible with the current Greenworks (might break controller support if not containing the aforementioned controller fix)
• Upgrade Greenworks to a version supporting the currently in use nwjs version
• Upgrade nw.js to a newer version (benefits currently unknown) and upgrading to a compatible Greenworks

Upgrade Greenworks using crosscode-greenworks

Awakening made crosscode-greenworks available, which has the needed files for fixing Steam integration for the current nw.js. Visit the crosscode-greenworks release page Download the latest version available Extract the files Use the files extracted from the zip file to replace the equivalent versions from the game folder (i.e. copy the assets/ folder from zip onto the game assets/ and replace everything)

Other information

API

Technical specs	Supported	Notes
Direct3D	11
OpenGL	3.3

Executable	32-bit	64-bit	Notes
Windows
macOS (OS X)
Linux

System requirements

Windows

macOS (OS X)

Linux

Windows
	Minimum	Recommended
Operating system (OS)	XP	7, 8
Processor (CPU)	2 GHz dual core
System memory (RAM)	2 GB	4 GB
Hard disk drive (HDD)
Video card (GPU)	1 GB of VRAM

A 64-bit operating system is required.

macOS (OS X)
	Minimum	Recommended
Operating system (OS)	10
Processor (CPU)	2 GHz dual core
System memory (RAM)	2 GB	4 GB
Hard disk drive (HDD)
Video card (GPU)	1 GB of VRAM

Linux
	Minimum	Recommended
Operating system (OS)
Processor (CPU)	2 GHz dual core
System memory (RAM)	2 GB	4 GB
Hard disk drive (HDD)
Video card (GPU)	1 GB of VRAM