Possebrew
Samet2772 said: "Has Turkish support been added? I will try it tonight and get back to you. Is any additional view required in the game?
squad_data.html
scouted_player_data.html
players_in_range_data.html
Apart from these, are there any others and do you have the link?"


You have to go to Getting Started and download the new views.
Should be something with FMArenaCalc.fmf
https://www.fmarenacalc.com/getting-started



Personally, I only use Squad & Players in Range, but I added it the others in case someone else uses them.

The new views are so that Age & Transfer Value are displayed across:
Squad, Scouted, Players-in-Range & Shortlist

But they are also needed, because I had standardize them to rewrite the parser to support uploads in other languages.

I will add the other languages bit-by-bit, when I push the next feature updates.
Not sure when that will be, as I had an uptick in workload this week, so bugfixes are the most I can offer in terms of support atm.
I pushed a new version just now.
It wasn't possible without breaking changes. I added new views to the getting-started page, so you'll have to import the new views into the game.

---
Contains support for Italian, German, Polish & Turkish.
New Team Builder
Filters for Age & Score
Transfer Value of players
Editable attributes in Player Calculator
An update on the current state of features.

Here’s some upcoming changes:
- Overhaul for TeamBuilder with substitutes. Still has a few weird bugs I’m trying to iron out.
- New Downloadable Views: with Age & Price (this might make old exports not work)

Internationalisation I currently have to do this manually, one by one… which is why I am procrastinating on it.
My current plan is to create a template for you guys to download & upload.
You’d have to put in the positions names & shorthands, and once it works for you, you can DM them to me and I can make them part of the default parser.
BaZuKa said:

This would be perfect :D


Oh that!
But I don’t understand what you hope to learn from that number.
What would it help you do, that you can’t do without it?
BaZuKa said: Hi again,
Loving the site so far, but i would like to give a suggestion.
Add Average Attributes of the players excluding Corners, Free Kick Taking, Long Throws, Penalty Taking.

Let me give you an example, i was looking for a CM under 18.


First column is the score from the site
Second column is the Average Attributes of the player

This way you can narrow down even more the best players tha you looking for.

Thanks for you amazing work, see you soon.


Can't you already do that using the attribute settings?
Give all those attributes a 0 for team-points and switch to "Points only"
cadoni said: What's your attribute settings for GK?

