iAdax

Value is a bit of a misnomer. It should more realistically be called "Expected Asking Price". All of those values you showed are for players who have a minimum of 3.5 years left on their current contract and they are very good players. Effectively what that is telling you is that your scouts think those clubs don't want to sell the player, however, they might be persuaded if you offer some looney amount of money for them. If you wait until those players have 1-2 years left on their contract, the price will fall dramatically. This is also how it works IRL, players are rarely sold with less than 2 years left on their contract unless they have a release clause. As the player, you can feel free to offer the club around 10% of the asking price. If the player really wants to join your club, they might kick up a big stink and after a few weeks, they request a transfer at a much more reasonable price range.

Some dropdowns do not have any ability to fine tune the value. This makes it so that searching based on advanced metrics for some attributes is useless (almost every player in the game will be between first and second option). Others allow you to use the dropdown to select a base number and then +/- buttons to have more fine control. It would be really nice to just standardize this UI element so that we can build filters for any advanced metric in the player search.

Is there anyone who can help me add the season stats into the scouting center report card? <!-- Season Stats --> <container> <container default_width="-588" minimum_width="588" priority="1"> <layout class="stick_to_sides_attachment" apply_to_children="true" inset="8"/> <widget class="player_additional_stats_panel" id="pcsp" file="player/player additional stats small"> <record id="object_property"> <list id="get_properties"> <record get_property="objt" set_property="objt"/> <record get_property="Pila" set_property="hidn"/> </list> </record> </widget> <widget class="player_stats_panel" id="pssp" file="player/player stats small"> <record id="object_property"> <list id="get_properties"> <record get_property="Pila" set_property="Shwn"/> <record get_property="objt" set_property="objt"/> </list> </record> </widget> </container> <container class="client_object_viewer_selector_panel" file="player/player overview small selector panel" id="cosF" default_width="-290" minimum_width="290" priority="2" navigation_container="true" default_widget="Pcrs"/> </container> I attempted to add this (from the player overview card) into this page but it won't render.

Sorry for the late reply, I was out of town. Yes, the screenshot is from the monthly staff meeting. I do think that is the right file but nothing is jumping out to me as the cause of this issue. I'll post back here if I end up figuring it out.

@sebastian_starttrbts do you know what panels these images come from? I'm attempting to add your changes into my own custom skin and I can't seem to locate these panels. If you notice the first attribute is missing its title.

I think it would add a lot to the game if player ratings were broken down into separate CA/PA for each of the different sections of attributes. (Technical/Mental/Physical/GK) What tends to happen right now with regen/newgens is that every high PA player ends up with elite physicals because the physical attributes eat up so much of the CA. I think it would add a lot of diversity for players to have separate CA/PA for each of these buckets so that we could end up with more elite technical/mental players who are not very athletic and vice versa. I would love to see more top tier regens end up looking like Bruno Fernandes instead of all of them being Mbappe-esque