Cronus GPC Documentation
Cronus CommunityGPC LibraryGPC Guide
  • Welcome
  • Introduction
    • GPC Explained
    • What's New with Zen?
  • Basic Syntax
  • A Simple Tutorial
  • Style Guide
  • GPC Structure
  • Basic GPC Structure
  • Definitions
  • Data Section
  • Remapping
  • Variables
  • Init Section
  • Main Section
  • Combo Section
  • User Created Functions
  • GPC Programming Basics
  • Constants
    • Zen
      • OLED
      • ASCII Constants
      • PIO
    • Keyboard
      • Keyboard
    • Controller
      • Polar
      • LED
      • Rumble
      • PS3
      • PS4
      • XBox 360
      • Xbox One
      • Nintendo WII
      • Nintendo Switch
    • Racing Wheel
      • G29
      • G27
      • G25
      • DF
      • DF GT
      • DF Pro
    • Trace
    • Memory
    • Misc
  • Flow Control
  • Persistent Memory
  • Operator Types
  • Identifiers
  • Functions & Commands
    • Internal Functions
      • Bit Functions
      • Combo Functions
      • Math Functions
      • Device Functions
      • OLED Display Functions
    • Console Functions
      • Core Console Functions
    • Controller Functions
      • Core Controller Functions
      • Rumble Functions
      • LED Functions
    • Keyboard Functions
      • Core Keyboard Functions
  • GPC Examples
    • #1
Powered by GitBook
On this page
  • remap
  • unmap

Was this helpful?

Remapping

PreviousData SectionNextVariables

Last updated 5 years ago

Was this helpful?

Remappings are defined at the beginning of a script and must be done before the main procedure. They cannot be executed during run time.

Command Name

Description

Assigns the value of the controller input to the output

Disconnects an input from the output report

remap

remap assigns the value of the input identifier to the output identifier

remap PS4_CROSS -> PS4_SQUARE;

Although you define remaps at the beginning of a script, the Virtual Machine does not execute the remaps until the main second has finished the current iteration. This means that any scripting operations on the remapped entries for inputs should be programmed for the original buttons and without considering the remapped item.

Syntax

remap < input_identifier > -> < output_identifier >;

Parameters

<input_identifier> : any defined variable. <output_identifer> : index point of the bit to be set with a range of 0 to 15.

Returns

Nothing

unmap

unmap disconnects an input from the output report. This means that although the Virtual Machine can still see the value of the button/axis on the input report, it will not pass its value onto the console in the output report. You can therefore still use an unmapped button to run code or start combos in your GPC script without worrying about its original function being sent to the console.

unmap PS4_TRIANGLE;  // unmaps the PS4_TRIANGLE identifier;
unmap ALL_REMAPS;    // unmaps all controller identifiers which have been remapped;

unmap <output_identifier>;

<output_identifier> : any defined variable.

Nothing

Syntax

Parameters

Returns

🔴
⚪
🔵
🔴
⚪
🔵
remap
unmap