In a nutshell, RNG in SIFAS works like this: A random number from 0 to 100 is generated. If the number is smaller or equal to the chance, the Skill procs (for example, 33 for the Tap Skill of most URs, plus whatever skill chance buffs are active). These random numbers are generated as a chain, which you can imagine as a list: The RNG delivers a list full of random numbers, and every time a Skill is checked for a proc, a number is taken out of it, and compared to the Skill's chance.

This is what you call a sequence - basically, an infinite queue of randomly generated numbers. In SIFAS, each card has their own sequence like that, and it's only used for Skill proc checks on that one card: each time, the first number from the sequence is removed, used for the check, and the next number in the queue is now at the front, ready for another check. This is also called “consuming” a number from the sequence.

In order to keep players from restarting songs over and over hoping for better luck, the generated lists will always be the same for a Live attempt - so if you reset by quitting the app and resume, the queue will spit out the same numbers. That means each card will always receive the same chain of numbers between 0 to 100, and will generally proc its Skills in the same moments if you play the Live the same way as before.

But this is where RNG manipulation is possible: since you will always get the same sequence, you can try to collect information about the numbers in the list over multiple resets, and then change when they are consumed. This way, you can try to have the Skill checks you want to succeed consume the correct numbers.

This guide will go over two examples: one to show how exactly the approach works, trying to go for a single early proc, and a second one applying the approach to an entire Live, showing you how to get as much information as possible about your run's sequence and plan out an optimal run regarding one unit's Skill.

One note before we start: RNG manipulation can only try to move around lucky numbers, but can't get new ones out of nowhere. If you're really unlucky and your sequence is just all numbers greater than 70, no amount of manipulation can help there. The generated numbers will always be the same and can't be changed. Luck still plays a part in your attempts: RNG manipulation isn't a way to make a good run out of a bad run. Instead, it's a way to push good RNG just a little bit further, to get the most of a run with already above average luck - so always run through the Live first as usual to see whether it's even worth it to attempt manipulation.

In this example, let's assume we have a card with a Cleanse Live Show AbilityLive Show Ability: The second Ability of a Card., assigned to the Blue Strategy, that procs with 30% chance on a Strategy switch. Our scoring team is in the Red Strategy, and because you start in the Green Strategy, the goal is to get to Red as fast as possible with a Cleanse proc.

The tables will show the numbers I picked randomly to act as the sequence this example is using, but we'll also be noting down what information we would actually know about the sequence as a player at that point. Right now, we have no idea what our sequence looks like - so we'll have to give the Live a play to see what we can learn.

The first instinct is to just switch to Red and hope for a first-switch Cleanse, and if it doesn't, just go back and forth between Green and Red until it does. For this example we won't get a proc on the first switch: the Skill proc check will consume the number 42.61, and that number is bigger than the Skill's proc chance (30%). The same happens for the second and third switch. We do finally get a Cleanse on the fourth switch, as 13.46 is less than 30. However, that means we are in the Green strategy at this point - so we need one more switch to get back to Red, and that one procs the Ability too. In total, we need 20 notes to arrive in Red without debuffs.

So, what information did we get? Each switch consumes one number from the sequence to check whether the Cleanse Ability procs. Based on whether the Skill procced or not, we know in what range the consumed number is: because the Skill's chance is 30%, the consumed number must be greater than 30 if the Skill failed to proc, and 30 or less if it did. With this knowledge, we can now reset the run - we'll get the same sequence, and can try to get to the low numbers sooner to get an earlier cleanse.

As mentioned before, in order to change the outcome of the RNG, we need to change how the sequence is consumed. We need to have more Skill proc checks on the cleanse card to get rid of the high numbers, so that a switch can consume the low number. All Skills consume a number to check for a proc if their trigger is activated - that includes the Tap Skill, all Insights, Live Show Abilities and the Skills of Accessories. The easiest one of those to control is the Tap Skill, so let's focus on that one for now.

