From Dustloop Wiki
Jump to navigation Jump to search

Finding content on Twitter

With the ease of posting videos and discussion to Twitter, it can be helpful to know how to track this information down. Each character in the game has a specific hashtag which people should aim to use when posting tweets for ease of searching. The current list of these hashtags is as follows:

Sol Badguy #GGST_SO
Ky Kiske #GGST_KY
Axl Low #GGST_AX
Chipp Zanuff #GGST_CH
Potemkin #GGST_PO
Faust #GGST_FA
Millia Rage #GGST_MI
Zato-1 #GGST_ZA
Ramlethal Valentine #GGST_RA
Nagoriyuki #GGST_NA
Giovanna #GGST_GI
Anji Mito #GGST_AN
Goldlewis Dickinson #GGST_GO
Jack-O' #GGST_JC
Happy Chaos #GGST_HA
Baiken #GGST_BA
Testament #GGST_TE
Bridget #GGST_BR

Input Shortcuts

Certain specials and Overdrives allow you skip directional inputs for their commands and still execute the attack. Below are the known valid input shortcuts for their usual directional commands (additional directional inputs within the given shortcuts will also work, as long as the minimum inputs as shown in the shortcut are met, e.g. 62146 is valid because 6246 is valid).

Sol performing Heavy Mob Cemetery (214214H) with the input shortcut 2421H
Command Shortcuts
41236 (63214)
  • 4236
  • 4126
  • 4136
236236 (214214)
  • 2626
  • 2623
  • 2636
  • 6246
  • 63146
632147896 (360 motion)
  • 6248
  • 4268

Low-End Considerations

Strive is a graphically-extensive game that will greatly bar out the lower end of older computers, needing much more power as opposed to Xrd just to run minimal settings (seeing as the game usually takes up around 4GB of RAM on its own). There are a few things you can try to alleviate any issues with stability in running the game, but there is only so much you can do before you're out of luck.

Quality 0, looking like blurred pixels. Sometimes, they won't be blurred and actually pixelated, but you don't want to play like this.

Firstly, be sure to set your resolution to lower than the default 1920x1080, such as 1280x720.

As usual, set your graphics setting all to the lowest values/OFF minus the Scaling Resolution and Effect Quality. Lowering Scaling Resolution will severely lower the pixel density of the in-game 3D graphics on your screen to speed things up along and use less power, but obviously this will adversely affect how you view gameplay - while it's still technically playable at 0, you'd have to question your decisions at that point. The minimum you might want to handle is 50, depending on your tastes and tolerance, with 75 being a good mix of seeing what's happening and performance. You'll have to play around with these values and judge it for yourself with screenshots. Note that this does not affect UI elements like text, gauges, buttons, so on.

Lastly, at the time of writing, there seems to be an oversight where not setting your Effect Quality to Best gives a very strange and ugly bloom/lighting effect on characters. However, you do not have to keep the setting at Best! At any point of the game, all you need to do is press Alt and Enter on your keyboard, which will toggle your fullscreen. Do just that and the bloom issues should no longer be present for the game's current session.


Thanks to this article's observation, another step can be made to slightly increase performance of your game. Make sure your game is closed, then navigate to Windows Explorer and type in %localappdata%. Hit enter and it should bring you to a folder called Local. In there, find GGST -> Saved -> Config and lastly open the Scalability.ini file that's in there. Copy and paste the following contents into there, then save the file.




























Next, you probably don't want the game to override these settings if you're satisfied, so right-click the ini, go to Properties, and set the Read-Only flag to checked and confirm it.


Unfortunately, not all stages in Strive are built the same, with some being more hardware intensive than others. This can be very detrimental when playing online with strangers especially if you're on Player 2 side, as having performance issues such as frame drops or lag spikes will leading to high rollback frames or worse the game slowing down. Observations on which stages are more intensive than others can be compared here, so you can use this to tell your friends which stages you can play on better if you're the low-end one out. However, remember that PC hardware is not unified so one stage might not give your PC any problems but it might give someone else's PC problems - these are all relative at best, but stages listed as A-OK should be the least intensive. So if you're experience some form of netplay lag on a specific stage try to check with an FPS counter like the one in the Steam overlay if your PC is running at a completely stable 60 fps and if possible ask the opponent to do the same.

