[FIXED] [ECO] Fizzing Station blocks after picking up juice

I had a look at this, and it seems that it is directly related to the fix EA implemented for the previous bug with the juice fizzer (where it would get stuck fizzing). Specifically, they add this bit of code to the state tuning in the b61de6b4!0000001e!0000000000039285.juiceFizzer.object.xml:

            <V n="tested_states_post_load" t="enabled">
              <U n="enabled">
                <V n="fallback_state" t="enabled">
                  <T n="enabled">235272<!--juiceFizzer_ProgressValues_Finished--></T>
                </V>
                <L n="tested_states">
                  <U>
                    <T n="state">235272<!--juiceFizzer_ProgressValues_Finished--></T>
                    <L n="tests">
                      <L>
                        <V t="statistic">
                          <U n="statistic">
                            <T n="stat">235305<!--commodity_JuiceFizzer_Progress--></T>
                            <V n="threshold" t="value_threshold">
                              <U n="value_threshold">
                                <T n="value">1</T>
                              </U>
                            </V>
                            <E n="who">Object</E>
                          </U>
                        </V>
                      </L>
                    </L>
                  </U>
                </L>
              </U>
            </V>

The tested_states_post_load variant tells the game what state an object should be in whenever you load into a lot based upon a series of tests. In this case, it tells the game it should be in the juiceFizzer_ProgressValues_Finished state with a test to check if the fizzer was previously in the process of making juice (meaning it will give it the Finished state whenever you reload the lot). However, this variant does also have a fallback state, which determines the state if the object fails all of the tests tuned there, and in this case, it uses the exact same state as the tested one. As a result, this will mean that the fizzer will have the Finished state regardless of whether or not the object has ever been used before.

It is logical that deleting and replacing the object works as a temporary fix, as this does not involve reloading the lot  (tested_states_post_load only takes effect upon reloading the lot), and as such, only the default Off object state is applied (and a few others that aren't related). A more permanent fix would be to change the state referenced in the fallback_state, such as this:

                <V n="fallback_state" t="enabled">
                  <T n="enabled">235269<!--juiceFizzer_ProgressValues_Off--></T>
                </V>

From testing, this does fix the issue, but won't retroactively fix any objects that are already in the bugged state (but prevents it happening with brand new ones)