# Cronus Zen script not working, or stops after a reboot > A Cronus Zen script not working is usually on slot 0 or was never written to a slot; after that, check Tournament Mode, the game, firmware errors and settings. - Canonical: https://cronuswiki.com/docs/cronus-zen-script-not-working - Site: Cronus Wiki (https://cronuswiki.com/) - Author: Cronus Wiki Editorial (https://cronuswiki.com/authors/editorial) - Section: Troubleshooting - Published: 2026-09-21 ยท Updated: 2026-10-07 - Tags: script not working, slot, firmware, settings, troubleshooting --- A Cronus Zen script that does nothing is usually on the wrong slot: slot 0 runs no script, so read the slot number first, then check the script was actually written to a slot. The causes after that are almost never the Zen itself. Work through them in order. ## Which symptom you have | Symptom | Start at | | --- | --- | | Script does nothing at all | Step 1 | | Worked until a power-off, then gone | Step 2 | | No script does anything, even GamePacks | Step 3 | | Worked on day one, inert now | Step 4 | | Runs, but does the wrong thing | Step 5 | | Error on the OLED or in Zen Studio | Step 6 | | Forgets settings after power-off | Step 7 | | Buttons doubled or fighting | Step 8 | ## 1. The slot Read the OLED. The number it shows is the active slot. Slot 0 means no slot is loaded; nothing runs there. If you programmed slot 3, the OLED must say 3. Change slot with the P1 button until it does, or use the remote slot change combo you chose in Zen Studio's Device panel (PS + SHARE or XBOX + VIEW, for example). This resolves more "script not working" reports than anything else on this page. Check the number again after every power-up rather than assuming; [Script slots and memory](/docs/cronus-zen-script-slots-and-memory). ## 2. The script was never written to a slot In Zen Studio Live, sending a script or GamePack to a slot does not write it: Cronus's setup has you open Home, click **Program**, then **Program Slots**, and wait for "Programming complete". In desktop Zen Studio, Build and Run (F5) runs a compiled script temporarily: Cronus's Device Monitor shows it as slot 10, and with the Device panel option "Unload Script When Closing Device Monitor" on, it unloads when Device Monitor closes. A power-off ends it either way. To keep a script, drag it onto a memory slot in the Programmer panel and click **Program Device**, which writes all configured slots to the Zen, and wait for it to finish. If you changed a GamePack's options through its configuration interface, Cronus's **Reload Memory Slots** syncs Zen Studio with what is on the device. [How to put a script on the Zen](/docs/how-to-put-a-script-on-cronus-zen). ## 3. Tournament Mode Zen Studio can switch the Zen into Tournament Mode, which Cronus says disables scripts, macros and GamePacks. When it is on, "TE" appears after the firmware version and the OLED shows a tournament graphic. Switch back with **Tools > Zen Operational Mode > Normal Mode > Finish**; the active mode is also shown, and clickable, in Zen Studio's status bar. ## 4. The script needs activating Many scripts do nothing until you use a button combination or step through a menu on the OLED, especially timing scripts that calibrate on first run. GamePacks are configured through their own OLED menu. A script that looks inert may be waiting. Read its instructions for the activation combo and the on-screen prompts. This also explains a script that "worked on the first day": it was activated then and is waiting now. ## 5. Wrong game, wrong console, wrong version A script is written for one game on one console family, and often for one version of that game. A Call of Duty script does nothing useful in NBA 2K; a script written for a previous title will compile and run and be wrong. Timing scripts are sensitive to game patches: a shot timing that was right last season can be off after an update. Check the author's notes for the game version the script targets and whether an update exists. ## 6. Errors from the firmware or Zen Studio Cronus's current guide lists firmware 2.3.2 (18 August 2026) as the latest release, and is built around Zen Studio Live, the browser-based version of Zen Studio; its changelog lists Zen Studio Live 1.0.9 (8 September 2026). Its older guide still shows firmware 2.2.14 and desktop Zen Studio 1.6.1 Build 82. Where the two guides differ below, this page follows the current one. | You see | Cronus's explanation | Cronus's fix | | --- | --- | --- | | Stack or bytecode error | Corrupted memory, an invalid script or a failed programming process: interrupted programming, power loss while flashing, or a corrupted GamePack or script. Cronus's older guide blamed a script made for a different firmware | Hard reset, then reinstall your scripts; if the error returns right after one script, that script is corrupted or incompatible | | "Programming Error" in Zen Studio | A faulty cable, corrupt Zen Studio files, or a script with old code no longer compatible | Tools > Reset Zen Studio; ask the author for a current version | | "Firmware Version Incompatible" | The Zen's firmware or Zen Studio is outdated | Update the firmware, update Zen Studio, then reconnect the Zen and restart Zen Studio | | A GPC error message on the OLED | Since firmware 2.1.0 Beta.16, a script error returns the Zen to slot 0 and shows the message instead of crashing | Send the message to the author | | E3, E3001 or E3002 | Firmware corrupted or missing, per Cronus's current troubleshooting page; its older guide called E3002 a system crash with faulty scripts the primary offender | Bootloader recovery and a reflash; if it returns after one script, contact the script's author | Older 16-bit scripts need the **Use Legacy 16Bit Compiler** option in the Device panel. Cronus's guide only documents moving forward to its current firmware; it does not offer a downgrade as a fix. [Firmware: update, downgrade, recovery](/docs/cronus-zen-firmware-update-downgrade-recovery) and [Zen Studio errors](/docs/zen-studio-errors). ## 7. Settings did not save You tuned the script, powered down, and it came back at its defaults. A script keeps its runtime settings only if its author wrote it to save them. | The script's notes say | What happens on power-off | What to do | | --- | --- | --- | | Settings save automatically | Kept | Nothing | | Save with a combo | Kept only if you pressed it | Press it after tuning, every time | | Nothing about saving | Lost | Write your values down; re-enter after each boot | [Script slots and memory](/docs/cronus-zen-script-slots-and-memory) has the detail on what persists. ## 8. Two things fighting A mouse-and-keyboard profile and a script in the same session, an Elite or Edge with its own remaps on top of the script, or Steam Input on PC remapping over the script: each is a second layer changing the same inputs. On a DualSense Edge, Cronus says to create a custom profile (its current page suggests a name like BEAM) with right stick sensitivity curve Default, curve adjustment 0 and deadzone 0%, or many M.O.D.s will break. On PC, disable Steam Input for the game, and Cronus's older guide says to unplug the PROG cable before starting any game. [DualSense Edge and Elite](/docs/cronus-zen-dualsense-edge-and-elite-controllers) and [PC setup](/docs/cronus-zen-pc-setup) cover the specific conflicts. ## 9. Power cycle and reset Cronus's first recovery for a crashed or stuck Zen is to unplug every USB cable for at least ten seconds, reconnect, and re-select the slot. A hard reset (P1 and P2 held while connecting CONSOLE/PC for at least four seconds, then a factory reset in Zen Studio over PROG) is the next step, and the first step for stack or bytecode errors, but Cronus says it erases every script stored on the Zen: back up M&K profiles and keep copies of your scripts. Cronus's older guide said scripts cannot be backed up from the device; Zen Studio Live's changelog now refers to slot backups. Desktop Zen Studio's Device panel also has **Erase Memory Slots**, which clears the slots without touching other options, and Zen Studio Live has an erase memory action. ## 10. Ask the author, with the right information If slot 0 controls work, the slot is programmed, the Zen is in Normal Mode, the versions match and the script still does nothing, the script's author is the next stop; Cronus's own error pages send script bugs to the script's creator. Send these five facts; "it doesn't work" gets you nowhere. | Fact | Where to find it | | --- | --- | | Zen firmware version | Zen Studio Live, or desktop Zen Studio's status bar or Help > About Zen Studio (F1) | | Zen Studio version | Zen Studio Live or desktop Zen Studio, and which build; Help > About Zen Studio (F1) on desktop | | Console and model | PS5 / PS5 Pro / Series X / Series S / PC | | Game version | The game's settings or title screen | | Exactly what the OLED shows | Photograph it | ## What this page does not cover A script that works but does not do what you hoped is not a fault. A timing script needs calibration to your player and your release; an anti-recoil script needs the values for your weapon; a mouse profile needs tuning. Those are the script's instructions, not a Zen problem. And if the OLED shows an error message rather than silence, [Zen Studio errors](/docs/zen-studio-errors) lists what it means. ## Quick reference | Symptom | Most likely cause | First fix | | --- | --- | --- | | Nothing happens | Slot 0 or wrong slot | Read the OLED; press P1 | | Gone after power-off | Never programmed to a slot | Program Slots in Zen Studio Live; Program Device on desktop | | No script or GamePack works | Tournament Mode | Tools > Zen Operational Mode > Normal Mode | | Inert after day one | Needs activation combo | Script's notes | | Wrong behaviour | Wrong game, console or version | Author's notes; update | | Stack or bytecode error | Corrupted memory or script, or interrupted programming | Hard reset; reinstall scripts; current version from the author | | Settings reset | Not saved | Save combo, or write values down | | Doubled inputs | Second remapping layer | Edge custom profile; Steam Input off | ## FAQ **Why does my Cronus Zen script not do anything?** Most often the Zen is on slot 0, which runs no script, or on a different slot from the one you programmed. Read the OLED. If the slot is right, check the script was written to a slot (Program Slots in Zen Studio Live, Program Device on desktop) and the Zen is not in Tournament Mode. **Why does the script reset after I turn the console off?** Either it was only running from Build and Run, which never writes it to a slot, or its settings are not saved. Some scripts save only when you press a specific combo; check the script's notes. **The script worked last month and now errors. Why?** Cronus says programming errors can mean the script has code no longer compatible with current updates. Its current troubleshooting page ties stack or bytecode errors to interrupted programming, power loss while flashing, or a corrupted script, and says an error that returns right after installing one script means that script is corrupted or incompatible. Ask the author for a current version. **The script compiles but plays wrong. Why?** Wrong game version, wrong console, or the script's calibration was not done. A timing script for one game version can be off after a game patch; check the author's update notes. **Why does the script work on the first day and not after?** It was activated on the first day and is waiting for its activation combo now, or its unsaved settings were lost on power-off. Both are in the script's notes. **Can two scripts run at once?** No. One memory slot is active at a time. A mouse-and-keyboard profile and a script both writing the right stick is a common reason a setup behaves strangely.