So I decided to create a calculator that just tells me which player/players to put on the field/buy.
What the calculator does: It aggregates the points, goals, goals conceded into a single score, akin to the 5 star system the game provides. So the highest rated player in the table should always be the best player.
Once you downloaded the views, you can use the print feature in FM24 to export a Web Print of the table. I recommend you name the exports as such to remember which one goes where, or the application might not be able to read the information correctly: "squad_data.html" "scouted_player_data.html" "players_in_range_data.html"
Once it's uploaded, you can click on the player and get a pareto chart along with their attributes.
Perhaps it's best you play around a bit with it and let me know what works and what stinks, or if you find any bugs.
cadoni said: Amazeballs! Thank you for creating and sharing such a tool! You can include a donation button, in order to help with maintain the cost; if you want. Expand
Thank you! I hadn't thought about that, but sure! Any little bit would help
Possebrew said: Thank you! I hadn't thought about that, but sure! Any little bit would help Expand
You are welcome! Question: Sometimes, the player in range scouting showing inside the game a range. For example 9-13. Usually the "correct" attribute is in the middle (ie. 11). How the tool translate that? What value does it take?
Hi, great job but I have one question. when a player has two natural positions wb and fb it shows me only in the wb section, is there any way to fix this?
cadoni said: You are welcome! Question: Sometimes, the player in range scouting showing inside the game a range. For example 9-13. Usually the "correct" attribute is in the middle (ie. 11). How the tool translate that? What value does it take? Expand
Funny you should ask that, as I had been working on just that yesterday. The update isn't ready yet, but the calculation I used now is as such:
Masked attributes (-) are defaulted to an 8, because that's what auto-generated players get in the game. Imho, it's fine that a player would have an inflated or deflated score, if he's far way from the 8, and is unscouted, because that's the point of scouting: to zero-in on the correct ability.
For semi-masked attributes (9-13), the formula is (min+max)/2 and then rounded, 9-13 would indeed be 11, but 5-12 would be 9.
---
For the formulas I have now made some adjustments, because I noticed that the outfield attributes are for 10 outfield players, while the goalkeeper is a single player.
So the formula goes as such: Each attribute's impact is adjusted to reflect its effect for a single player over one season (dividing by 10 for outfield players, as the original data measures team-wide results). It's then scaled based on how much the player's attribute exceeds the average baseline of 8 (up to 20), using: contribution = (adjusted_impact * (attribute_value - 8) / 12).
These contributions are summed to estimate the extra league points the player adds per season. To represent the total impact as observed in FM-Arena's extensive testing (equivalent to about 63 seasons from 2400 simulated matches), the seasonal total is multiplied by a scaling factor adjusted for position: around 24 for outfield players (accounting for shared team effects) and 3.5 for goalkeepers (reflecting their solo role and test variability). This provides a cumulative score aligned with the full test data.
So a Brazilian second division striker might add about 10 extra points per season, scaling to around 249 cumulatively, while a brazilian second division goalkeeper, adding a similar 10 per season, scales to about 37.
The formula feels off somehow still, so if anyone has a better recommendation on how to aggregate the numbers, I am more than happy to put that formula in.
Kamas1 said: Hi, great job but I have one question. when a player has two natural positions wb and fb it shows me only in the wb section, is there any way to fix this? Expand
Thank you for catching that! That is a bug. I will have to look into it. Should be fixed when I deploy again, probably end of this week.
Kamas1 said: Hi, great job but I have one question. when a player has two natural positions wb and fb it shows me only in the wb section, is there any way to fix this? Expand
Turns out I deployed earlier than expected, my plane got delayed. Can you please try again?
cadoni said: You are welcome! Question: Sometimes, the player in range scouting showing inside the game a range. For example 9-13. Usually the "correct" attribute is in the middle (ie. 11). How the tool translate that? What value does it take? Expand
This should work too now, based on my explanation earlier. Can you please test it?
Kamas1 said: Now I can only add dm to team builder and the players' ratings increase? For example, Brice Wembangomo had scores around 300 and now he has 396 Expand
Yes, I had to review the initial formula, as it was too simplistic. I just pushed an update for the Team Builder. Can you please check?
Possebrew said: Yes, I had to review the initial formula, as it was too simplistic. I just pushed an update for the Team Builder. Can you please check? Expand
I was trying to wrap my head around the attribute weights from this other thread:
https://fm-arena.com/thread/14009-attribute-testing-football-manager-24
So I decided to create a calculator that just tells me which player/players to put on the field/buy.
What the calculator does:
It aggregates the points, goals, goals conceded into a single score, akin to the 5 star system the game provides. So the highest rated player in the table should always be the best player.
Most of the information you'll find in the getting started page here:
https://fmarenacalc.com/
Once you downloaded the views, you can use the print feature in FM24 to export a Web Print of the table. I recommend you name the exports as such to remember which one goes where, or the application might not be able to read the information correctly:
"squad_data.html"
"scouted_player_data.html"
"players_in_range_data.html"
Once it's uploaded, you can click on the player and get a pareto chart along with their attributes.
Perhaps it's best you play around a bit with it and let me know what works and what stinks, or if you find any bugs.
Amazeballs! Thank you for creating and sharing such a tool! You can include a donation button, in order to help with maintain the cost; if you want.
cadoni said: Amazeballs! Thank you for creating and sharing such a tool! You can include a donation button, in order to help with maintain the cost; if you want.
Thank you! I hadn't thought about that, but sure!
Any little bit would help
Possebrew said: Thank you! I hadn't thought about that, but sure!
Any little bit would help
You are welcome! Question: Sometimes, the player in range scouting showing inside the game a range. For example 9-13. Usually the "correct" attribute is in the middle (ie. 11). How the tool translate that? What value does it take?
Hi, great job but I have one question.
when a player has two natural positions wb and fb it shows me only in the wb section, is there any way to fix this?
cadoni said: You are welcome! Question: Sometimes, the player in range scouting showing inside the game a range. For example 9-13. Usually the "correct" attribute is in the middle (ie. 11). How the tool translate that? What value does it take?
Funny you should ask that, as I had been working on just that yesterday. The update isn't ready yet, but the calculation I used now is as such:
Masked attributes (-) are defaulted to an 8, because that's what auto-generated players get in the game. Imho, it's fine that a player would have an inflated or deflated score, if he's far way from the 8, and is unscouted, because that's the point of scouting: to zero-in on the correct ability.
For semi-masked attributes (9-13), the formula is (min+max)/2 and then rounded, 9-13 would indeed be 11, but 5-12 would be 9.
---
For the formulas I have now made some adjustments, because I noticed that the outfield attributes are for 10 outfield players, while the goalkeeper is a single player.
So the formula goes as such:
Each attribute's impact is adjusted to reflect its effect for a single player over one season (dividing by 10 for outfield players, as the original data measures team-wide results). It's then scaled based on how much the player's attribute exceeds the average baseline of 8 (up to 20), using: contribution = (adjusted_impact * (attribute_value - 8) / 12).
These contributions are summed to estimate the extra league points the player adds per season. To represent the total impact as observed in FM-Arena's extensive testing (equivalent to about 63 seasons from 2400 simulated matches), the seasonal total is multiplied by a scaling factor adjusted for position: around 24 for outfield players (accounting for shared team effects) and 3.5 for goalkeepers (reflecting their solo role and test variability). This provides a cumulative score aligned with the full test data.
So a Brazilian second division striker might add about 10 extra points per season, scaling to around 249 cumulatively, while a brazilian second division goalkeeper, adding a similar 10 per season, scales to about 37.
The formula feels off somehow still, so if anyone has a better recommendation on how to aggregate the numbers, I am more than happy to put that formula in.
Kamas1 said: Hi, great job but I have one question.
when a player has two natural positions wb and fb it shows me only in the wb section, is there any way to fix this?
Thank you for catching that!
That is a bug. I will have to look into it.
Should be fixed when I deploy again, probably end of this week.
thx for this wanted to ask, if a player can play multiple positions, can we get a score for each position they could play?
OpticFawn said: thx for this wanted to ask, if a player can play multiple positions, can we get a score for each position they could play?
I do not have information to calculate that.
If someone can provide the formula to calculate it, then I would be glad to add that feature.
Kamas1 said: Hi, great job but I have one question.
when a player has two natural positions wb and fb it shows me only in the wb section, is there any way to fix this?
Turns out I deployed earlier than expected, my plane got delayed.
Can you please try again?
cadoni said: You are welcome! Question: Sometimes, the player in range scouting showing inside the game a range. For example 9-13. Usually the "correct" attribute is in the middle (ie. 11). How the tool translate that? What value does it take?
This should work too now, based on my explanation earlier.
Can you please test it?
Possebrew said: Turns out I deployed earlier than expected, my plane got delayed.
Can you please try again?
Now I can only add dm to team builder and the players' ratings increase? For example, Brice Wembangomo had scores around 300 and now he has 396
Kamas1 said: Now I can only add dm to team builder and the players' ratings increase? For example, Brice Wembangomo had scores around 300 and now he has 396
Yes, I had to review the initial formula, as it was too simplistic.
I just pushed an update for the Team Builder. Can you please check?
Possebrew said: Yes, I had to review the initial formula, as it was too simplistic.
I just pushed an update for the Team Builder. Can you please check?
It works better now