Welcome! This is a list of cheat codes for Crash Bandicoot: The Wrath of Cortex (PS2 version). A cheat device, such as a CodeBreaker or an Action Replay, is needed to use these codes. These codes are in "raw" format, so they may need converting to your cheat device's native format before use. (Google: OmniConvert.) Not all versions of the game are fully supported yet - sorry!

Codes that are written in red are codes that haven't been tested, and might not work. If you find any codes that don't work (or otherwise), I'd appreciate it if you could let me know... please. Thanks!

These codes were found/created by both Hacc and LXShadow. This HTML page was written (well, mostly) by LXShadow. The Editor Guide was written by LXShadow.

Notes:

Editor Codes Usage

The editor codes are powerful codes that let you "edit" many parts of the game's levels. The game has an AI Editor, Anim Editor, Crate Editor, Grass Editor, Light Editor, Object Editor, Wumpa Editor, and Particle Positioner. That's what I meant by "many parts"!

To actually use the editors, though, you need to activate at least three of the editor codes: Loader, Enable All Editors, and Open Editor (Hold Select + R1, L1, R2, L2). It's recommended that you also activate the Font Scale Corrector code so that you can read the editor's fonts more easily (by default, they're ultra-tiny).

When these codes are active, you can enter the main editor menu at any point in the game by holding down Select, R1, L1, R2 and L2. The editors won't work in certain cutscenes, though... they'll only work in the warp room cutscenes and the "game over" cutscene. (They may also work in the talking-head cutscenes that start when you enter a level, but I haven't tried it myself.)

For an incomplete guide on the editors' controls, settings and other useless stuff, you can find the guide here.

E3 Hub Note

As this code's name suggests, when you go to the Warp Room, you'll be taken to the E3 Hub instead. Once you get there, though, you may find yourself stuck underneath the ground. To get out of the ground, keep tapping X to slowly "jump" your way up.

Alternatively, if you have the Cheat Menu code activated, you can turn on the "Lift Player" option, and hold Triangle to rise.

Note that "jumping" your way up won't work if you have the Enable Out-of-Terrain Movement code enabled, though. In this case, using the Lift Player option in the Cheat Menu is the best way out.

"Fire Island" Note

This code is similar to the one above, but this time, you start above ground!..

...but it isn't solid. The rules for the last code apply here: If you don't have the Enable Out-of-Terrain Movement code enabled, you can jump up, up, and up through the ground (this I cannot confirm, however, because I always leave the Enable Out-of-Terrain Movement code on anyway). Otherwise, you'll want to use the Cheat Menu's "Lift Player" option.

With either option, you'll still want to get off of the volcano and onto the main track, anyway. Off you go!

Enable Out-of-Terrain Movement Note

This code lets you walk outside the level's terrain. Usually, you're forced to stay above solid ground (meaning that you have to stay on the level's terrain). This code lets you break the barrier.

(That means you can walk off of the terrain now, by the way.)

Note that you'll still need to use another code to get through the wall splines, though. The wall splines will stop you from going near the edge of the terrain.

Disable Terrain Collisions and Disable Wall-Spline Collisions Note

The Disable Wall-Spline Collisions code lets you walk through the game's invisible walls, and the Disable Terrain Collisions code lets you walk through the level scenery (including the ground).

However, the Disable Terrain Collisions code is slightly different from the other. To activate it, hold Select + R1 + R2. To deactivate it, hold Select + L1 + L2.

The Disable Wall-Spline Collisions code is always active.

Spline Info

Splines are 3D lines, saved into the level files. They're used for pretty much anything in the level that involves 3D lines - the camera path, wall splines (invisible walls), vehicle triggers, possibly more. This code, Show Splines, lets you see them.

The Render Debug Lines code must be activated in order for you to see the splines.

Another thing worth noting is the fact that these lines are affected by the Draw Distance option in the Draw Settings menu. This could be helpful, because you can usually see these lines even when they're hidden behind something, which can make things look like quite a mess.

Debug Lines Info

Debug lines are (or "were") 3D lines drawn by the game for debugging purposes. The game function for drawing these lines was removed, though, so this code (Render Debug Lines) has been made to restore it. (Well, sort of.)

Note that this code is actually still useful, as some of the editors still try to use the missing Debug Lines function. The AI Editor uses it to display the different movement points of the AI placed, the Light Editor uses it to actually let you see where the lights are, and so on. Without the Render Debug Lines code on, these will all be invisible.

So, come on, kids! Render your debug lines today!

Disable "Visitables" - what??

Visitables are used by the game as a means of balancing the frame rate. They decide exactly which polygons (parts of the level) should be drawn depending on the location of the player. This can get a bit annoying when using the editors, since it only lets you see areas close to Crash or Coco's current position.

This code (Disable Visitables) disables Visitables so that you can see the whole level at once, wherever the player is standing. The frame rate may drop when you do this, though. But it's nowhere near as bad as Enter the Dragonfly.

One thing worth pointing out, though, is the fact that the "Draw Distance" option in the Draw Settings Menu will still have an effect, so you might not be able to see the "whole" level until you increase the draw distance. Alternatively, you could decrease the draw distance to help balance out the frame rate.