Rob Henry
5 years ago
1 month ago
7

"DETAILED FUTURE REGEN" "Mark" "Matt" "Baker" "31/1/2007" "1435" "2000337293" "0" "1" "4" "196" "85" "4" "MIDFIELDER_CENTRAL" "11" "104445" "130" "200" "2000337295"

 

Does this look correct to you? Am i doing something wrong. The team is a Red Bull Mod, otherwise fairly standard.

Fidney
18 years ago
5 days ago
407
Premium

@Rob Henry  DETAILED FUTURE REGEN should be DETAILED_FUTURE_REGEN (with underscores between each word) and in my file I use a period as the date seperator rather than a slash, but I'm not sure if that matters. I also have the country name for nationalily rather than the ID, but I think you can use either.

 

This is the line I have in my file:

 

"DETAILED_FUTURE_REGEN" "Fred" "" "Bloggs" "31.01.2007" "England" "671" "0" "7" "3" "180" "72" "2" "MIDFIELDER_CENTRAL" "31" "29044758" "" "-9" "671"

 

I do have it in the 2430 database - see the screengrab below with my .edt file highlighted.

I  place a copy of my .edt file (it's not .lnc as I mentioned a few posts back) in the same place in each and every database just to be on the safe side, but I think that technically you only need it in the latest (or the one you have selected for your game).

 

The whole of the dbc, edt and lnc folders are replaced when you use the real name fix, which I do, so the contents of my permanent might be slightly different to yours but that doesn't matter at all - as long as you have your newgen edt file in that place it should work fine.

jeremydk1
6 years ago
6 hours ago
240
By Fidney 21 April 2024 - 11:12 AM UTC 

@Rob Henry  DETAILED FUTURE REGEN should be DETAILED_FUTURE_REGEN (with underscores between each word) and in my file I use a period as the date seperator rather than a slash, but I'm not sure if that matters. I also have the country name for nationalily rather than the ID, but I think you can use either.

 

This is the line I have in my file:

 

"DETAILED_FUTURE_REGEN" "Fred" "" "Bloggs" "31.01.2007" "England" "671" "0" "7" "3" "180" "72" "2" "MIDFIELDER_CENTRAL" "31" "29044758" "" "-9" "671"

 

I do have it in the 2430 database - see the screengrab below with my .edt file highlighted.

I  place a copy of my .edt file (it's not .lnc as I mentioned a few posts back) in the same place in each and every database just to be on the safe side, but I think that technically you only need it in the latest (or the one you have selected for your game).

 

The whole of the dbc, edt and lnc folders are replaced when you use the real name fix, which I do, so the contents of my permanent might be slightly different to yours but that doesn't matter at all - as long as you have your newgen edt file in that place it should work fine.

 

possible to make your newgen24 file available? 

Rob Henry
5 years ago
1 month ago
7

I think the missing underscore in the title would be enough to throw it off, well spotted, i will do a simple save and holiday until newgen date and let you know, thank you 🙂 

Fidney
18 years ago
5 days ago
407
Premium
By jeremydk1 21 April 2024 - 16:05 PM UTC 

possible to make your newgen24 file available? 

 

Here you go.  Each of the 3 lines beginning "DETAILED_FUTURE_REGEN" are my actual newgens - all the other lines prefixed with # are ignored by the game and are there just for info.

 

Hope you find it useful.

bosco8179
6 years ago
9 hours ago
17

i wonder if this guide will be relevent for fm25

bosco8179
6 years ago
9 hours ago
17

Is it possible to set the newgen to show up in random team?

Fidney
18 years ago
5 days ago
407
Premium
By bosco8179 24 April 2024 - 01:35 AM UTC 

Is it possible to set the newgen to show up in random team?

 

I guess so. Not tried it myself, but the last number is the club so if you just leave it blank, by that I mean put “”, then I would expect (but I don't know for certain) the newgen to either appear at a random club or as unemployed. Try it in a test save and see what happens.

bosco8179
6 years ago
9 hours ago
17
By Fidney 24 April 2024 - 19:04 PM UTC 

I guess so. Not tried it myself, but the last number is the club so if you just leave it blank, by that I mean put “”, then I would expect (but I don't know for certain) the newgen to either appear at a random club or as unemployed. Try it in a test save and see what happens.

 

I have test it and it won't generate any newgen
Maybe i am missing something but you would like to test it by yourself

Pelado250
4 months ago
10 hours ago
14

Easy and well explained. I translated it with Google, no problem.

 

https://www.fmsite.net/files/file/1513-leyendas-y-buenos-jugadores-de-todos-los-tiempos-para-fm24-y-fm23-edt/

Fidney
18 years ago
5 days ago
407
Premium
By bosco8179 25 April 2024 - 00:58 AM UTC 

I have test it and it won't generate any newgen
Maybe i am missing something but you would like to test it by yourself

 

Had a little mess about and it doesn't work for me either you don't put a club at the end. Ah well, something learned I guess, so not a total waste of time! 😂

 

I even tried putting a birth dates that would make them in their 40s, 50s or 60s to see if they would appear as staff and that doesn't work either - if you try to make a newgen too old they simply do not appear.

FMPLAYER85
2 weeks ago
1 hour ago
11

I have figured out a way to generate 3 players a season on average at any club,in my experiments i used Scunthorpe United and i have tested this method from players born between 2008-2039,i don't recommend going beyond that because it is untested and it really isnt necessary.

 

Ok so this is for England and for FM24 ONLY,for older games adjust the date of births according to what year game you are playing so if you want to do this on fm20 for example then take away 4 years from the examples i show in England where we start in 2008 for every generation

 

Ok so here are some rules,players born between the 1st of January to the 13th of march are considered EARLY

DO NOT have any birthdays between the 14th of march-31st of March(these are the dates the youths generate in England,avoid them because players will not generate or generate the wrong year)

And players born between the 1st of April to the 31st of December are considered LATE

 

ok so here we go and i recommend keeping the same amount of players per generation except for gen 4 because only the first player will generate

 

1st generation must be born EARLY in consecutive years 2008-2018 (11 players per generation)

2nd generation must be born LATE in the same consecutive years 2008-2018(11 players)

3rd generation must be born EARLY in the same consecutive years 2008-2018(11 players)

4th generation must be a single player born LATE in the year 2008 (1 player max)

 

In my experiment from the first generation everyone has their first name as First and their surname as One-Eleven,second generation everyone has their first name as Second and their surname as One-Eleven,the pattern repeats for the third gen and the single player in the fourth gen is named Fourth One

 

and here is the order they will generate at the club

-first season-first one-third one =2 players
-second season-first two--second one-third two-fourth one =4 players
-third season-first three-second two-third three= 3 players
-fourth season-first four-second three-third four=3 players

and so on it will generate 3 players every season after that until all players have generated,so if you want to put 100 players in your club put 33 players in gen1-3 and 1 player in gen 4

 

 

 

FMPLAYER85
2 weeks ago
1 hour ago
11

I did some more tests to try to generate wingbacks and dms but I couldn't successfully generate them because the code was wrong so it seemed to generate random positions and many of them were dms and wingbacks by coincidence so the wrong code for preferred position seems to be the same as no code so then i did the test again with no preferred position and all the players generated again in random positions and many of them were dms,so I think if you generate 50 players with no preferred position about 15-20 or them will be dms and maybe 5-10 of them would be wingbacks but I haven't tested it with so many players

You'll need to Login to comment