Resolution of Recent Fable 3 Local Co-Op Save Autodestruct Problem

Hello: I hope I am in the right forum, if not, apologies, and hopefully the moderator can situate this post where it belongs...

In an earlier post I surprisingly was well received in my discussion of the matter. I even got "upvotes", whatever those are, I assume, or hope, good in some way? In any case, I have, by empirical vigor purely, figured out how to at least, in some way, circumvent
the recent Fable 3 (local co-op and beyond) save overwrite problem affecting many, many players.

I do not speculate as to causation (whether a recent update connected to the emulator, so-called, is involved.) But the problem is avoidable in the playing of Fable 3 in local co-op mode, by ENSURING the two relevant parties or players, in the section of
the Sanctuary accessible when attempting to load or review one's save file(s), simply DO NOT occupy the same mathematical space.

To illustrate: player 1, firstly (as I imagine strongly, this factor, if negative, shall affect matters), is the actual holder of the Xbox Live Gold membership...but I cannot confuse myself, or digress here... Anyway, player 1 is internally programming-wise,
understood to occupy "SAVE #1" (as alluded to above, there are even mannequins in a certain Sanctuary room, representing each discrete save file the profile/gamertag might possess, in the 360 version, 5, I believe.)

Okay, so the host Hero who occupies the Save space numeral "#1", now has a relative visiting who has a distinct sub-profile (I don't know the technical right words here) on the very same console; and they wish to play together in what I believe people call,
"couch co-op" mode, which, as far as I can tell, is another term for "local co-op."

What the theoretical player 2 must do, then, is NOT OCCUPY THE SAME NUMERICALLY DESIGNATED SPACE OR SLOT. If the Host is Save 1, the other player MUST be
not Save 1 when properly inspected in the "Load Old Game/Save" section of the Sanctuary, which, I believe, one automatically enters if only pressing the button to access saves in the "Settings" panel of main Sanctuary...

It's really quite devilishly simple. If wishing to play in local co-op with Fable 3, the Save File numeral of the one Hero, MUST be different from the other; if not, the mutilating glitch or duplication glitch inexorably shall happen.

If I am being unclear, here is another concrete illustration: the Host player is in the Save room with the mannequins of potential saves, labeled therein, as Save (File) #2 -
what matters here is the NUMERICAL SPACE, not the position of the mannequins, I should add... SO, as the Host hero occupies Save space 2, any would-be local co-op participant MUST be occupant of any Save File numeral,
EXCEPT 2! As long as both Heroes (and their related saves) occupy differentially distinct save spaces, NO save overwrite catastrophe or even androgynous deformation, shall eventuate, I am decently confident...

I am not a cryptographer, a programmer, only an empiricist... I learned the above method of transcending the recent game-breaking problem through sheer rigorous, relentless testing of possible variables involved, over so many hours, I am too embarrassed
to declare, better or worse.

If what I am seeking to communicate is not comprehensible to any one, I can try to re-phrase and work with struggling Fable 3 players, who, like me, virtually had their hearts broken, when this problem destroyed a Hero they had invested in heavily, in terms
of idealism, energy, time, etc.

I hope this helps, even if only one or two people can now resume playing the way they used to with friends, spouses, etc. My previous post declared there is no solution, and this post rectifies the subject.

:)