{"id":564,"date":"2026-06-04T20:03:44","date_gmt":"2026-06-04T20:03:44","guid":{"rendered":"https:\/\/rivals2.com\/workshop-dev\/?post_type=knowledgebase&p=564"},"modified":"2026-07-17T19:31:31","modified_gmt":"2026-07-17T19:31:31","slug":"playtesting","status":"publish","type":"knowledgebase","link":"https:\/\/rivals2.com\/workshop\/knowledge-base\/getting-started\/playtesting\/","title":{"rendered":"Playtesting"},"content":{"rendered":"\n

Playtesting your work as quickly as possible is critical for making progress, this page aims to explain the methods available for playtesting your content in the workshop.<\/p>\n\n\n\n\n\n\n\n

IMPORTANT: In order to playtest your character in the editor, you must be signed into steam, and steam must be running in the background, or else the editor will crash.<\/mark><\/p>\n\n\n\n

Playtest Through Modding UI<\/h3>\n\n\n\n
\"\"<\/figure>\n\n\n\n

If you have already created a character mod you can right click on your character icon in the modding UI and select Playtest in DebugRoom<\/strong> to quickly load the Debug Room Level and play with the selected mod character as player 1.<\/p>\n\n\n\n

Playtest Through Main Menu (Boot Level)<\/h3>\n\n\n\n

The workshop always launches with the BootLevel loaded by default, that is the black screen in your level viewport and it is responsible for loading the main menu of the game.<\/p>\n\n\n\n

You can quickly load this level at any time by clicking Modding in the top toolbar and selecting Load BootLevel<\/strong><\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
click the green arrow to launch the game from the currently loaded scene<\/figcaption><\/figure>\n\n\n\n

Clicking play while in the bootlevel will launch the game in editor (This is called Play In Editor or PIE mode) via the main menu. From here you can select local mode (Versus or training).<\/p>\n\n\n\n

Be sure to connect any controllers you wish to use before clicking play, in PIE mode controllers will auto bind in the order they were touched after the game starts. Sometimes if a controller is connected after Unreal is launched you may need to restart the editor before Unreal will register it.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

On the Character Select Screen <\/p>\n\n\n\n

    \n
  1. Activate workshop mode with the toggle in the top right<\/li>\n\n\n\n
  2. Select the workshop Character Option in the center of the portraits<\/li>\n\n\n\n
  3. In your player slot the currently loaded mod characters will be listed. If you do not see your character here you may need to stop playing in Editor, go to the character data (CD_ file) blueprint file for your mod and open it to force Unreal to load it, then try launching the game again.<\/li>\n<\/ol>\n\n\n\n

    Playtest Though Rivals Developer Settings<\/h3>\n\n\n\n

    The Rivals Developer Settings menu will allow you to customize your play test scenario. You can choose any stage, the number of players and which character is selected per slot, set up CPU levels, stock counts and more.<\/p>\n\n\n\n

    \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

    Open the Modding menu on the Menu Bar at the top and click Open DebugRoom to load a lightweight stage perfect for quickly play testing your content.<\/p>\n\n\n\n

    \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

    Alternatively press Ctrl+O or click File\/Open in the menu bar to bring up the open level menu and navigate to any of the folders in
    Content\/Maps\/GameplayLevels\/<\/strong> and double click the gameplay level asset within to open that level in order to playtest on specific stages.<\/p>\n\n\n\n

    In order to playtest this way you will need to first set up the playtest settings in the Rivals Developer settings menu located under editor preferences.<\/p>\n\n\n\n

    \"\"
    Click Edit on the toolbar at the top and click Editor Preferences<\/figcaption><\/figure>\n\n\n\n

    In the menu bar click Edit – Editor Preferences<\/strong>, then when the preferences window opens click on Rivals Developer Settings in the left hand column.<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    This will load the Rivals Developer settings on the right column allowing you to setup various playtest scenarios. By default no players will be present and the game will not load.<\/p>\n\n\n\n

      \n
    • Palette Choices – This is where you choose which character is loaded per player. Click the plus to add players to the list, each list item allows you to select a specific character skin palette. Mods that you create will appear in the dropdown list for these entries.<\/li>\n\n\n\n
    • Debug Stock Settings – How many stocks to start with, 0 is infinite.<\/li>\n\n\n\n
    • Respawn Platforms – Choose which respawn platform each player is using, default if no entry added.<\/li>\n\n\n\n
    • Death Effects – Choose which death effect each player is using, default if no entry added<\/li>\n\n\n\n
    • Critical Hit Data – Choose which Critical Hit each player is using, default if no entry added.<\/li>\n\n\n\n
    • CPU Level – Choose the CPU level (0 is a dummy, -1 is a human player controllable by device input)<\/li>\n\n\n\n
    • Training Mode – Leave this on for access to save states, hitbox display and other features.<\/li>\n\n\n\n
    • Doubles – Activates Doubles Mode<\/li>\n\n\n\n
    • Team Attack – Allows team mates to attack each other.<\/li>\n<\/ul>\n\n\n\n

      Audio Debug<\/p>\n\n\n\n

        \n
      • Mute BGM in Editor – Background music will not play while playtesting.<\/li>\n\n\n\n
      • Debug Menu Audio <\/li>\n\n\n\n
      • Enable Workshop<\/li>\n<\/ul>\n\n\n\n
        \"\"
        Tip: It can be helpful to dock the editor preferences in a tab next to the viewport for quick access to these settings<\/figcaption><\/figure>\n","protected":false},"excerpt":{"rendered":"

        Playtesting your work as quickly as possible is critical for making progress, this page aims to explain the methods available for playtesting your content in the workshop.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","template":"","knowledgebase_cat":[3],"knowledgebase_tag":[],"class_list":["post-564","knowledgebase","type-knowledgebase","status-publish","hentry","knowledgebase_cat-getting-started"],"_links":{"self":[{"href":"https:\/\/rivals2.com\/workshop\/wp-json\/wp\/v2\/knowledgebase\/564","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rivals2.com\/workshop\/wp-json\/wp\/v2\/knowledgebase"}],"about":[{"href":"https:\/\/rivals2.com\/workshop\/wp-json\/wp\/v2\/types\/knowledgebase"}],"author":[{"embeddable":true,"href":"https:\/\/rivals2.com\/workshop\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/rivals2.com\/workshop\/wp-json\/wp\/v2\/comments?post=564"}],"version-history":[{"count":19,"href":"https:\/\/rivals2.com\/workshop\/wp-json\/wp\/v2\/knowledgebase\/564\/revisions"}],"predecessor-version":[{"id":1688,"href":"https:\/\/rivals2.com\/workshop\/wp-json\/wp\/v2\/knowledgebase\/564\/revisions\/1688"}],"wp:attachment":[{"href":"https:\/\/rivals2.com\/workshop\/wp-json\/wp\/v2\/media?parent=564"}],"wp:term":[{"taxonomy":"knowledgebase_cat","embeddable":true,"href":"https:\/\/rivals2.com\/workshop\/wp-json\/wp\/v2\/knowledgebase_cat?post=564"},{"taxonomy":"knowledgebase_tag","embeddable":true,"href":"https:\/\/rivals2.com\/workshop\/wp-json\/wp\/v2\/knowledgebase_tag?post=564"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}