Adding multiple Façade methods

Even though our auto-save feature only needs one method, that won’t always be the case – in most scenarios, your façade will need to handle multiple combinations of subsystem operations. In these situations, you have the freedom to add as many public Façade methods as you want (as long as you follow the same client-subsystem separation)!

For example, we could add another public Façade method that only converts and saves the player’s score without pausing and unpausing the game, which you can see in the following code block:

public class AutosaveFacade: MonoBehaviour
{
    //… No variable changes needed …
    void Start()
    {
        //… No changes needed …
    }
    public IEnumerator Save(double score)
    {
        //… No changes needed …
    }
    // 1
    public void ConvertAndSave(double score)
    {
        // 2
        float convertedScore = _dataConverter...