CzenScripts field guide

NBA 2K27 Script Showing the Wrong PlayStation or Xbox Buttons

If your NBA 2K27 Cronus Zen script displays L2, Square and Options when you use Xbox—or LT, X and Menu on PlayStation—the script may be detecting the console rather than your controller.

Shane T 11 min read
NBA 2K27 Script Showing the Wrong PlayStation or Xbox Buttons
Before you begin

Start with the recommended baseline, change one value at a time, and test each adjustment under consistent conditions.

Your NBA 2K27 Cronus Zen script works, but its OLED menu is showing the wrong controller buttons.

Maybe you are using Xbox and the Zen says:

L2 + Options

or:

Square / Cross

Or perhaps you are using a PlayStation controller and the script displays:

LT + Menu

LB

or Xbox-style A/B/X/Y labels.

This does not automatically mean the script is broken.

After checking the current CzenScripts NBA 2K27 GPC archive, there are several reasons this can happen.

Quick Answer

NBA 2K27 scripts can determine their button labels in different ways:

  • Some detect the connected console and change OLED labels automatically.
  • Some only change certain menu labels.
  • Some always display PlayStation-style text.
  • Some use Xbox-style text internally.
  • Some detect the console rather than the physical controller.

As a result, the label shown on the OLED may not always match the controller in your hands.

PlayStation vs Xbox Button Names

PlayStation Xbox Equivalent
L2 LT
R2 RT
L1 LB
R1 RB
L3 LS
R3 RS
Cross A
Circle B
Square X
Triangle Y
Options Menu / Start
Share View / Back

So if your script says:

L2 + Options

the equivalent Xbox combination is normally:

LT + Menu

The Important Difference: Console vs Controller Detection

This is the biggest reason for confusing OLED labels.

Cronus GPC supports separate functions for identifying:

  • The connected console/output platform
  • The connected controller

They are not the same measurement.

A script can therefore decide what button names to display based on the console rather than the controller physically connected to your Zen.

Example: Xbox Controller on a PlayStation Setup

Imagine you are physically holding an Xbox controller, but the Zen's console/output side is operating as PlayStation.

If the NBA 2K27 script checks the console rather than the controller, it may decide:

PlayStation detected → display PlayStation labels.

Your OLED could therefore say:

L2 + Options

even though the buttons physically in your hands are:

LT + Menu

That behaviour can be completely consistent with how the GPC was written.

How Current NBA 2K27 Scripts Detect the Platform

Several scripts in the current CzenScripts archive use logic equivalent to:

If Xbox console detected → use Xbox mode
Otherwise → use PlayStation mode

Examples include:

  • All Star
  • Burger V3
  • Prime
  • ReloxHQ V4
  • Saint V7
  • Swish Labs V6.0
  • TT Scripture V4
  • YEW2K
  • Hoops V1.5
  • Glory V7
  • Green V2

However, these scripts do not all use the detected platform in exactly the same way.

Some Scripts Change Their OLED Labels Automatically

Green V2 is a clear example.

Its source contains separate startup instructions for:

PlayStation:

L2 + Options

and:

Xbox:

LT + Start

The script chooses which version to display based on its detected console state.

Swish Labs V6.0 Also Switches Labels

Swish Labs V6.0 uses the same type of system on its screensaver.

Its source contains separate text for:

  • L2 + Options
  • LT + Start

It also switches its L3/R3 remapping labels into Xbox-style LS/RS terminology when Xbox mode is detected.

Glory V7 Has Extensive Platform-Specific Labels

Glory V7 contains separate PlayStation and Xbox text for several options.

Examples include:

PlayStation Display Xbox Display
L2 + R2 LT + RT
L2 + R3 LT + RS
L2 + L3 LT + LS
R2 + SQ RT + X
L2 + SQ LT + X

The actual menu headers also change where necessary.

Hoops V1.5 Changes Square to X

Hoops V1.5 contains separate menu headers for PlayStation and Xbox.

For example:

PlayStation: SQ is mapped to

Xbox: X is mapped to

The actual behaviour is the same type of remapping feature—the text simply changes to match the detected platform.

YEW2K Also Changes Menu Text

YEW2K maintains separate PlayStation and Xbox OLED menu headers.

