CronusZenWiki
Setup & Firmware

Cronus Zen Memory Slots: How to Flash and Switch Scripts

How Cronus Zen memory slots work: eight 32 KB slots, flashing scripts and GamePacks in Zen Studio, cycling slots on the device, and remote slot change.

Updated September 2, 20266 min readCECZW EditorialBeginner10 min

The Cronus Zen has eight memory slots of 32 KB each, and they can hold any combination of GPC scripts, GamePacks, and remapper profiles. You fill them from Zen Studio's Programmer panel over the PROG cable, then switch between them at the console using the blue Memory Slot button on the device — no PC required once the slots are flashed. This guide covers the Cronus Zen memory slots end to end: flashing, erasing, switching on the OLED, the remote slot change option, and a sane way to organize eight slots.

What the memory slots are

Think of the slots as the Zen's onboard library. Zen Studio is where scripts are compiled and configured, but nothing in Zen Studio affects gameplay until it is written into a slot on the device itself. Once flashed, slots persist without the PC: you can unplug from Zen Studio, connect the Zen to a console, and cycle through everything you loaded.

Three kinds of content can occupy a slot, per Cronus's documentation:

Content type Where it comes from Typical use
GamePack Cronus's built-in pack library in Zen Studio Pre-built, menu-configurable mods for a specific game
GPC script The compiler panel (community or self-written .gpc files) Custom logic — see loading a script
Remapper profile Zen Studio's remapper Button/stick remapping without any scripting

Each slot holds up to 32 KB of compiled output. Most scripts fit comfortably; very large community scripts can approach the ceiling, and a script that exceeds it simply will not flash to the slot. Zen Studio's device panel shows flash memory usage statistics if you want to see where you stand.

There is also an implicit ninth state: slot 0, the unloaded state. When no slot is active the Zen passes controller input through untouched, and the OLED shows the Collective Minds logo instead of a slot number. Unloading is how you play clean without erasing anything.

Flash a script or GamePack to a slot

Flashing happens in Zen Studio's Programmer panel:

  1. Connect the Zen's PROG port to your PC with the PROG cable and open Zen Studio. If Zen Studio is not set up yet, start with installing Zen Studio.
  2. Open the Programmer panel. You will see the eight slots alongside the available content: GamePacks, any script open in the compiler, and remapper profiles.
  3. Drag your chosen GamePack, script, or profile onto a memory slot.
  4. For GamePacks, the GamePack Configuration Interface (GCI) opens so you can set the pack's options; it also opens later if you click the slot's number.
  5. Click Program Device. Zen Studio writes every configured slot to the Zen — this is the step that actually changes the device.
  6. Wait for programming to finish before unplugging.

Nothing is committed until Program Device runs. You can arrange all eight slots first and write them in one pass, which is faster than flashing one at a time.

Tip

If you change a GamePack's settings through the GCI afterward, use the Programmer panel's Reload Memory Slots option to resync Zen Studio with what is actually on the device. Otherwise the panel can show stale contents.

Erase or replace slots

  • Replace: drag new content onto an occupied slot, then Program Device. The old contents are overwritten.
  • Erase: drag the slot to the trash icon, then click Program Device to confirm the deletion. Until you program, the erase is only staged.
  • Erase everything: the device panel includes a memory-slot erasure option alongside factory reset. Use the targeted trash-icon route for routine cleanup and keep the full wipe for genuine resets.

Erasing a slot removes the compiled copy from the device only. Your .gpc source files and GamePack configurations on the PC are unaffected — but the reverse is worth remembering too: the Zen stores compiled output, not source. Keep your .gpc files organized on the PC, because you cannot pull a script back out of a slot to edit it.

Switch slots on the device

At the console, slot switching is a hardware affair:

  1. Press the blue Memory Slot button on the Zen (the right-hand button — the left one, P2, is Bluetooth pairing).
  2. Each press advances to the next occupied slot, and the OLED shows what is loaded.
  3. Keep pressing to cycle through all occupied slots and back to the unloaded state, indicated by the Collective Minds logo on the OLED — no GamePack or script active, inputs passing straight through.

The Zen only cycles through slots that contain something, so eight taps are the worst case. If you are ever unsure what is running, Zen Studio's Device Monitor displays the active slot number and the name of the loaded GamePack or script in real time.

Remote slot change from the controller

Reaching for the Zen mid-session is awkward if it is buried behind a console, so Zen Studio's device settings include a remote slot change option that lets you switch memory slots from the connected controller. Two honest caveats from the documentation:

  • The exact button combination varies by controller type, and Cronus does not publish one universal combo. Check the setting's description in your Zen Studio version and Cronus's current documentation for the combination that applies to your controller.
  • Many community scripts and GamePacks also bind their own controller shortcuts (menus, mode toggles). A remote slot-change combination can collide with a script's bindings, so test the combo with your actual scripts loaded before relying on it in a match.

Separately, many GamePacks offer OLED configuration menus opened by controller shortcuts — those are per-pack features documented in each GamePack's own guide, not part of the slot system itself.

Managing eight slots well

Eight slots sounds like plenty until you play three games with two script variants each. A structure that holds up:

  • Group by game, order by frequency. Put your daily game's scripts in slots 1–2 so they are one tap away, and park rarely used packs at the end of the cycle.
  • Keep one slot for a plain remapper profile. A scripting-free profile gives you a quick "legit but remapped" option, with slot 0 as the fully clean state.
  • Update by reflashing the same slot. When a script gets a new version, overwrite its existing slot rather than adding a copy — duplicate versions in different slots is the classic way to play an outdated script by accident.
  • Track versions on the PC side. Slot contents are not self-describing beyond a name, so a dated folder of .gpc sources is your real record of what is where.
  • Mind the firmware. After a firmware update, confirm your slots still behave as expected before a serious session; reflash from source if anything seems off.

FAQ

How many memory slots does the Cronus Zen have?

Eight, at 32 KB each, holding any mix of GPC scripts, GamePacks, and remapper profiles. There is also an unloaded state — slot 0 — where the Zen passes inputs through with nothing active.

How do I change Cronus Zen memory slots without a PC?

Press the blue Memory Slot button on the Zen itself. Each press cycles to the next occupied slot, shown on the OLED, and cycling past the last slot returns to the unloaded state. Slots persist on the device, so no PC is needed after flashing.

That is the unloaded state: no GamePack or script is currently active, and inputs pass through unmodified. Press the Memory Slot button to cycle to an occupied slot.

Can I switch slots with my controller instead of the Zen's button?

Yes — enable the remote slot change option in Zen Studio's device settings. The button combination varies by controller type and is not one universal combo, so check the setting and Cronus's current documentation, and test for conflicts with your scripts' own shortcuts.

Does erasing a slot delete my script?

It deletes only the compiled copy on the device. Source .gpc files and configurations on your PC are untouched. The reverse does not hold — the Zen cannot export a slot back into editable source, so keep your originals.