Instead of going to Red, we'll switch to the Blue Strategy to allow our Cleanse card to appeal. This also consumes the first number as before, so now we need to consume two more numbers before the low enough number is at the front of the sequence ready for the switch to take. So we just tap two rounds, which means the Tap Skill is checked for proc twice. As a small extra, the Tap Skill does proc on the second tap, because the 32.11 is consumed here which is less than 33. We get even more information about the sequence that way: if the Tap Skill procs, the number must be 33 or less, but since the same number didn't proc the Cleanse Ability on the switch in the previous run, it must be higher than 30 - so the number must be between 30 and 33!

After two taps, a total of three numbers have been consumed - next up in the sequence is the number that we already know is 30 or less, and guaranteed to proc the Cleanse Ability. So if we switch to Red now to trigger the Skill, the proc check is executed, the small number is consumed for it, and we get a Cleanse on the second switch.

This is the basic idea behind manipulating any seeded RNG like this: find out what numbers are in the sequence, then change how numbers are consumed to match up good numbers with checks you want to succeed. For an actual manipulation in a run though, you wouldn't try to find out the actual numbers like this. Instead, you would watch a Skill with a similar chance as the one you want to proc, and mark the elements of the sequence where that comparison Skill procs. These marked elements are potential moments where you could also proc the desired Skill, so you can focus on making the target Skill do its check on these values - like in the next example.

In this example, we'll try maximizing the use of an CSp SR Kanan Guest, and try to proc her Live Ability as many times as possible. The first thing we'll have to note is that because of how Guests work, the card in the center position of our Formation will inherit the Guest's Abilities. That means our Center owns the SP Fill Ability we want to proc, and it will consume the Center's sequence, along with all the other Skills that already consume it.

Again, we will need to get some information about what the center's RNG sequence looks like to be able to do manipulation. Luckily, the chance for Kanan's SP Fill Ability is pretty close to the usual Tap Skill chance (30% vs 33%), so we can use Tap Skill procs as a guide: if there is a number in the RNG sequence low enough to proc the Tap Skill, there's a good chance it will also proc the SP Fill Ability. (However, it should be noted that Skill Chance buffs only increase the proc chance for the Tap Skill, not any other Skills, so that gap might widen.)

The first step is to play through the song once - without using any SPs, to avoid meeting the condition on Kanan's Skill, which would change how the RNG sequence is consumed - while writing down on which notes the Tap Skill of our center procs. As before, for this example, we'll just randomly pick some numbers.

We’re taking a slightly different approach to writing down the sequence here: instead of writing down the possible range of each element, we just record candidates - notes at which the RNG sequence delivers a number low enough to possibly be useful.

With this, we have a list of at which points a Tap Skill check consumes a number that procs it - we know that at these notes, the value taken from the RNG sequence is 33 or less. That also means that, since these taps are the ones consuming that number, the low number is sitting in front of the queue between notes 9 and 12. With this information, we can “steal” this number for our Kanan SP Fill Ability check. By using the SP Skill between notes 9 and 12, a Skill proc check is executed on the Ability, which takes the number that note 12's Tap Skill check would have usually gotten - we're stealing the proc from the tap, and hopefully it's low enough to proc the SP Fill Ability.

Let's find where the first possible proc is. At each note in the list, we can attempt to steal the proc as described above, so let's try from the top - we'll assume we are loaded with Crown and Piano, and we do have an SP Skill ready at note 12. Before we hit note 12 and our center would proc their Tap Skill, we use the SP Skill, to make Kanan's Ability consume the low number from the sequence. Two things can happen now: it is possible that the SP Fill does not proc, because the number is lower than 33, but higher than 30. In that case, we reset the run, and try the next note instead, so note 15 in this case. In case it does proc, we're successful! For our example, we'll assume that we have gotten a proc on that tap - so we used our SP Skill after we hit note 12, the Ability check consumes the value that note 15 would have usually used, and procs the SP fill.

Due to using the SP Skill, we've now had one extra Skill proc check consuming a number the sequence - so we now need to adjust our list. Because one extra value has been taken from the sequence after this SP, all Tap Skill proc checks will now get the RNG number that the tap before them got. So for example, if note 30 procced the Tap Skill with 0 SPs, after that one extra value was consumed, note 27 will instead get that number and proc the Tap Skill there.