I filter for Reflex & Agility over 13 (Adjusting upwards if there's too many)
and with Aerial Reach over 12.
Usually that leads to about 3-5 Goalkeepers.
Nebucco said: It doesn't work for me since the update, when I load the html file it doesn't show anything at all (English).It was flawless before. Any suggestions?

That's strange.
Can you DM me the HTML file you're trying to upload?
66connor66 said: How comes you add work rate?

I aim to keep each result set under 250 players found.
As work-rate under 12 has such a big impact according to another set of test results (which I can no longer find), I decided to filter the lazy bums out in-game already
Esyuelo said: Thank you for your response. Let me try to explain my point in more detail.

Let’s say I’m looking for an AM (C) and I find a player with a score of 450. In the Data Analysis, his positions are listed as AM (RLC), ST (C). When I check in FM24, I see that he is Natural at AM (C), but only Accomplished at ST (C).

However, after I transfer him and upload my updated squad list to the Calculator, choose 4-2-3-1 formation in the tab Team Builder, it assigns him to the ST (C) position instead of AM (C), most likely because my existing ST (C) is weaker than my AM (C) in terms of score.

So, it ends up placing players in positions where they’re not Natural and I need to look another AM (C) after spending 140M EUR to an Accomplished ST (C). That’s why I’m wondering if there could be an option to make the Team Builder only assign players to positions where they are Natural, so the squad it produces matches the criteria I originally set when scouting and selecting players.


That sounds more like a problem in the Team Builder, than an issue with the Natural/Accomplished. I'll try to see if I can find the cause.

Afaik, the calculator is blind to Accomplished positions, it only ever considers Natural positions.

The Team Builder in its current form is more of a placeholder solution. As I mentioned earlier, I am surprised how many of you use it. I myself only used it two or three times.
CBP87 said: I'm really confused by the new scores, what would you now say is a decent score? I know I can revert back to the previous score system and with that I would aim to get players who had a score of 360+ but I'm struggling to figure how the new scoring system works

I always load my own squad along with players I plan on buying, then pick players with a higher rating than the ones in my team, who are interested in playing for me.

I never thought of them as absolutes, but relative.

If you have the game editor, and want to know the absolute peak player score, I suppose you could load up someone with all 20s, and someone with all 1s to determine edge cases.
Esyuelo said: Excellent work, I absolutely love using it. However, I’ve encountered an issue for me, well not exactly an issue, but something that bothers me.

When building my team, I try to select only players who are Natural in the positions I use, and when I upload the "Players in Range" or "Squad Data" lists to the Calculator, I choose players this way as well. But sometimes, after I transfer a selected player from the list, the Team Builder tab in the Calculator shows that the player needs to play in a position where they are Accomplished, not Natural.

In my save managing Man City, for the past three seasons I’ve constantly had to buy players for the DMC position because the Team Builder says the player should play as DC or as DL (if they’re accomplished there), rather than in their Natural position. I'm guessing that Team Builder is trying to reach best average score for starting 11 with the list provided.

I’m wondering if it’s possible to add an option to limit the Team Builder tab to only the positions in which players are Natural?


I am not sure I understand your question.
Afaik, the positions in the position field are only Natural Positions.


The team-builder auto-picks the first result you would get for a given position in the data-analysis tab.
So if you add a Defender Right position from the dropdown, it would pick the first player that contains D R in their position.

If we added the Sec. Position to the views, we could also obtain the accomplished positions.
Like the player here, you may notice he is an AM (RL) Natural, but a M (R) Accomplished.
Kamas1 said: You can go into Man City, for example, and scan their team, then we have a point of reference. I did this with Bayern Munich in my save, and they musiala have had around 650.

This is indeed how I also do it.
Although, I do not care about absolute scores that much, as I am still on my MAN save since I wrote the calculator.

My filter always includes Interested in Transfer & Loan, as it doesn't make sense for me to filter for players that don't want to play for my team.

Afterwards, I set Work-Rate to 10 as a pre-filter, and ACC/PAC to 15/15.
then I increment Acc/Pac until I reduced player-found to under 250.



My standard process goes like this:
1. I load my fresh squad-data, players-in-range & scouted data whenever I intend to begin scouting.
2. I go position by position for my squad and check if the best player in Data-Analysis is a player in my squad or if there's someone else ranking higher.
3. Based on the gap between players, I decide whether to buy/loan a new player.
4. Repeat for each individual position in my formation.

I am quite surprised how many of you request features for the team-builder, as I myself almost never use it. So I assume some of you already have more expertise in using the calculator than me :)
Kamas1 said: @Possebrew Do you think it makes sense to take away a points from, for example, DC for having a low dribbling or finishing or long shots etc? Because it seems to me that such attributes in this case do not matter for a central defender, what do you think about it?

I don't know about that. My IWB Left gets quite a few goals from long shots.
And Long Shot + "Shoots with power" tends to lead to a lot of goals.

Also Ball Playing Defender is the recommended role for a CD. With Player Instruction of "Dribble More".
thepunisher23 said: Hello, excellent tool, is it possible to add the best substitutes per position in team builder?

Can you describe how you imagine that working?
Usually I use the data analysis tab for that, and I pick source: "Squad" and the position I am looking to substitute
66connor66 said: Another question? Not sure if just me or anyone else.
But when searching players were coming up in the 700s. After I signed went down to 300s in squad view and then signed some more and went back into squad vies and now down in the 100s?

https://gyazo.com/7b4047245fd6abf9d58280c9573c564f
https://gyazo.com/9a21d6fec13d7fdd7577dcb44cb2bfb2

