Potentially cool 124 classic thing

Working on chain Dsuming.
In concept this should allow for some more optimal Dsum in the safari zone, where you look for more than 1 encounter.
In principle you try to buffer catching things as good as good as possible, to end up in a known position in the Dsum after either catching something or have something flee on you.

This can be made as complicated as one wants to have it, as it can be hard to react to the pokemon fleeing/being caught while keeping track of what happened exactly and how long each action takes and so on.
The easiest applications for this are:

Catching something (mostly nido f/m) in the first ball, because this lines up the Dsum to almost where it is after fleeing that encounter (5 or less letter mons or mons with a longer cry might beg to differ).

Dsuming rare encounter into rare encounter (like Tauros into Tauros for example).
This needs more adjustments and stuff but so far I got

rare (still Needs adjustment)
1 fail into running		wait 4.5 
2 failed into running		look 1.5
3 into run			wait 2
4 into run			wait 4.5
5 into run 			look 1.5

Info Above is huge if true

But there are more complicating factors:
Since Dsuming is by nature not precise and only an estimate, it can be hard to verify these intervals
Also, since there are quite a bit of textboxes, chances are that the offset compared to perfect execution becomes significant (but just git gud imo Kappa).