Stage Lagginess
Castle of the Silver Feet Little Lag
Lars Canyon A-OK
Seventh Heaven District A-OK
12-Dimensional Flux Observatory A-OK
Ajatar Hunting Ground Very Laggy
"A Happy Family" A-OK
L'oro Di Illyria Some Lag
Council of Three A-OK
Jellyfish Skyarium Very Laggy
Original Times Square Some Lag
Lap of the Kami Very Laggy
White House Reborn Some Lag

Note: White House Reborn is generally banned in tournament play, because the rubble that spawns after a Wall Break stays on screen for too long, obscuring post-Wall Break interactions.

Using Mods

The Lite version. Part of the stage is still intact, for average computers.
The original edits. The stage is destroyed and should no longer pose a threat to your potato.

Thankfully, modders have jumped into action to customize things like audio, models, and textures, but fortunately this also gives a possibility of fixing the offending stages for low-end setups. Using the following mods created by DraftFGC, much of the resource-hogging models on stages will be removed and not be rendered, which is a better visual alternative to completely removing all of the stage's characteristics.

  • The first set of removals are here, which are collective and also remove skies and Character Selection Screen assets. Individual and manual downloads (without those extreme edits) can be found in this MEGA folder. For if Lite really doesn't fix it - this should do the job.

After downloading the stages you've chosen, to manually install these mods, follow these steps:

  • Navigate to C:\Program Files (x86)\Steam\steamapps\common\GUILTY GEAR STRIVE\RED\Content\Paks\ (whichever drive/directory your game is saved in)
  • In the Paks folder, make another folder called ~mods
  • Extract and drop your downloaded contents into that folder and test in-game (in other words, you should have Paks/~mods/*.pak and *.sig).

You should no longer have to worry about fighting strangers or asking people to swap stages with these mods. Unfortunately, though, if your game is still having issues running even after all these steps, then there likely isn't any more you can do aside from upgrading your setup.

Training Mode Shortcuts

Direction + Reset
Left + Reset to reset both characters to the left corner. (P1 in the corner)
Right + Reset to reset both characters to the right corner. (P2 in the corner)
Down + Reset to reset both characters to round start position.
Up + Reset to reset both characters to the previous starting position with their player sides switched.
Play + Record = Reset
Pressing both Play and Record at the same time is the same as pressing the Reset button.

Technical Calculations

These are not required to utilise game mechanics, but these sections further elaborate on the mathematical calcuations for various system mechanics, which are otherwise too complex for their respective sections.

Base R.I.S.C. Gain

Base R.I.S.C Gain is tied to Attack Level, using the formula:

(5 + 5 × Attack Level) ÷ Number of hits × 100

  • While values are normally rounded down before the ×100 multiplier, they will instead round up to 1 if the result is lower than 1.
  • Projectiles ignore Attack Level for their base R.I.S.C. Gain, acting like Level 0 attacks regardless of their actual level.
  • A fully charged Dust Attack functions like a Level 4 for the opponent on block despite being Level 2, including R.I.S.C. Gain.
  • R.I.S.C. Gain is reduced by 25% if the blocked attack is a low or an overhead.

R.I.S.C. Damage Reduction

When striking an opponent with a negative R.I.S.C. Level, the output damage is reduced. This is colloquially known as "combo scaling".

As a first approximation, take the table below, and see the "percentage" column - that is how much the damage is scaled for respective R.I.S.C. Level.

R.I.S.C. Level Factor Percentage
-100 256 100.00%
-1700 200 78.13%
-3300 152 59.38%
-4900 112 43.75%
-6500 80 31.25%
-8100 48 18.75%
-9700 32 12.50%
-11300 16 6.25%
-12900 8 3.13%

The exact math is as follows:

  1. Find the two closest R.I.S.C. Level values in the left column of the table above, look up the corresponding values in the factor column.
  2. Do the linear interpolation between the values obtained; round down to nearest integer.
  3. Multiply the base attack damage by the number obtained, then divide by 256 and round down.
  4. The result would be the damage taken by your opponent.
Example, in prose
Let's say we are landing a 30 damage attack on an opponent with a R.I.S.C Level of -4000.

The two closest R.I.S.C. Level values in the table above would be -3300 (factor of 152) and -4900 (factor of 112). For simplification purposes, the negatives can be omitted. We then do the linear interpolation of the two (i.e. "finding the average of the values, accounting for the proximity", roughly) as follows:

 factor_a + (factor_b - factor_a) * (risc - risc_a) / (risc_b - risc_a)
 = 152 + (112 - 152) * (4000 - 3300) / (4900 - 3300)
 = 152 + (-40) * 700 / 1600
 = 152 - 17.5
 = 134.5

Round it down, getting 134; and get the final answer as 30 * 134 / 256 = 15.7 = (rounding down once more) = 15 damage.

 fn scale_attack(attack_damage: int, risc: int)
   if(risc >= 0) {return attack_damage;}  // positive risc does not affect damage at all
   if(risc >= -12800) {risc = -12800} // can't go lower than this
   risc = abs(risc); // flip the sign so it's easier to work with
   // table from above, with sign flipped
   let risc_factor_table = {100: 256, 1700: 200, 3300: 152, 4900: 112, 6500: 80, 8100: 48, 9700: 32, 11300: 16, 12900: 8}; 
   let risc_ordinal = floor((risc - 100) / 1600);
   let risc_lower = risc_ordinal * 1600 + 100;
   let risc_upper = (risc_ordinal + 1) * 1600 + 100;
   let factor_lower = risc_factor_table[risc_lower];
   let factor_upper = risc_factor_table[risc_upper];
   // linear interpolation
   let factor_interpolated = factor_lower + floor((factor_upper - factor_lower) * (risc - risc_lower) / (risc_upper - risc_lower));
   let out_damage = floor(attack_damage * factor_interpolated / 256);
   return out_damage

Dash Acceleration

For each frame a dash is held (excluding Leo, Giovanna, and I-No's unique dashes), the dash speed will be:

vₙ₊₁ = vₙ + Acceleration - (vₙ/Friction)


  • vₙ is the current speed
  • vₙ₊₁ is the speed next frame
  • Acceleration is the character's base acceleration
  • Friction is the character's base friction value
  • v cannot exceed 38.5
  • The value in ⌊ ⌋ is rounded down to the nearest 0.001

Initial dash speed is the value of v when n=0, therefore frame 1 will always be slightly faster. For the sake of calculation, friction is inverse, a higher value maintains speed, while a lower value loses acceleration quicker.

Due to rounding and the mechanics of friction there is no simple way to estimate speed from an arbitrary frame, without calculating the entire series.

Additional Data Charts

6P Values

6P Values

chara startup active recovery onBlock onHit invuln
chara startup active recovery onBlock onHit invuln
Anji Mito 10 6 25 -17 1-3 Upper Body
4-15 Above Knees
Axl Low 12 5 18 -13 +2 1~4F Upper Body
5~12F Above Knees
Baiken 9 5 19 -10 -7 1-3f Upper Body
4-13f Above Knees
Bridget 10 6 20 -12 -9 1~3 upper body, 4~15 above the knees
Chipp Zanuff 9 5 25 -16 -13 1~2F Upper Body
3~13F Above Knee
Faust 9 3 32 -21 KD 1-4 Upper Body
5-11 Above Knees
Giovanna 12 8 15 -9 KD 1~4 Upper Body
5~19 Above Knees
Goldlewis Dickinson 12 6 27 -19 -16 1~2 Upper Body
3~17 Above Knees
Happy Chaos 9 5 25 -16 -13 1~3 Upper Body
4~13 Above Knees
I-No 9 5 18 -9 -6 1-2 Upper Body
3-13 Above Knees
Jack-O 10 6 20 -12 KD 1~1 Upper Body
2~12 Above Knees
Ky Kiske 9 5 17 -8 -5 1-3f Upper Body
4-13f Above Knees
Leo Whitefang 10 5 18 -5 1-2 Upper Body
3-14 Above Knees
May 12 6 18 -7 KD 1-3 upper body
4-17 above knees
Millia Rage 9 9 16 -11 -8 1-2F Upper Body
3-11F Above Knee
Nagoriyuki 12 5 15 -6 -3 1~3F Upper body
4~17F Above Knee
Potemkin 11 7 25 -15 SKD (+29) 1 ~ 4F Upper Body
5 ~ 17F Above Knees
Ramlethal Valentine 9 5 18 -9 -6 1-3 Upper Body
4-13 Above Knees
Sol Badguy 9 5 20 -11 KD (+24) 1~2F Upper Body
3~13F Above Knees
Testament 11 6 15 -7 KD 1~3 Upper Body
4~17 Above knees
Zato-1 12 8 12 -6 KD 1 ~ 3 Upper Body
4 ~ 15 Above Knees

Reversal Values

Reversal Values

chara input startup active recovery onBlock onHit invuln
chara input startup active recovery onBlock onHit invuln
Anji Mito 632146S Total 40 1-30 Guard
Axl Low 236236H 11+1 8(24)13 26 -2 HKD 1~15F All
Chipp Zanuff 623S 9 20 23 -27 KD 1~10 Strike
Faust 632146H 16+5 3 48 -32 HKD 1~23 Full
Giovanna 632146H 5+4 4(4)4(4)4(4)4(4)7 49 -37 HKD 1~10F Full
Goldlewis Dickinson 632146P 6+(135 Flash)+4 5 46 -33 1~14 All
Goldlewis Dickinson 720P 11+(191 Flash)+4 5 46 -33 1~19 All
Goldlewis Dickinson 1080P 16+(230 Flash)+4 5 46 -33 1~24 All
I-No 632146S 7+2 4 (42) 9 13 +26 Full F1~11
Jack-O 632146P 10+1 2 58 - HKD All 1~12F, Throw 1~55F
Ky Kiske 623S 11 4 43 -33 KD (+22) [+34] 1-14f Strike
Ky Kiske DI 623S 11 4 43 -26 KD (+26) 1-14f Strike
Ky Kiske 623H 13 8 44 -38 KD (+21) [+37] 1-16f Strike
Ky Kiske DI 623H 13 6 39 -22 KD (+37) 1-18f Strike
Ky Kiske 632146H 8+1 3×4(20)2 99 -82 HKD (+20) 1-10f All
Ky Kiske DI 632146H 8+1 2×8(20)2×3 99 -79 HKD (+26) 1-15f All
Leo Whitefang [2]8S 9 3,12 33 -28 1-9 Strike
Leo Whitefang [2]8H 10 3,12(10)5 42 -52 1-10 Strike
Leo Whitefang 632146H 10+1 8(15)12(13)8(10)8(44)6 43 -33 1-18
May 632146H 6+4 12(22)10 55 -21 HKD 1~21 Full
Millia Rage 236236S 4+5 till corner Total 43 +8 HKD 9-26F Airborne
Nagoriyuki 632146S 7+(173 Flash)+2 2 54 -37 HKD 1~10F Full
Nagoriyuki 632146H 11+(58 Flash)+10 6 80 -66 HKD 1~26F Full
Potemkin 236236S 12+0 15 16 N/A KD 1 ~ 12F Full
Ramlethal Valentine 236236S 7+2 6 51 -38 [-38] {-43} KD All 1~14
Sol Badguy 623S 9 14 18+10 after landing -28 KD (+17) 1~11F Strike
Sol Badguy 623H 13 5, 11 19+10 after landing -26 KD (+18) [HKD (+54)] 1~14F Strike
Sol Badguy j.623S 9 9 Until landing+10 KD 1~10F Strike
Sol Badguy j.623H 13 5, 11 Until landing+10 KD [HKD] 1~14F Strike
Sol Badguy 632146H 7+2 3(20)20 41 -44 HKD (+19) [HKD (+49)] 1~8F Full
Testament 236236K 11+4 5 67 -67 HKD 1~19F Full