To keep track of it, we add a column on our table, with all procs moved ahead by one Skill check. However, we also have to strike a few numbers because of the Guest Ability cooldown. We have used the SP Skill that procced the Ability after note 12, so the earliest possible next proc is after note 42 - we can ignore all taps before that. (The Skill proc check for the Guest Ability is also not executed while in cooldown. If you use an SP during that time, no extra value from the RNG sequence is consumed, so you can double SP to your heart's content.)

We can easily see our earliest chance to get another Ability proc is at note 51, so now, we can proceed just like before. Use an SP Skill between notes 48 and 51, and see whether it procs - if not, reset and try the next, otherwise, add another column, moving everything ahead by three and striking all notes before the Guest Ability cooldown. Once more as an example, we'll see how it looks if we use SP after note 48, stealing the proc from the tap on note 51, proccing the Ability…

…and try again, starting from note 84. Like this, we can create a table of all possible Ability proc spots across the entire Live, which we can use as a map to plan out paths through the song for optimal SP filling. These are obviously just possible procs - some of the numbers you'll get from the sequence will be not low enough for Kanan's ability, so get ready for a lot of resetting and experimenting, removing taps that don't work out from the list and trying out even more paths. You'll want the path that gives you the most Ability procs, but you'll also want to avoid long streaks of unlucky numbers keeping you from proccing, and not waste your Bracelet fills on ACs - but if you got lucky with your sequence numbers, you might just find the path that gives your run the edge you need for VolRan.

Of course, making this map is not always that simple. Now that we are looking for procs across the entire Live, other sources of Skill proc checks can become a problem. If the Center has any other Skills that can proc on triggers like AC Clear, SP Skill or on Crit, no matter whether it’s their Live Show Ability, an Insight or an Accessory - they can heavily influence when numbers are consumed, and you'll have to consider those in such a table as well and keep track of where the sequence is moving. Make sure you always have an overview of all Skills using the sequence, and consider every proc check that is executed.

In addition to the per-card Skill RNG sequences, the game has three more RNG generators shared across all cards. These are the Critical RNG, used to check whether a tap should proc as a Crit, the Strategy Switch RNG, used to choose which Switch Bonus is procced, and a general RNG without any label used for an unknown purpose.

The Critical RNG probably works similar to the Skill RNG: a number between 0 to 100 is generated, and each note will consume one value from the sequence. The consumed value is compared with the current card’s Critical chance. If it is smaller, the Appeal becomes a Critical. Critical RNG can be manipulated in two ways.

• Use Strategy switches to get off the usual cycle. As long as the sequence consumption itself is not changed, a note will always have the same chance requirement - so if you can change your Strategy's cycle, you might be able to match up cards with higher Technique with the notes with higher requirements, and end up hitting more Critcals.
• The Critical RNG sequence is not consumed when missing a note. That means missing some notes before a Critical AC can move the sequence and result in the lower requirement notes landing in the AC, meaning that you can hit more crits to clear it.

The Strategy Switch RNG is simply a sequence of the numbers 1, 2 and 3, and whenever you switch, a number is consumed, and the card at that position in the switched-to Strategy will use its Switch Bonus. Some manipulation is possible, since that means only the amount of switches matters, not the timing: for example, if you switch to the green Strategy for the first switch of a run, and it procs the Switch Bonus of the first card in that Strategy, it means the first switch will always proc the Switch Bonus of the first card in the other Strategy. So you could for example reset and switch to the blue Strategy instead, if you can make better use of the Switch Bonus of the first card in that one, and it doesn't matter when you do that switch.

Some small details on when numbers are consumed from the Skill sequence, which you need to consider when mapping out RNG:

• All Skills use the card's Skill RNG sequence - that includes Tap Skill, Abilities, Insights, Accessories and inherited Guest Abilities.
• Guaranteed Skills (100% chance) still consume a number from the sequence.
• Conditions are checked after the proc check. This means a Skill will always consume a number from the RNG sequence if its trigger is activated, even if other conditions do not apply. This includes:
  • The activation limit of a Skill. For example, EGd Fes Kanan (Live Ability: DR on Switch, up to 2 times) will execute a proc check for all Strategy Switches, including the third switch or later.
  • Any minimums, like “80% Stamina or lower”, are also conditions. If the condition is not met, the Skill will never use its effect, but the proc check still uses RNG.

Since Skill conditions are not checked until after a number from the RNG sequence is consumed (as described above), Skills that trigger as often as possible can be used to consume extra sequence values and increase chances of finding favorable values. This involves adding Active Insights to units that need RNG cycling. Insights with triggers such as “When Stamina hits 80%” or “When Voltage reaches 30% of Target” check for procs on every Stamina/Voltage change - so, pretty much every note. This allows consuming an extra value for every note tapped.

Common Insights to use as RNG cycling Insights are the various kinds of “Appeal+ [M]: On 30% Clear (Voltage)” (“アピール＋ [中]:30%達成時”) Insights, which drop from a Dance/Dance/Push-Ups combination. These Insights trigger every time Voltage is gained, no matter whether they are on the Frontline or Backline, and will add a 2% Appeal buff to Strategy/Type/Group/… when it procs for the first time. However, any Insight with this trigger will have the same effect, if you can manage to get one dropped, for example from Running or Swimming.

The main use for this approach is to allow a card to move through its RNG sequence while in an inactive Strategy. Being able to consume more values from the RNG sequence faster means you can “see” more values in a single Live, which means it is possible to find more favorable values, which in turn means RNG manipulation becomes even more powerful as it can be used to proc even more Skills. Outside of RNG manipulation, these Insights have no advantage.

Cards that can heavily benefit from having an RNG cycling Insight are:

• When using a Guest such as CSp SR Kanan with an RNG cycling Insight, the RNG outcome doesn't change only your center's turn anymore, but on every note. This means you now get three times as many RNG values from the sequence. You can now try to SP on every note instead of just the notes your center taps, as every single turn could be a possible proc of her LSALSA: Short for "Live Show Ability". The second Ability of a Card..
• A Backline CSp SR Kanan usually is locked into a sequence of outcomes since you don't tap notes with her. Having this Insight allows her to still consume values from the sequence and thus change the RNG outcome for her LSA, allowing you to possibly find a proc on every single note.
• Similarly, any other Backline card's LSA can be manipulated the same way:
  • You can fish for NSp Fes Emma's and SSp Fes Setsuna's SP Fill on Strategy Swap LSAs on every note if they have a cycling Insight.
  • For cards with a 5% Appeal LSA on AC Success such as NVo Kanan, changing the outcome on every note means it is possible to time the AC clear to proc as many of these LSA as possible on the very first Appeal Chance.
  • Cleanse on SP cards such as SSk Kasumi allow you to delay your first SP, to possibly find an RNG value that allows them to remove debuffs at the first possible moment.
• Any card used in the Frontline can also profit from an RNG cycling Insight. Having such an Insight means that the card will consume at least four values each round: three consumed by the cycling Insight for each note, and one for its own Tap Skill check - which means that the Tap Skill will always get every fourth RNG value.
  While that interval cannot be manipulated, you can offset the rounds so different values are consumed by swapping Strategies. Since the cycling Insight still consumes values, but the Tap Skill doesn't, you can time the swap back, so values that were consumed by the cycling Insight before are consumed by the Tap Skill now (see image).
  Offsetting the value the Tap Skill consumes means you can simply switch to a whole new set of RNG values if you run into an unlucky streak where your Tap Skills do not proc, or, when doing a swap formation, you can delay your swaps to find the “sub-sequence” for the target Strategy that contains the most Tap Skill procs.
• For this reason, adding cycling Insights to your Guests is also a nice thing to have for your high ranking friends - besides sharing their usual LSA, this means they also get a free RNG cycling Insight on their center so they can manipulate that card's Tap Skill or your Guest's LSA (which is especially useful, for example, on CSp SR Kanan guests).

Note that having multiple Skills with this kind of trigger at once is not useful - what matters is the frequency of moving the RNG sequence ahead, not the step length. It’s important that you get a chance for a new RNG outcome every note, but whether the new chance comes from a +1 step in the sequence or a +2 makes no difference.

• What is the general RNG sequence used for? Maybe just graphical effects?
• If a Skill has a On Stamina Change/On Voltage Gain trigger, will it proc multiple times if multiple damage/heal/Voltage sources happen in the same turn? (For example, note damage and Heal Tap Skill)
• When using a Skill with an On Stamina Change trigger, will it still check for procs when Shields are up?