Remapping buttons on the Cronus Zen: Remapper profiles, MAX Mapper and GPC remap()

#Why remap at all?

Games do not always let you move the button you need. A player with limited hand mobility may need jump on a shoulder button; a fighting-game player may want a specific pad layout; a crossover user may want the DualSense's Create button to act as Xbox's View button. Remapping at the adapter level works in every game, including ones with no remap menu, and needs no script logic. It is also the Zen feature least entangled with platform rules, because it automates nothing.

#Method 1: MAX Mapper (Zen Studio Legacy)

MAX Mapper is a plugin in Zen Studio Legacy that builds Remapper profiles visually. Collective Minds describes it as remapping any buttons, analog sticks or sensors, with sensitivity adjustments for any button and advanced adjustments for the sticks. You can keep an unlimited number of profiles, export and import them to share or back up, and generate a GPC script from any profile.

#Setting up a profile

1. Open MAX Mapper from Zen Studio Legacy's plugins.
2. Profile → New, give it a name.
3. Choose the Input controller: PlayStation 4, Xbox One, PlayStation 3, Xbox 360 or Switch Joy-Cons. The official note: for a PS5 controller select PlayStation 4; for an Xbox Series controller select Xbox One.
4. Choose the Output console: PlayStation 4, Xbox One, PlayStation 3, Xbox 360 or Switch.
5. Configure mappings, sticks and triggers (below).
6. Test live: while the plugin is running, changes take effect instantly on a connected controller, so you can check before saving.
7. Drag the profile from the Remapper Profiles list onto a slot in the Programmer and program the device.

#Mapping

Click a button in the layout and choose the output it should produce. Any input can go to any output, and one input can be left unmapped to disable it.

#Sticks

For each stick:

• X and Y sensitivity: how far the output moves for a given input.
• X and Y deadzone: the radius around centre that is ignored, to cancel jitter.
• Invert: flips an axis.
• Midpoint: default 50%. Setting it to, say, 80 creates a low-sensitivity zone near rest for accuracy and a high-sensitivity zone further out for fast movement.
• Stick size: an outside deadzone that converts the square range of a mouse or Wii IR input to the circular range of a stick. Leave at the default 142 for Xbox games; the official page notes values around 115 to 120 for some PS3 and PS4 titles.

#Triggers

Sensitivity for the left and right triggers, useful for making a trigger register earlier or later.

#Exporting to GPC

The generate GPC operation opens the profile as a script in the editor. This is the bridge to current firmware: since Legacy's Programmer is disabled above firmware 2.2.14, export the script, save it, and program it from Zen Studio Live. It is also the easiest way to learn what the remap statements look like.

#Method 2: automatic crossover remapping

When you connect a controller from a different platform, the Zen translates its layout automatically so face buttons, sticks and triggers land where the console expects. This happens with no profile loaded and, importantly, it is one of the two features that stay active in Tournament Mode alongside crossover support. If all you need is "DualSense on Xbox with sensible buttons", you may not need MAX Mapper at all. Details in crossover controllers.

#Method 3: GPC remap and unmap

Scripters can remap in a few lines. The official guide documents remap and unmap as top-level statements:

remap PS5_CROSS -> PS5_SQUARE;
remap PS5_SQUARE -> PS5_CROSS;
unmap PS5_TOUCH;

main {
}

The first two lines swap Cross and Square; unmap stops the touchpad click reaching the console. Two details from the official page matter: remaps are applied after main, so your script logic still uses the original identifiers, and an unmapped input is still readable by the script even though the console never sees it. Because they are compile-time declarations, they cost nothing per cycle.

For remaps that depend on a condition, the runtime tools are on the blocking-and-swapping page: swap(a, b) exchanges two controls' values for the current cycle only, so it runs inside an if in main; block(id, ms) suppresses one control for a timed period; and set_val with get_ival handles arbitrary routing, as shown in reading values with get_val.

Stick tuning in GPC uses sensitivity(axis, midpoint, value) and deadzone(x_axis, y_axis, shape, radius), mirroring MAX Mapper's stick controls. The guide also mentions a device-level remapper via set_remapper and save_eeprom, which persists beyond the script and should be saved only on a deliberate action.

#Which method should I use?

#Notes and limits

• Elite paddles. Series 1 paddles have their own identifiers and can be mapped independently; Series 2 paddles cannot, and Scuf paddles remap only together with the face button they mirror.
• One profile per slot. A Remapper profile occupies a slot like any script. Eight slots, eight layouts.
• Console-side remapping. Consoles offer their own remapping for official controllers. If you only need a simple swap on a matched controller, the console setting may be enough and involves no adapter.
• Games that detect layout changes do not exist in any meaningful sense; the console receives ordinary button presses.

For the rest of the Legacy plugins, MAX Combo and MAX Rec, see the Zen Studio walkthrough.