For example, its remap page changes between platform-specific button terminology when Xbox mode is detected.

Saint V7 Only Changes Some Labels

Saint V7 detects Xbox and changes certain menu values accordingly.

Its remap options and Dunk Meter labels can switch between PlayStation and Xbox terminology.

However, some other strings remain fixed—for example, parts of its source still contain PlayStation-style text such as:

L2 + SQ

This means the same script can contain a mixture of adaptive and fixed labels.

Some Scripts Detect Xbox but Still Show PlayStation Instructions

This is another important source-level finding.

Scripts such as:

  • TT Scripture V4
  • Burger V3
  • ReloxHQ V4
  • All Star

contain console-detection logic, but some menu instruction strings are still written using PlayStation terminology.

For example, source text can contain:

  • L2 + RIGHT
  • L2 + LEFT
  • L2 + UP/DOWN
  • L2 + Options

even though the script also knows whether an Xbox console was detected.

In that situation, seeing PlayStation button names on Xbox can simply be a cosmetic limitation of the OLED text.

Fixed Labels Do Not Necessarily Mean Fixed Controls

The words displayed on the OLED and the controller input being processed are two separate parts of the GPC.

A developer might write a menu instruction as:

L2 + UP/DOWN

while the underlying input identifiers still correspond to equivalent controller positions when the script is used on another supported platform.

So do not assume that a PlayStation label means the feature cannot work with Xbox.

Why GPC Scripts Often Use PS4 Button Names Internally

You may also notice that many NBA 2K27 GPCs contain code such as:

  • PS4_L2
  • PS4_OPTIONS
  • PS4_SQUARE
  • PS4_CROSS

even though the script is intended for more than one controller type.

Those are GPC input identifiers used by the script code.

The existence of PS4-style identifiers inside the source does not by itself mean the script is PlayStation-only.

PlayStation Identifiers Also Cover DualSense

Cronus documentation specifically notes that its PS4 input identifiers also work with the PS5 DualSense controller.

So a GPC using:

PS4_L2

does not mean it only supports an actual DualShock 4.

Xbox Identifiers Cover Series X|S Controllers

Likewise, Cronus documents XB1 identifiers as working with Xbox Series X|S controllers.

A script using:

XB1_LT

or:

XB1_MENU

is not necessarily limited to an Xbox One controller.

Why the Wrong Labels Can Appear After Changing Controllers

Many current NBA 2K27 scripts determine their console mode when the script first initializes.

For example, they may run logic similar to:

On script startup → check console → save Xbox/PlayStation flag

If you change your controller, console configuration or Zen output setup while the same script remains loaded, the displayed platform state may not automatically be recalculated.

Reload the Script After Changing Platform Settings

If you have just changed controllers or Zen configuration:

  1. Switch to another Zen memory slot.
  2. Return to the NBA 2K27 script slot.
  3. Allow its startup screen to finish.
  4. Check the OLED labels again.

This forces scripts that detect the platform during initialization to run their detection logic again.

Restart the Zen If Necessary

If reloading the slot does not refresh the display:

  1. Disconnect from gameplay.
  2. Reconnect the Zen normally.
  3. Reconnect the controller correctly.
  4. Load the NBA 2K27 script again.

Then check the OLED.

Check Zen Studio Output Protocol

If several scripts consistently appear to identify the wrong platform, inspect your Zen configuration rather than editing every script.

The output side of the Zen can affect what platform information the GPC receives.

This matters because many current NBA 2K27 scripts use console detection to select their OLED labels.

Physical Controller and Output Platform Can Be Different

Cronus supports crossover-style controller configurations.

That means the controller plugged into the Zen and the platform connected on the output side do not always have to be from the same controller family.

This is exactly why GPC provides separate:

  • get_console()
  • get_controller()

functions.

Example: Xbox Controller + PlayStation Output

In a crossover configuration:

Physical controller: Xbox

Output platform: PlayStation

A script that checks get_console() can choose PlayStation labels.

A script that checks get_controller() could instead identify the Xbox controller.

Both results can technically be correct—they are measuring different parts of the setup.

Panda Green V4.1 Is Different

Panda Green V4.1 is notable because its current source contains checks involving both:

  • get_console()
  • get_controller()

That gives the GPC access to both pieces of information rather than relying only on the console side.

