Purity said: First of all, amazing work! Thank you. It is by far the best tool I've seen for FM in years. I was vibe-coding a similar tool using just exports, but it was painful. I tried implementing a few of my own ideas into your code. I'm not great at this and it probably broke a few things, but hopefully it gives you some ideas for future updates!
I've linked the modified files below (the link expires in 3 days, so don't hesitate to ask if you need me to re-upload them). I'm sorry the text in the app is in French, but the features should be fairly self-explanatory.
Here is a quick breakdown of what I added:
-GK Meta Score: Added a meta score for GKs based on harvestgreen22's work (I believe it was up to date).
-Position-based Meta Score: Added position-based scoring using very low-thought attribute weightings. It’s not a huge change, you could easily revert to FMArena weighting, I just felt this direction made sense for the future.
-PA-Meta Score: Added a Potential meta score named "PA-Meta" based on your potential attributes preview. It includes its own filter, column, and profile display.
-"Best XI" Tab: Calculates the best possible lineup for a given formation using your squad. You can either choose from presets or manually set the positions yourself. Clicking "⚡ Trouver la meilleure compo" automatically picks the preset formation that yields the highest overall meta score for your players.
-"Mercato" Feature: Located inside the Best XI tab, this button shows potential squad upgrades based on your chosen formation. It includes lightweight filters for interest, as well as a "Value for Money" filter (Meta Score divided by price) to highlight bargains. It offers up to 3 upgrade choices per position; you can dismiss players with a cross, and the next available upgrade will take their place.
-"Clubs & Divisions" Tab: A quick early concept that ranks all in-game divisions by average meta score. Clicking a division displays its clubs, ranked by the average meta score of their top 20 players. It also shows average PA meta, top player, and total squad value. Search filters are available for both division and club names.
These two new tabs are still in early stages, but I think they have a ton of potential.
Known Issues: Because I tweaked this mainly for my own playstyle, a few things are broken: -The "New Data" button doesn't work (you have to press F9 to load data). -Historical graphs currently don't render. -I modified how loaddumps are read because it was mixing data across different saves on my end. -And surely more
I'm just sharing these files in case you want to test out the features. it's definitely not a finished project and was never meant to be! I felt a bit guilty rewriting on top of your codebase since it started as a personal tweak, but I figured I'd share the ideas visually. They are surely better in yours and other hands. Everyone else is free to modify it again or give suggestions on top of it. Hope it helps!
Amazing rework mate! I was fiddling a bit with the same kind of target. Only thing I added was some weighting on hidden attributes. I was about to fiddle even more by weighting "bad hidden attributes", but using their scores as 21-attribute (so 20 injury proneness is like having a 1 and 1 is like having a 20 - thus keeping their weighting easily comparable to "good" attributes).
Big kudos to the original, and great job with those add-ons! I'll be sure to buy a Koffee for ya @mavali . And "bon travail" to you @Purity . All of the new features are an absolutely great idea to be added. I upvote them!
Also, I'm raising my hand if you want beta testers for some features or even accept contributors. This project is one of the best companion app I've found for us FM niche nerds
First: 1.4.2 is out. It fixes the startIndex crash some of you hit, makes scans fast again (the 1.4.1 snapshot is now only an automatic retry when a live scan misses too much memory), lowers the plugin's own memory use, and adds a check-for-updates button. Problem reports now include scan telemetry automatically. @bf3metro metro this release is aimed squarely at your Win32 1450 and 17% errors: they come from Windows running low on memory with a 157k-player save loaded, which is also why a reboot helped. Update and let me know.
@Purity ty thank you, great list and clearly a lot of care went into it. I went through everything and two of your ideas are coming in the next release: a GK meta score (weights from harvestgreen22's keeper attribute retest, so measured numbers rather than invented ones) and a PA meta column with its own filter. For the other features: pull requests on GitHub are very welcome, one per feature keeps them reviewable and your credit visible.
@Panneton0 noted, and thanks for the offer to test.
First: 1.4.2 is out. It fixes the startIndex crash some of you hit, makes scans fast again (the 1.4.1 snapshot is now only an automatic retry when a live scan misses too much memory), lowers the plugin's own memory use, and adds a check-for-updates button. Problem reports now include scan telemetry automatically. @bf3metro metro this release is aimed squarely at your Win32 1450 and 17% errors: they come from Windows running low on memory with a 157k-player save loaded, which is also why a reboot helped. Update and let me know.
@Purity ty thank you, great list and clearly a lot of care went into it. I went through everything and two of your ideas are coming in the next release: a GK meta score (weights from harvestgreen22's keeper attribute retest, so measured numbers rather than invented ones) and a PA meta column with its own filter. For the other features: pull requests on GitHub are very welcome, one per feature keeps them reviewable and your credit visible.
@Panneton0 noted, and thanks for the offer to test.
I saw your message on GitHub. Unfortunately, I can’t test the new version yet because I’m at work, but I’ll install and test it as soon as I get home.
First of all, thank you for taking the time to investigate the issue so thoroughly. I really appreciated reading your explanation because it makes a lot of sense, especially considering the random behaviour I was experiencing. Sometimes it would work after a reboot, sometimes only the first scan would work, then it would suddenly fail for no apparent reason. Your explanation fits that behaviour perfectly.
It’s also clear that you didn’t just patch the symptom—you took the time to identify the root cause and improve the plugin as a whole. I really like the changes you’ve made in 1.4.2. Reducing memory pressure, improving the diagnostics, and making the scanning process more robust overall is exactly the kind of work that gives users confidence in a project.
I’m really hoping this update fixes the issue and that I won’t see those errors anymore. But even if I do, I still wanted to take a moment to thank you.
I really appreciate how much time you’ve spent investigating my reports, explaining the root cause in detail, and helping users who run into problems like mine. You’re incredibly responsive and willing to help, and that’s something I don’t take for granted. To be honest, I’ve rarely seen this level of support from a developer, not even from the Football Manager developers themselves.
I’m also really looking forward to seeing what comes next. FMSS already has a lot of potential, and seeing the amount of care and effort you put into improving it makes me genuinely excited for future versions and the new features you’ll add over time. I honestly believe FMSS has a very bright future ahead of it.
I also noticed that you accept donations. Once I’ve had the chance to test 1.4.2, I’d be more than happy to make one as a small thank-you for all the work and support you’ve provided.
Thanks again, and I’ll let you know how the testing goes!
So far, I haven't had any issues with FMSS—fingers crossed! 🤞 I do have one question though. Why is it that when I load the data, like in this example, it always loads a date that's a little earlier than the actual in-game date I'm currently on? I've attached some screenshots to show what I mean.
The real in-game date is findable in theory, but in practice it is a serious reverse-engineering job: to a memory scanner every contract, birthday and fixture looks like a date, and the right address shifts with every FM patch. So it would be a lot of work that breaks on every update, to fix a label that is only a few days off.
Instead the plugin lets every loaded team vote with its next-match date and takes the consensus: always close, works in every save, survives patches. If the gap is bigger than a few days, your dump is just old: press F9 again.
mavali said: The real in-game date is findable in theory, but in practice it is a serious reverse-engineering job: to a memory scanner every contract, birthday and fixture looks like a date, and the right address shifts with every FM patch. So it would be a lot of work that breaks on every update, to fix a label that is only a few days off.
Instead the plugin lets every loaded team vote with its next-match date and takes the consensus: always close, works in every save, survives patches. If the gap is bigger than a few days, your dump is just old: press F9 again. Expand
Thanks for the explanation, that actually makes a lot of sense. I completely understand why you're using the next-match consensus instead of trying to locate the real in-game date in memory.
In my case though, the difference is sometimes more than just a few days—it's occasionally a few months behind the actual in-game date.
Also, pressing F9 behaves exactly like clicking New Data for me. It reloads the data successfully, but it doesn't bring the loaded date any closer to my current in-game date. It just reloads the same snapshot/date again.
That said, I'm really not complaining. I'm already happy that everything is working again after the recent fixes. I just thought I'd mention it in case it's useful, and maybe it's something that can become more accurate in future versions. Either way, I'm really enjoying FMSS and I'm looking forward to seeing how it continues to improve.
Would it be possible to have this tool work with the women's database? I'm playing a save with the Tijuana women's team and when I attempt to use it, the tool only loads in the ~500 male players in the database rather than the ~40,000 female players that I actually want to see.
bf3metro said: Thanks for the explanation, that actually makes a lot of sense. I completely understand why you're using the next-match consensus instead of trying to locate the real in-game date in memory.
In my case though, the difference is sometimes more than just a few days—it's occasionally a few months behind the actual in-game date.
Also, pressing F9 behaves exactly like clicking New Data for me. It reloads the data successfully, but it doesn't bring the loaded date any closer to my current in-game date. It just reloads the same snapshot/date again.
That said, I'm really not complaining. I'm already happy that everything is working again after the recent fixes. I just thought I'd mention it in case it's useful, and maybe it's something that can become more accurate in future versions. Either way, I'm really enjoying FMSS and I'm looking forward to seeing how it continues to improve. Expand
Found it thanks to your screenshots: your game is at 23 July, the summer break. The date comes from the teams' "next match" fields, and during the break most teams have no next match yet, so the field still holds the season finale (your 31 May). F9 re-reads those same frozen schedules, so the date does not move until the new fixtures exist. Known blind spot now, but ok for now for me. Useful catch, thanks.
FMSuperScout 1.5.0 is out, and most of it comes straight from this thread.
GK meta score (@Panneton0 0, @Purity): keepers now get a meta rating, weighted by @harvestgreen22 2's keeper attribute retest. Measured numbers on the familiar 1-20 scale, so no invented weights next to tested ones. PA meta (@Purity , @kami911 ): the meta a player projects to at his full potential, as a sortable column, filter and profile line. Sort the world by tomorrow's meta stars. Women's database (@johnconnerson ): new Database setting, scan men, women or both. Your Tijuana save should now load all ~40,000 women; with "both" you get a gender filter in the sidebar. Let me know how it behaves. Four languages: English, Dutch, French and German (@Purity , your French build nudged this along). Also in: wages per week/month/year, nation names and the EU check now language-independent (they came out of memory in your game's language before), shorter help texts, and a manual check-for-updates button. Direct download: https://github.com/mavarobli/FMSuperScout/releases/latest/download/FMSuperScout-Setup.exe Full changelog: https://github.com/mavarobli/FMSuperScout/blob/main/CHANGELOG.md
Keep the requests and reports coming, this release is proof they land.
Purity said: First of all, amazing work! Thank you. It is by far the best tool I've seen for FM in years. I was vibe-coding a similar tool using just exports, but it was painful. I tried implementing a few of my own ideas into your code. I'm not great at this and it probably broke a few things, but hopefully it gives you some ideas for future updates!
I've linked the modified files below (the link expires in 3 days, so don't hesitate to ask if you need me to re-upload them). I'm sorry the text in the app is in French, but the features should be fairly self-explanatory.
Here is a quick breakdown of what I added:
-GK Meta Score: Added a meta score for GKs based on harvestgreen22's work (I believe it was up to date).
-Position-based Meta Score: Added position-based scoring using very low-thought attribute weightings. It’s not a huge change, you could easily revert to FMArena weighting, I just felt this direction made sense for the future.
-PA-Meta Score: Added a Potential meta score named "PA-Meta" based on your potential attributes preview. It includes its own filter, column, and profile display.
-"Best XI" Tab: Calculates the best possible lineup for a given formation using your squad. You can either choose from presets or manually set the positions yourself. Clicking "⚡ Trouver la meilleure compo" automatically picks the preset formation that yields the highest overall meta score for your players.
-"Mercato" Feature: Located inside the Best XI tab, this button shows potential squad upgrades based on your chosen formation. It includes lightweight filters for interest, as well as a "Value for Money" filter (Meta Score divided by price) to highlight bargains. It offers up to 3 upgrade choices per position; you can dismiss players with a cross, and the next available upgrade will take their place.
-"Clubs & Divisions" Tab: A quick early concept that ranks all in-game divisions by average meta score. Clicking a division displays its clubs, ranked by the average meta score of their top 20 players. It also shows average PA meta, top player, and total squad value. Search filters are available for both division and club names.
These two new tabs are still in early stages, but I think they have a ton of potential.
Known Issues:
Because I tweaked this mainly for my own playstyle, a few things are broken:
-The "New Data" button doesn't work (you have to press F9 to load data).
-Historical graphs currently don't render.
-I modified how loaddumps are read because it was mixing data across different saves on my end.
-And surely more
I'm just sharing these files in case you want to test out the features. it's definitely not a finished project and was never meant to be! I felt a bit guilty rewriting on top of your codebase since it started as a personal tweak, but I figured I'd share the ideas visually. They are surely better in yours and other hands. Everyone else is free to modify it again or give suggestions on top of it. Hope it helps!
Files download
Amazing rework mate! I was fiddling a bit with the same kind of target. Only thing I added was some weighting on hidden attributes. I was about to fiddle even more by weighting "bad hidden attributes", but using their scores as 21-attribute (so 20 injury proneness is like having a 1 and 1 is like having a 20 - thus keeping their weighting easily comparable to "good" attributes).
Big kudos to the original, and great job with those add-ons! I'll be sure to buy a Koffee for ya @mavali . And "bon travail" to you @Purity . All of the new features are an absolutely great idea to be added. I upvote them!
Also, I'm raising my hand if you want beta testers for some features or even accept contributors. This project is one of the best companion app I've found for us FM niche nerds
Quick update from my side.
First: 1.4.2 is out. It fixes the startIndex crash some of you hit, makes scans fast again (the 1.4.1 snapshot is now only an automatic retry when a live scan misses too much memory), lowers the plugin's own memory use, and adds a check-for-updates button. Problem reports now include scan telemetry automatically. @bf3metro metro this release is aimed squarely at your Win32 1450 and 17% errors: they come from Windows running low on memory with a 157k-player save loaded, which is also why a reboot helped. Update and let me know.
@Purity ty thank you, great list and clearly a lot of care went into it. I went through everything and two of your ideas are coming in the next release: a GK meta score (weights from harvestgreen22's keeper attribute retest, so measured numbers rather than invented ones) and a PA meta column with its own filter. For the other features: pull requests on GitHub are very welcome, one per feature keeps them reviewable and your credit visible.
@Panneton0 noted, and thanks for the offer to test.
DOWNLOAD!
mavali said: Quick update from my side.
First: 1.4.2 is out. It fixes the startIndex crash some of you hit, makes scans fast again (the 1.4.1 snapshot is now only an automatic retry when a live scan misses too much memory), lowers the plugin's own memory use, and adds a check-for-updates button. Problem reports now include scan telemetry automatically. @bf3metro metro this release is aimed squarely at your Win32 1450 and 17% errors: they come from Windows running low on memory with a 157k-player save loaded, which is also why a reboot helped. Update and let me know.
@Purity ty thank you, great list and clearly a lot of care went into it. I went through everything and two of your ideas are coming in the next release: a GK meta score (weights from harvestgreen22's keeper attribute retest, so measured numbers rather than invented ones) and a PA meta column with its own filter. For the other features: pull requests on GitHub are very welcome, one per feature keeps them reviewable and your credit visible.
@Panneton0 noted, and thanks for the offer to test.
DOWNLOAD!
Hi, @mavali!
I saw your message on GitHub. Unfortunately, I can’t test the new version yet because I’m at work, but I’ll install and test it as soon as I get home.
First of all, thank you for taking the time to investigate the issue so thoroughly. I really appreciated reading your explanation because it makes a lot of sense, especially considering the random behaviour I was experiencing. Sometimes it would work after a reboot, sometimes only the first scan would work, then it would suddenly fail for no apparent reason. Your explanation fits that behaviour perfectly.
It’s also clear that you didn’t just patch the symptom—you took the time to identify the root cause and improve the plugin as a whole. I really like the changes you’ve made in 1.4.2. Reducing memory pressure, improving the diagnostics, and making the scanning process more robust overall is exactly the kind of work that gives users confidence in a project.
I’m really hoping this update fixes the issue and that I won’t see those errors anymore. But even if I do, I still wanted to take a moment to thank you.
I really appreciate how much time you’ve spent investigating my reports, explaining the root cause in detail, and helping users who run into problems like mine. You’re incredibly responsive and willing to help, and that’s something I don’t take for granted. To be honest, I’ve rarely seen this level of support from a developer, not even from the Football Manager developers themselves.
I’m also really looking forward to seeing what comes next. FMSS already has a lot of potential, and seeing the amount of care and effort you put into improving it makes me genuinely excited for future versions and the new features you’ll add over time. I honestly believe FMSS has a very bright future ahead of it.
I also noticed that you accept donations. Once I’ve had the chance to test 1.4.2, I’d be more than happy to make one as a small thank-you for all the work and support you’ve provided.
Thanks again, and I’ll let you know how the testing goes!
@mavali
So far, I haven't had any issues with FMSS—fingers crossed! 🤞
I do have one question though. Why is it that when I load the data, like in this example, it always loads a date that's a little earlier than the actual in-game date I'm currently on? I've attached some screenshots to show what I mean.
The real in-game date is findable in theory, but in practice it is a serious reverse-engineering job: to a memory scanner every contract, birthday and fixture looks like a date, and the right address shifts with every FM patch. So it would be a lot of work that breaks on every update, to fix a label that is only a few days off.
Instead the plugin lets every loaded team vote with its next-match date and takes the consensus: always close, works in every save, survives patches. If the gap is bigger than a few days, your dump is just old: press F9 again.
mavali said: The real in-game date is findable in theory, but in practice it is a serious reverse-engineering job: to a memory scanner every contract, birthday and fixture looks like a date, and the right address shifts with every FM patch. So it would be a lot of work that breaks on every update, to fix a label that is only a few days off.
Instead the plugin lets every loaded team vote with its next-match date and takes the consensus: always close, works in every save, survives patches. If the gap is bigger than a few days, your dump is just old: press F9 again.
Thanks for the explanation, that actually makes a lot of sense. I completely understand why you're using the next-match consensus instead of trying to locate the real in-game date in memory.
In my case though, the difference is sometimes more than just a few days—it's occasionally a few months behind the actual in-game date.
Also, pressing F9 behaves exactly like clicking New Data for me. It reloads the data successfully, but it doesn't bring the loaded date any closer to my current in-game date. It just reloads the same snapshot/date again.
That said, I'm really not complaining. I'm already happy that everything is working again after the recent fixes. I just thought I'd mention it in case it's useful, and maybe it's something that can become more accurate in future versions. Either way, I'm really enjoying FMSS and I'm looking forward to seeing how it continues to improve.
Would it be possible to have this tool work with the women's database? I'm playing a save with the Tijuana women's team and when I attempt to use it, the tool only loads in the ~500 male players in the database rather than the ~40,000 female players that I actually want to see.
bf3metro said: Thanks for the explanation, that actually makes a lot of sense. I completely understand why you're using the next-match consensus instead of trying to locate the real in-game date in memory.
In my case though, the difference is sometimes more than just a few days—it's occasionally a few months behind the actual in-game date.
Also, pressing F9 behaves exactly like clicking New Data for me. It reloads the data successfully, but it doesn't bring the loaded date any closer to my current in-game date. It just reloads the same snapshot/date again.
That said, I'm really not complaining. I'm already happy that everything is working again after the recent fixes. I just thought I'd mention it in case it's useful, and maybe it's something that can become more accurate in future versions. Either way, I'm really enjoying FMSS and I'm looking forward to seeing how it continues to improve.
Found it thanks to your screenshots: your game is at 23 July, the summer break. The date comes from the teams' "next match" fields, and during the break most teams have no next match yet, so the field still holds the season finale (your 31 May). F9 re-reads those same frozen schedules, so the date does not move until the new fixtures exist. Known blind spot now, but ok for now for me. Useful catch, thanks.
FMSuperScout 1.5.0 is out, and most of it comes straight from this thread.
GK meta score (@Panneton0 0, @Purity): keepers now get a meta rating, weighted by @harvestgreen22 2's keeper attribute retest. Measured numbers on the familiar 1-20 scale, so no invented weights next to tested ones.
PA meta (@Purity , @kami911 ): the meta a player projects to at his full potential, as a sortable column, filter and profile line. Sort the world by tomorrow's meta stars.
Women's database (@johnconnerson ): new Database setting, scan men, women or both. Your Tijuana save should now load all ~40,000 women; with "both" you get a gender filter in the sidebar. Let me know how it behaves.
Four languages: English, Dutch, French and German (@Purity , your French build nudged this along).
Also in: wages per week/month/year, nation names and the EU check now language-independent (they came out of memory in your game's language before), shorter help texts, and a manual check-for-updates button.
Direct download: https://github.com/mavarobli/FMSuperScout/releases/latest/download/FMSuperScout-Setup.exe
Full changelog: https://github.com/mavarobli/FMSuperScout/blob/main/CHANGELOG.md
Keep the requests and reports coming, this release is proof they land.