{"id":913,"date":"2026-06-08T20:09:20","date_gmt":"2026-06-08T20:09:20","guid":{"rendered":"https:\/\/rivals2.com\/workshop-dev\/?post_type=knowledgebase&p=913"},"modified":"2026-06-17T16:38:13","modified_gmt":"2026-06-17T16:38:13","slug":"setting-up-a-throw","status":"publish","type":"knowledgebase","link":"https:\/\/rivals2.com\/workshop\/knowledge-base\/character-creation\/setting-up-a-throw\/","title":{"rendered":"Setting Up A Throw"},"content":{"rendered":"\n

Setting up throw data<\/h2>\n\n\n\n

This setup applies to any attacks that move the opponent before throwing them.<\/p>\n\n\n\n

    \n
  1. Open up the throw’s attack data.<\/li>\n\n\n\n
  2. In the “Throw Data” section of the attack data, you’ll need to fill out the following fields:\n
      \n
    • Release Offset – Determines the location that the opponent will be teleported to when released.<\/li>\n\n\n\n
    • Release Window String Table Key – The opponent will be released from the throw on the first frame of this window.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
    • There are two types of throws: hitbox throws and non-hitbox throws. Hitbox throws spawn a hitbox when the opponent gets released, applying hitpause like a normal hitbox. Non-hitbox throws instantly release the opponent with no hitpause.\n
        \n
      • For hitbox throws, you can leave the “Throw Knockback Data” section empty. Instead, you will add a hitbox to the release window like a normal attack.<\/li>\n\n\n\n
      • For non-hitbox throws, fill out the “Throw Knockback Data” section with the desired knockback properties.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
      • Add an entry to the “Thrown Animation Data” array.\n
          \n
        • Note: Without thrown animation data, the opponent will not be moved by the attack.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
        • The first entry in the thrown animation data should have the “Anim Start Window String Table Key” set to the first window that the opponent will be grabbed in, and the “Anim Start Window Frame” should be zero.\n
            \n
          • For normal throws, it should be the first startup window name.<\/li>\n\n\n\n
          • For command grabs, it should be the name of the window that the character transitions into on a successful grab.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
          • Set the “Thrown Animation” field according to the animation you want the opponent to play when the throw first starts.\n
              \n
            • Descriptions of each option can be viewed by hovering over them.<\/li>\n\n\n\n
            • Thrown animations play at 60 frames per second and do not loop.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
            • Optional: Add more entries into the “Thrown Animation Data” array.\n
                \n
              • When your character reaches the “Anim Start Window Frame” in the window specified by the “Anim Start Window String Table Key”, the opponent’s animation will instantly change to the newly specified animation.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n

                Authoring a throw animation<\/h2>\n\n\n\n

                Consider the Existing Thrown Reactions<\/h3>\n\n\n\n

                When concepting throw animations for your character, consider creating throws that can work with the existing library of thrown reaction animations. See what reactions are available and create your throw with those reactions in mind.<\/p>\n\n\n\n

                Creating the Throw<\/h3>\n\n\n\n

                In the game, the opponent will follow the Grab_M bone. This bone is highly recommended to be left alone at first as any changes to the throwing animation would result in Grab_M needing adjustments.<\/p>\n\n\n\n

                Here is the recommended workflow:<\/p>\n\n\n\n

                  \n
                1. Animate the throwing character\n
                    \n
                  • Animate and adjust posing and timing as needed.<\/li>\n\n\n\n
                  • Test the animation in the game and repeat the step above if needed until the throwing characters looks good.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                  • Animate the Grab_M bone\n
                      \n
                    • This bone is often animated frame by frame to achieve the desired opponent movement.<\/li>\n\n\n\n
                    • It is common for this bone to make big jumps over a frame in order to move the opponent correctly when switching between thrown states. For example, Wrastor’s BThrow jumps from Grounded Resist, to Back First, to Slam Front.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                    • Set up the proper reactions and timing in the throw’s attack data\n
                        \n
                      • Find “Thrown Animation Data” in the throw’s attack data and add an element using the + sign.<\/li>\n\n\n\n
                      • Specify which attack window needs to play a Thrown Animation and on which frame the animation should start.<\/li>\n\n\n\n
                      • Add as many elements and reactions as needed.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                      • Did everything work perfectly?\n
                          \n
                        • Probably not! That’s ok. This is a meticulous process.<\/li>\n\n\n\n
                        • Make adjustments following the previous steps while going frame by frame to ensure the opponent is reacting as desired.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n

                          <\/p>\n","protected":false},"excerpt":{"rendered":"

                          Setting up throw data This setup applies to any attacks that move the opponent before throwing them. Authoring a throw animation Consider the Existing Thrown Reactions When concepting throw animations for your character, consider creating throws that can work with the existing library of thrown reaction animations. See what reactions are available and create your […]<\/p>\n","protected":false},"author":8,"featured_media":0,"comment_status":"open","ping_status":"open","template":"","knowledgebase_cat":[4],"knowledgebase_tag":[],"class_list":["post-913","knowledgebase","type-knowledgebase","status-publish","hentry","knowledgebase_cat-character-creation"],"_links":{"self":[{"href":"https:\/\/rivals2.com\/workshop\/wp-json\/wp\/v2\/knowledgebase\/913","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\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/rivals2.com\/workshop\/wp-json\/wp\/v2\/comments?post=913"}],"version-history":[{"count":10,"href":"https:\/\/rivals2.com\/workshop\/wp-json\/wp\/v2\/knowledgebase\/913\/revisions"}],"predecessor-version":[{"id":1490,"href":"https:\/\/rivals2.com\/workshop\/wp-json\/wp\/v2\/knowledgebase\/913\/revisions\/1490"}],"wp:attachment":[{"href":"https:\/\/rivals2.com\/workshop\/wp-json\/wp\/v2\/media?parent=913"}],"wp:term":[{"taxonomy":"knowledgebase_cat","embeddable":true,"href":"https:\/\/rivals2.com\/workshop\/wp-json\/wp\/v2\/knowledgebase_cat?post=913"},{"taxonomy":"knowledgebase_tag","embeddable":true,"href":"https:\/\/rivals2.com\/workshop\/wp-json\/wp\/v2\/knowledgebase_tag?post=913"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}