 |
Quote: |
 |
|
|
 |
Originally Posted by Matt10 |
 |
|
|
|
|
|
|
|
My problem, since names were greyed out - I did whatever I could so the gray went away. So editing a player, "SELECT EXISTING NAME"...selected one - then backspace - replaced name with whoever.
Now, I save - load up the franchise file again - it says "Name corruption" or something, I say no (just to see) and I go to the Jaguars, PUnter Adam Podlesh now says Chris Podlesh. OKay, fine, I think I knew that would happen - after all each is an existing name, I'm sure there is a limit.
So next time I load up the franchise again - I click "yes" and voila, it's fixed.
Now...after editing about all the positions except for CBs and S -- I come to find that after loading the franchise again...there is no "corruption" prompt, therefore the names are not being corrected.
Why is this? Is there a fix?
Am I basically overdoing something? Is there a completely different way to do this? I'm not exactly at wits end, as long as the last names stay in-tact, I'll sacrifice getting the first names wrong for the sake of having all my rooks.
*edit sorry for the scatter-brained post,
|
|
 |
|
 |
|
Hi Matt
Your assumption about why the name of Adam Podlesh changed to Chris Podlesh is actually wrong
While there is a limit to the number of names, you will never reach it. You can have 3874 unique names in the game when using the default roster as a basefile & without utilizing the in-game create-a-player feature. This is because there were 1937 players in the default roster and each has a unique first name & last name slot that can be changed
The reason I say you will never reach the limit is because there are always hundreds of instances of duplicate names; e.g. multiple instances of "Williams," dozens of the first name "Michael" or "Eric," etc... These duplicates can share the same unique name "slot," so in reality you can probably have 5000-6000 or more names at a given time to distribute between the 1937 players in a roster.
The reason you saw "Adam" in Adam Podlesh overwritten into "Chris" was because you clicked on his assigned name in the editor; the instance of "Adam" that said "Adam Podlesh" next to it, and you edited it into the first name "Chris" for a new rookie-- now they share that nameslot, which you changed to Chris.
To avoid this, you need to either:
(1) point this new rookie's first name to an existing instance of "Chris," like "Chris Simms" for example, and have them share that name
(2) Find a name that is not assigned to anyone and edit that into Chris... depending on whose updated roster you are using there may not be any unassigned names, in which case you would have to do #3 to create a new name that doesn't yet exist in the database of names for that gamesave:
(3) Take a duplicate name like Adam and assign all players with that name to the same slot-- e.g. pile up all the other "Adams" on to Adam Podlesh's first name slot. Then save & close out the franchise & reopen. The other Adam slots will now all be unoccupied and can be edited into new unique names. However, the editor will only show ONE instance of an unoccupied slot for Adam in the name database, so you will have to keep track of how many slots you freed up & only overwrite the open slot for Adam exactly that many times-- otherwise, you will get the name corruption error. Alternatively, you could save, close & reopen the franchise after each time you overwrite one of the open "Adam" slots you freed up-- this is because closing & reopening the file refreshes the name database. So, when you overwrite all the "Adams" while saving & closing in between each time, when you reopen it for the last time you will see that "Adam" is gone from the list of names except for the one instance that is share by all players named Adam in the file.
If you
don't save/close/reopen during this process, you need to remember exactly how many names you freed up, otherwise you could overwrite the name an infinite number of times even though there were only 10 or so unoccupied instances of Adam. This is why the corruption error pops up: Say for example that there were 10 instances of "Adam" that were unoccupied, but you overwrote the slot 20 times without closing/reopening; the editor will not know where to assign the 10 extra names after you close & reopen the file so it will create 10 NEW nameslots (beyond the 3874 total). This is okay at first but it will hit a max at some point & corrupt your franchise... at which point not even Finn can fix it because of the complexity of franchise file data. However, if you corrupt a
roster (rather than a franchise) by adding too many names to the database in this way, he can usually repair it by using a lengthy process of moving your data on to an uncorrupted roster.
If you want to learn about renaming and how to do it, I would highly recommend executing a search for posts by me, "Puja21," with these keywords: "rename" "corruption" "grayed" "editable" and "draft." I have posted how to rename in great detail several times using those words so a search for them should yield instructions to help you.
Best of luck.