Not every NBA 2K27 script is structured this way.

Use Zen Studio Device Monitor

If you are unsure whether the issue is only the OLED label or the actual controller input, use Zen Studio's Device Monitor.

Press the relevant controller buttons and confirm the Zen is receiving the expected inputs.

For example, test:

  • LT / L2
  • RT / R2
  • LS / L3
  • RS / R3
  • X / Square
  • A / Cross
  • Menu / Options

If the inputs are registering correctly while the OLED simply uses different names, the issue is likely cosmetic rather than an input failure.

Wrong Labels vs Wrong Controls

What You See Likely Meaning
OLED says L2 but LT works Cosmetic PlayStation label
OLED says Options but Menu works Equivalent platform control
OLED switches correctly after reloading slot Platform detection occurred during initialization
Every script identifies the wrong platform Check Zen/output configuration
Button labels are wrong and inputs do not register Controller/setup issue rather than OLED text only
Only one script has wrong wording Likely fixed text inside that particular GPC

Don't Edit the GPC Just Because the Words Are Different

If your script says L2 while your controller says LT, but the feature works when you press LT, there is usually no functional reason to edit the script.

Simply translate the labels:

L2 = LT
R2 = RT
L1 = LB
R1 = RB
L3 = LS
R3 = RS
Square = X
Cross = A
Circle = B
Triangle = Y
Options = Menu

When Should You Actually Troubleshoot the Controller?

Investigate the controller connection if:

  • Buttons do not register at all
  • The controller disconnects
  • The wrong physical button activates a feature
  • Device Monitor does not show expected inputs
  • Multiple unrelated scripts stop responding correctly

Those symptoms are different from an OLED menu simply using another platform's terminology.

Check Controller Compatibility

If your controller itself is not behaving correctly, see our Controllers Compatible With Cronus Zen guide.

This is especially useful when using crossover configurations or controllers that are different from the console family.

Menu Shortcut Showing the Wrong Platform?

A common example is:

OLED: L2 + Options

while you are using Xbox.

Try the equivalent Xbox controls:

LT + Menu

Likewise, if an Xbox-oriented menu says:

LT + Menu

on PlayStation, use:

L2 + Options

For additional menu troubleshooting, see Cronus Zen OLED Menu Explained.

Settings Page Shows Square but You Use Xbox

Translate:

Square → X

This is especially common on scripts where the menu wording was written around PlayStation controls but the underlying script is intended to work across both controller families.

Settings Page Shows Cross

Translate:

Cross → A

Settings Page Shows Circle

Translate:

Circle → B

Settings Page Shows L3 or R3

On Xbox:

L3 → LS

R3 → RS

The terms describe pressing the left or right analog stick.

Best Troubleshooting Order

  1. Translate the displayed button into the equivalent control for your controller.
  2. Test whether the feature works despite the different label.
  3. Check whether the script automatically changes platform text.
  4. Reload the script slot.
  5. Reconnect the Zen if you recently changed controllers or platform settings.
  6. Check the Zen's output configuration.
  7. Use Device Monitor to verify actual controller input.
  8. Test another NBA 2K27 script.
  9. Only edit or replace the GPC if the issue is genuinely script-specific.

Final Answer

If your NBA 2K27 Cronus Zen script is showing the wrong PlayStation or Xbox buttons, the script is not necessarily malfunctioning.

Many current NBA 2K27 GPCs choose their OLED labels using the connected console rather than the physical controller.

Other scripts only translate some labels, while several still contain fixed PlayStation-style instructions even when used on Xbox.

Start by translating the equivalent controls:

L2/RT? No — L2 = LT.
R2 = RT.
Square = X.
Cross = A.
Circle = B.
Options = Menu.
L3 = LS.
R3 = RS.

If the equivalent button works, the issue is probably only the displayed wording.

If the button itself does not work, reload the script, check the Zen output setup and verify the controller through Device Monitor.

For more help, read our NBA 2K27 Cronus Zen Setup Guide, Cronus Zen OLED Menu Guide, or How to Change Cronus Zen Script Settings.

You can also browse the full NBA 2K27 Cronus Zen script collection.

CzenScripts updates

Get new settings guides first

Receive new script guides, setup updates and CzenScripts releases directly in your inbox.