The second gyazo was the second time I looked at squad view... in the 1st he went to 450. Same for all players


Ah, that was a bug caused by the dynamic normalization.
That is players with -270 would push all other scores up by 270, so the lowest would be 0.
I made it so scores won't go into the negatives now. So 0 will be the lowest.
ScratchMyDog said: @Possebrew I have been LOVING this tool.  But something definitely broke in this morning's update.  I only use the Squad Data tool, and beyond it having negative scores now (perhaps intended?), the corner attribute is coming in with triple digits, and one of my best players who was a ~170 before (i'm in lower leagues) is a -270 now.  My actual best player who was a 290 is now a 48.  Very very strange, and a 15yo kid who was a ~95 is now a 290.

I loved the tool - I was close to building one myself but let me go back to the old formula plz!!


I'll add the option to the settings screen to switch to the old formula.

Update: I added the toggle to the attribute settings screen. Can you please check if it works for you?
66connor66 said: Thanks for sorting, Intersting to see as some of my 200 scored players down to 30! Need a rebuild now :D

That is not to say that this is correct. It is an attempt. Let me know how it works out, it may very well be, that the performance of the new formula is worse than the old one.

I'd welcome any suggestions on how to improve it and make it more relevant & accurate.

Gabriel here has 0. Imho, it is correct, and he doesn't deserve any spot on my team.
ScratchMyDog said: Ding ding!!  Yes - the load is scrambling the attributes.  Downsides of vibe coding :-(

Alas, that was an incorrect commit, that I accidentally pushed in, but was part of the internationalization branch.
ScratchMyDog said: @Possebrew I have been LOVING this tool.  But something definitely broke in this morning's update.  I only use the Squad Data tool, and beyond it having negative scores now (perhaps intended?), the corner attribute is coming in with triple digits, and one of my best players who was a ~170 before (i'm in lower leagues) is a -270 now.  My actual best player who was a 290 is now a 48.  Very very strange, and a 15yo kid who was a ~95 is now a 290.

I loved the tool - I was close to building one myself but let me go back to the old formula plz!!


Oh that doesn't sound good. May have introduced a bug into the parser there.
I'll have a look at it and try to get a fix out as soon as I can.

Thank you for letting me know!

Update:
I found the parsing issue, seems to work fine now.
The various negative scores however, are a side-effect of the new formula.
In a weird way they also make sense though.

Any attribute below the baseline of 8 will apply negative points, and the outcome is... well, let's say not everyone IRL is cut out as a footballer.

I'd take the -270 score as an:
"Maybe gardening is more your thing, sweetie?"

Either way, I tried to add a minimum score of 0, so all scores were normalized upwards as a result.
CBP87 said: This is a brilliant tool, thank you for creating and sharing it with us. Can I ask what the importance of the goals scored/conceded values are please?

At the time of your asking, only the points were used for calculation. Goals for/against were mere placebos. I have taken your question as an impulse to do something about it, and just pushed a new version.

Alas, this means a new formula, so you will notice changes in the scores of the players.
However, I'd argue these are more correct than the previous ones.

I clustered the attributes by offensive/defensive/balanced attributes, based on the ratio between Goals For/Goals Against. Tackling for example is a pure defensive attribute, while dribbling is an offensive attribute. It will thus contribute differently to the player's total score.

I also added penalties, for attributes below 12. As being below baseline for critical attributes like Work-Rate seems to be more meaningful than being above 12. I had GPT5 review  the logic on this one multiple times, as I had doubts about the implementation myself, but our AI God vouched for it, fwiw.

You'll find a detailed description on how the score is calculated on the getting-started page.

For others reading this asking me about internationalization:
Still working on it. It's far more complicated than expected, because of the different position names.

So far my best approach is to tediously map the Italian position names to their English equivalents, after which I'll do Polish & German. Hopefully I'll get a better idea on how to go about this as I'm building them.