(sic)
-
Posts
607 -
Joined
-
Last visited
-
Days Won
1
Content Type
Forums
Articles
FAQs
Online Manual
Support: Blocks
Support: Games
Bug Tracker
SIGames Manual (beta)
Profiles
Posts posted by (sic)
-
-
13 minutes ago, herne79 said:
It isn’t. Traits are not included and there are many attributes which also aren’t. Determination for example and all hidden attributes.
I'm fairly sure whenever I added player traits via editor, it would follow up with an overall decrease to players attributes, if the player was already at the CA limit or his CA increasing. But I admit I might be wrong on this one.
13 minutes ago, herne79 said:Again I’m afraid this is incorrect. He still can increase past 14 but other attributes would need to decrease accordingly to compensate and keep within the CA limit. However that is nowhere near as dramatic as it sounds because increasing Positioning from say 14 to 15 would see minute (and therefore a negligible impact) decreases across pretty much all other attributes (say a 0.1 drop) rather than a larger hit against one or two attributes.
But CA is not (and never has been) a measure of how good a player is because as mentioned above there are many attributes not included in the calculation, all of which can have a pretty dramatic effect on a player’s ability.
I'm very much aware of that, but that's rarely going to happen in game, which is why I didn't include it in my post. Sure if you use the editor and change an attribute from 13 to 20, you'll see other attributes decrease to compensate for it.
CA isn't a measure of how good a player is, instead his attributes are, most of which won't be seeing any significant changes after the players hits the cap.0 -
And there's the problem.
Current ability is the sum of all attributes (& traits as well I think), and it just wont go past the PA set. You could have player that's 25 years old with 140PA. He has 14 Positioning, and you'll never see him actually increase it past 14 because his CA is already at 140. This hard cap is too harsh and unrealistic.
Certain attributes absolutely can be improved by anyone, with hard work, time, and dedication. Though, they can't be improved to infinity obviously, since the cap is 20 in game, and in real life there's also some sort of a cap based on many, many factors. Some players will find it much harder and much more time consuming to improve certain attributes (lack of talent maybe), while others will find it much easier (and will actually start off with higher attributes than regular players - aka they're more talented).
Certain attributes have softer caps than others (I'm not talking about the game here). For example, it's much easier to improve Determination, Leadership, Teamwork (which for some reason is incredibly difficult to improve in game), most, if not all technical attributes, Stamina, Balance, etc. compared to attributes like Anticipation, Decisions, Composure, Concentration, which in turn are easier to improve than things like Flair, Natural Fitness, Bravery that are pretty much hard capped.
1st group are attributes that can be improved in various ways, via coaching, training, etc.
2nd group are attributes that can be improved somewhat via training, but they also require playing experience at a certain level. These attributes are harder to improve, because they also rely on a player being smart enough to learn things, rather than just repeating certain things until you get better.
3rd group are attributes that are pretty much not going to change much, if at all, unless there's a bad injury or something (as it currently happens with Bravery).Jumping reach for example, I'd put in first category, as you absolutely can improve it a lot by training. But if you have a player that's 160cm tall, and a player that's 185cm tall, and both work on improving their jumping reach, it's obvious which player will be better at it. Strength for example can also be improved a lot.
In my opinion, certain attributes being improved, absolutely shouldn't take away from the players PA. The problem is, improving in attributes obviously raises the player's CA, therefore it takes away from PA in a way, because it leaves less room for improvement in other areas.
How to solve that issue? Change PA from a thing that encompasses attributes and traits as a whole, and instead use it on a more individual or group basis and/or maybe as suggested previously, PG (Potential Growth).
How would that work? No idea.
But let's actually try to come up with something and give an example.Let's make an imaginary player that's 18 years old and play as a CF.
If he has 10s for all attributes, with hard work, dedication, a lot of training, and a lot of time, he can eventually get all 20s, right? Well not so fast. PA/PG in this case should affect the ceiling of his attributes, INDIVIDUALLY or in a group.
So let's say he's a player that's determined that wants to improve and has a very good work ethic, his PA/PG should be pretty high, meaning he can improve a lot and the PG itself determines the rate of improvement.
However, not all attributes have the same level of PA/PG. Some attributes only have a margin of improvement of 1 or 2, meaning they can't improve by a lot, if at all. This is reserved for the attributes in the 3rd group that I mentioned previously. You either have these at the start, or you don't. Meaning, the player will likely keep 10s in those attributes, on some rare occasions it might improve to 11 or 12.
Then there are attributes from the 2nd group that can be improved via playing time, and less via training. These naturally have a higher PG than attributes from the 3rd group (which can't improve by much or if at all), but still below attributes from the 1st group. PG in this case is determined by player's personality and the level he's playing at, as well as the formation/system he's playing in (to a lesser extent maybe).
"In this players case, he has 10s for all attributes, so if we move him to a club like Man City, and give him enough playing time, he's gonna reach all 20s, is that what you're saying?", might be the first reply to this. The answer is no. The rate at which player learns and absorbs information is obviously not the same for everybody, in this example, the player is smart and dedicated, which is why I said PG is determined by player's personality (as well as the level he's playing at). In theory, he could improve his Composure from 10 to 20, but that's not gonna happen. Why? Diminishing returns, as well as lack of focus.There should be diminishing returns, meaning the PG slows down the closer you get to 20, and the lack of focus is pretty simple to explain - you just can't focus on improving one single attribute like composure in isolation, while ignoring all other attributes. But, you can set an individual focus for a player (like you currently can) that will put a bit more emphasis on improving certain attributes. Also, not all attributes are going to be improving, and not all attributes will be improving at the same rate. Only those attributes that are useful for the position and the role of a player, and only those attributes you train (via training, position/role training) are actually gonna see noticeable improvement. For example, this imaginary player will see more improvements in Off The Ball movement, than Positioning, simply due to him playing as a Striker, and that attribute being more relevant for his position and utilizing that attribute more in his game.
Here we finally reach the 1st group of attributes. These are the easiest to improve by simply working hard, training consistently. Time is key here. Other important factors are facilities and coaches.
Again, he can't reach 20s in all attributes in this group, because he can't focus on improving all attributes at the same time + the diminishing returns (If he had 1000 years, then he could theoretically do it - but only the attributes in this group).Now the PG absolutely will depend on the players age as well. At younger age, players have a higher PG rating in those 2 groups that actually can improve. But, this also won't stop a player from improving in certain attributes if he's 25+ (because there isn't a PA cap). Sure, attributes from the 1st group might not see much growth, but you could still see noticeable improvement in attributes from the 2nd group. For example: A 26 years old player that's considered at or near his peak, finally makes a move to a bigger club, with world class facilities and coaches, and a manager that uses a system that aligns well with the player's attributes and position he's playing in. Provided he gets enough game time, you could see some decent improvements in certain attributes (something that doesn't seem to be the case currently in game, at that age). On the other hand, if the system doesn't suit him at all, and plays in a league that's not really a challenge for him (aka he doesn't move "up" to play against better opponents), he's likely to stay at the same level without seeing any improvement.
Anyways, I've rambled for too long, and this is just writing my thoughts down as they come, but this is just an example of how things might work with a different system.There obviously are flaws with this system, when it comes to real-life players, but for players generated by the game, it absolutely can work.
0 -
17 hours ago, Brother Ben said:
You are describing CA. Replace every PA with CA in that sentence and that is what we have now.
Keep PA, make the journey towards the PA more varied imo
If you haven't already, read the threads that XaW linked above, it makes for interesting reading
CA is just a sum of all attributes though. I do agree that the PA can be kept, but add more variation to the "journey" towards achieving that PA. Personality changes, injuries, etc. could all have a more drastic effect towards it.
I will look into those threads. Cheers.
2 -
On 12/06/2023 at 21:29, the_hdk said:
funny you make such claims. its utter baloney what you say.
it actually is realistic if you look at science and what we know of human beings. we are born with 400 something predetermined traits/characteristics and capped talents. so that means we are born with a certain Potential value in certain areas that is predetermined but not visible. \
stop trying to make FM into fifa with *dynamic potential* and make it possible for every player to become messi.
Sure, that argument does make it seem like PA is realistic, and I'd agree to an extent. But FM doesn't use "400 something predetermined traits/characteristics", it uses way less than that. There are so many predetermined factors in real life, there are so many other factors that happen during a persons childhood, there's so much stuff that there's no way in real life we can access that information anyways, otherwise all the big clubs would be getting the best prospects that are guaranteed to succeed (based on a mathematical formula). There's just no way to access or use all those variables to determine players potential in real life. We can make some rough estimates, based on watching how a player performs, but as we all know, not everyone lives up to be a star player (in some cases it's because they've self sabotaged their careers in a way, because of injuries, or whatever, but in most cases it's because they didn't have that high of a potential to begin with).
In FM, we all know who the players with high potential are, because they do live up to their PA and become amazing players. Their PA is mostly always the same (not in the case of PA ranges where you could have a 150PA in one save, and a 160PA in another, but even then the PA is determined and set in stone once you create the save). Now I do feel there could be some margin of PA, where depending on the stuff that happens to that player during development, the PA can increase or decrease. Maybe if he gets a long term injury during development, the PA decreases, but it's a big can of worms that will ultimately make everything 100x more complicated.
Honestly this is one of the least important "issues", and I'm fine with it being the way it is for the time being, though I'm not opposed to changes, and I do think we can come up with better ways to determine PA.
1 -
On 04/06/2023 at 13:47, Minotti said:
-LESS of the statistical crap and that flashy **** that only looks cool but in reality is completely useless (data Hub and the likes).
-MUCH more tactical flexibility where I can dictate how I want my players to play. My definition of an inside forward or roaming playmaker is apparently not the same as the games hard coded versions. Same with tactics and the movement.
-BETTER match engine where I see more variety in how goals are scored.
-BETTER transfer activity from big teams. They end up buying crap players after a while and handicapp themselves.
This x100
I want more tactical options, more instructions, more control over how my players play, instead of just selecting premade presets that are hardcoded to behave a certain way in the ME. I want to control players movement and positioning in all 3 phases of play separately, instead of having a role that controls all 3 aspects of that for me. (I'd also like to control my players behaviour in defensive third, middle third, and final third in posession, in order to create/replicate modern, real-life stuff that people like Pep, Ten Hag, Arteta, De Zerbi do).
Overall match engine improvements so it actually resembles a real match, I don't want to see the same thing happening every single game (main reason why I use instant result on 80% of the matches I play)
I don't care about the statistics, etc. because they're useless to me due to how the game is designed. I have access to all the attributes (bar the hidden ones, that I also can easily see with a skin). I don't really have to look at any data to see how good a certain player is, I can just look at his attributes and personality - that immediately tells me if he's good or not. Stats do make sense in real life, where you don't just have a list of attributes for every player, and you need to measure their performance somehow, but imo, currently, it's just not at all required in FM, unless you play attributeless.
Better squad building and AI transfers are a must.
Graphics... we've been repeating this for the last 3-4 years. They've gone downhill. We don't need a 2023 AAA title level of graphics, we just need them not to be like they came out in 2005.
Better set piece planner/designer.
Major UI/UX improvements are needed, it's definitely getting better every year, but it's still the same as it's been 10 years ago in many areas. - There are some really talented and committed skin makers out there, and they've made some incredible stuff this year. But I don't want to rely on myself, or any other skin maker creating skins in order to make this game look better (and this is highly subjective ofc). But it would be great if SI themselves introduced the attributeless version of the skin, where we rely more on the data and stats, and where we can't really see most, if not all of the attributes. Rather, the attributes are replaced with text strings, just like the scout reports are (something like this https://community.sigames.com/forums/topic/568674-fm23skin-the-annual-show-your-skin-thread/?do=findComment&comment=14048252)
Something that's also tied to the UI/UX is the overall immersion. Now this might sound contradicting, but hear me out.
The game needs to be more like a game, and less like a spreadsheet. We need more gamification, and less walls of text, less tables, less numbers, less tabs to click through. We need more animations, more graphics, more "visual" feedback on certain stuff, rather than relying on pure text/numbers. You'd think immersion would be accomplished by adding more realism, but that just doesn't seem to be the case for this game, due to how everything is displayed to you.
I'm obviously not expecting any of this to actually happen, and I'll still probably buy the game come November (unless it's yet another FM23 with no new stuff - but I doubt that will be the case).
2 -
- Popular Post
- Popular Post
20 hours ago, Fantasista10 said:I think the game does a pretty good job at trying to get as close to real life as possible, and that's all it can do.
However, I do think it can be improved and is overdue a bit of an upgrade. Especially as football has evolved quite a lot in the last few years with Pep and his disciples. Even Roberto De Zerbi is transforming English football with his style of play and results at a so called 'smaller club'.
I think it goes beyond adding new player roles. Sure, we'd like a John Stones-esque role where the Centre Back becomes a second midfield pivot, or even a Ben White role where a full back plays as a wide centre back.
I'm not sure what the answer is - I'll leave that to the talented people at SI. But I think they need to prioritise bringing the game up to speed with modern football, where formations are no longer a thing.
As I understand it, the game understands formations as a teams defensive shape, which I agree on, and that part is fine. You can ask your team to defend in a 4-4-2 high or mid block, but in today's football, this can take on all forms of shapes and positions when the team has the ball, which are simply not viable in the tactics creator in its current state.
Agreed. And I'd like to emphasize those bolded points.
Player roles are just presets, but instead, the game should look to allow us to customize player movement and positioning (in possession) more than it currently does. Right now in football, everything is about space, and someone filling in that space. In FM it's a rigid system, where certain roles are going to occupy the same positions most of the time, while in real life it's fluid (at least with modern managers like Pep, De Zerbi, Ten Hag, etc.), and players think in terms of space (where do I need to go, based on where other players around me are) rather than roles, for example: "I'm an Inverted Wing-Back, therefore I'll always have to cut inside and play in the midfield". Players should make intelligent decisions, and if you have Roam From The Position on, then they should look to occupy other positions on the pitch, while players around them would shift, to cover other zones that are left uncovered due to that roaming.
On 30/05/2023 at 08:57, Prolix said:Then design a new one.
I'll never get this argument. So you are not allowed to criticize or suggest stuff now?
On 30/05/2023 at 12:58, Andros said:I would also argue that some changes are new this season. so Si needs time to work out how to implement these things. But I agree that adding more to the tactical creator would be good. i assume there will always be imporvements
Wingers holding the width during all phases of the attack, Fullbacks forming a back 3, etc. aren't new things at all. Sure, Stones being a CB out of possession and a DM/CM in possession is new, but I wouldn't expect that sort of thing to be in the game so soon anyways.
Overall, the tactical creator just looks like a bunch of presets you play around with (player roles, mentality). You're stuck with those presets, and you can only alter them so much via instructions and Player Traits. Instead, it should allow for more freedom in terms of allowing us to dictate how the player moves and what positions does he occupy in 3 phases of play SEPARATELY (because right now, roles are hardcoded to behave a certain way in each of 3 thirds of the pitch, and if you like how a role plays in the defensive third for example, during buildup, but dislike how it plays in the final third...well you're out of luck).
9 -
16 minutes ago, Jyuan83 said:
Unless there is a new role called the reverse halfback that allows the cb to step into the dm space during possession, it’s virtually to replicate pep’s 3241. The john stones role is crucial to its success.
Libero does that, but you can only use it from a central position.
I'd like to be proven wrong on this, but I don't think we'll get a realistic tactic creator any time soon. The ME can't handle it, the AI teams wouldn't handle it... And the question is, are we ever going to get a brand new ME, rather than getting constant updates on the current one (that's at least 10 years old at this point)?
There are so many things that are locked/hardcoded, so many movements are hardcoded and tied to certain roles, that users have no freedom of creating their own movements of players and freedom to choose positioning of players during each phase of play. Instead, all we have are 'presets' (player roles and duties) that can only be slightly and broadly tweaked by mentality, instructions and player traits.
So replicating any sort of movement or positioning that real-life teams use, comes down to: have the devs included it in-game yet? In most cases the answer is no, and you have to wait for a few years to have something like that included in game (WCB role is the latest example). We are always a few years behind the current tactical trends.
There's no way for us as users to create custom movements/roles, because the match engine simply isn't capable of doing that, and the AI teams also aren't smart enough to deal with that. I'm fairly sure it would be very much possible with the current technology to create something like that, although it would be hard and expensive to do I assume, and it would certainly come with its own, different set of issues (all of which is why I'm thinking it won't come any time soon).
All we can do is work with what we have, and realize that replicating real-life tactics 1:1 will not be a thing any time soon. It's incredibly frustrating for some (me included), but there's not much we can do about it.
Anyways here's my current tactic (which is not a complete replication of Pep, it also has hints of De Zerbi).
The IWB won't form a double pivot with a DM, which is an issue. The FB-D will also stay kinda wide, and won't form a back 3, which is also an issue.
I want my wingers high and wide, hence the attack duties. This is more of a De Zerbi thing I think, and you could swap one (or both) to a support duty.
I still feel like using a Winger is much better than an IW, if you want your wide players to hold the width for longer. You could still have them cut inside, just make sure their stronger foot is on the opposite side of where they're playing, and that they have a trait to cut inside from the flank.
Inverted wingers would sit narrower in the final third, once they cut inside, and you'd sometimes find them on the inside of a fullback (rather than being wider, outside). Also the AM would get in the way of the IW on the left, so a Winger was a natural solution to that.
Now obviously the movement and positioning of players won't be how they actually play in real life. Something I'm often frustrated with, for example, is how my wide players never cut off the passing lanes between CBs/Midfielders and Fullbacks. I've tried with different instructions, but it just doesn't work. They just stand around, doing nothing to prevent the pass, but they do close the fullback down once the pass is played.
1 -
On 23/03/2023 at 23:48, bluestillidie00 said:
I like that tbf. Looks a bit sparse, can maybe add another row of information but that's up to you
Yeah, that's the issue I had, I also felt there was too much unused space, and it didn't really look symmetrical. After letting it sit for a day, I just decided to do the same thing I already had previously.
Still have to fix the other selector panels and stuff, because a lot of stuff doesn't show up for players that aren't scouted/aren't at your club. Right now it looks like this for example:
SpoilerNow I'm probably gonna look into adding some more statistics, etc. to the player overview, we'll see how that goes.
For anyone who's asking me to share the skin, as I've said previously, I will not be sharing my skin this year. If I had wanted to share it, it would've been out already shortly after FM23 released.
A lot of it is still unfinished, and I'm constantly going back and forth redesigning the same screens as I'm not always happy with how they look. I'm also designing the skin for my screen size/resolution only, as well as for my own personal taste, so it probably wouldn't work for some people, and I'm just not willing to take endless requests to add or change things.Those are only a few reasons why I'm not releasing it this year. Maybe I will release a skin in the future, for FM24, but at this point I don't know.
3 -
Player profile, still work in progress. Gotta figure out what to do with the left portion below the player pic, still not 100% happy with it.
Absolutely love the attribute bars (shoutout to @bluestillidie00 for that one), don't think I'm going back to regular attributes any time soon.
7 -
21 hours ago, Andrew Marines said:
Yeah, as it should be. Probably we were talking about different things, sorry.
It's a common rule to not have your fullback and winger in the same vertical line during the build-up phase and this example is perfect to see why. If your forward gets the ball, he won't have no-one to pass it to cause the AM-R is not available(too wide).
It's a common issue with both IW and IF that kills possession tactics
Yeah, I agree that they shouldn't occupy the same vertical channel. In this case, both are technically in the halfspace, because the ball is on the opposite flank.
The wingback is never going to push high early on when the ball is on the opposite flank, so he and the winger pretty much occupy the same space there.
Imo in this situation, I'd want a CM or an AM in that central position, with the winger holding the width, being outside of the opposition fullback, so he could attack the space and go 1v1 if your team decides to switch the play. The fullback on the same side should act like an outlet for buildup and recycling the possession. But if you do want your winger to come even more central, you just have to play an AP or TQ there.
What I really have an issue with is this.
They're basically occupying the same space, while there's a huge gap in the halfspace/channel. That's because they look to stay wide, and then cut in, they don't automatically occupy the halfspace in the buildup, they only do so after the ball reaches the middle third (or even final third in some cases). Inverted Wingers would probably look to move in earlier.
Now that is FM22, I don't know how different it is compared to FM23, as I haven't really used overlapping wingbacks with IFs in FM23.
0 -
First impressions after 2 matches.
Something about the ME just feels way better. I'm seeing some great passes that I haven't previously seen, most notably in the centre of the pitch. Even just the "regular" passes seem to be improved, as the team moves the ball forward much better than previously. My wide players are actually taking players on 1v1, dribbling past them, cutting in. Players also seem to do more layoffs, and quick one-two's, and they seem to occasionally play faster passes, with more force behind them. It feels way more fluid and dynamic in possession than it was previously.
It's obviously still far from perfect, and it's been only 2 games, but now I can also say this ME is the best there ever was. I definitely expect to see stuff that has frustrated me previously, I have no idea how a different playstyle/tactic would perform, but so far so good.
Edit: Yet there's an annoying bug now. The squad view keeps resetting again, and I thought it was finally fixed this year.
It keeps moving to the right, and it doesn't fit the screen, so there's a scroll bar.
7 -
6 hours ago, The unknown said:
This picture describe my problem. Why is my wingers not moving into that massive space in the channel!
Both wingers have the trait move in to channels. And below is their instructions
I'm afraid that's hardcoded, because SI has decided that's how they should play. You can only do so much to alter their behavior.
They absolutely will occupy the halfspaces, just not in that phase of play (buildup). When the ball gets to the midfield, they will invert and look to come more narrow. I think someone has mentioned that IWs would look to come narrow earlier than the IFs would, so you might try with that, but I doubt it will help with the buildup phase. You could use APs, or TQs, as mentioned before. I see that you already have aggressive WBs, which also should force them to move inside earlier. I'd also try removing the overlaps, it might help.
It's funny, because I've seen so many of us complaining about the opposite thing. The wingers don't hold their width enough, which is (or at least was) true in the final third, where they would often just come narrow, and you have nobody on the flanks. IWs and IFs still do cut inside, as they should, but regular Wingers hold the width more in FM23.
0 -
38 minutes ago, snowofman said:
if you want, feel free to sent me your file and i'll gladly take a look and see if i can find a solution.
can't make any promises tho
I don't have the file anymore, I gave up and reverted it back to the default look.
It's nothing complicated though, just another container added next to the main bit that shows the squad. That container has this code inside it, and that .xml file contains all the info.
<container class="club_overview_panel" file="club/team squad facts"> <record id="object_property" get_property="Csca" set_property="Csca"/> </container>
0 -
41 minutes ago, snowofman said:
Thats down to the changes you made to the config file, changing true to false in both makes it possible to see changes without reloading.
the other issue i can't say as i havnt tried myself
I knew there was way to change it somewhere, thanks for the info.
4 hours ago, _Ben_ said:I don’t think it’s that! I would love to offer you a solution but, as you’ve said, I’ve got the same issue. I had wondered whether it was to do with the adaptive container or the fact it was on the left hand side - something that is a commonality between our two ideas.
One day I will go back and have a deeper look at things…
Yeah, I've had the entire game completely bug out after trying to fix that issue. First, I deleted all the skins from the folder, then my game just used some completely random colours, as well as a totally random background. Had to reset everything, restart the game, and reload the skin in order to finally make it work again..
But yeah that idea is the same, it's a normal container on the left hand side that just keeps going blank after switching screens.
Shame that whenever I try to do something even slightly unique, the game just doesn't allow it. I wanted to have a similar thing that exists on a club overview page, with Key player, captain, hot prospect, etc. with their picture and below it some more info about the team, I just don't want to place it above the squad view.
I've moved on to other things now, I've tried looking into it more for 5-6h straight that day, but to no avail.
0 -
So I've been trying to incorporate some more info in the team squad screen. Shoutout to @Tyburnand @_Ben_ for this idea, and code.
However, I'm having some issues. The info does display fine whenever I reload the skin, but when I click to any other screen in-game, and return to the team squad screen, it just displays no info.
Used the same approach of having a club_overview_panel container, pointing to a separate file with all the info bits. Even tried just copy pasting the entire table from the club panel, and it does the same thing.
<container class="club_overview_panel" file="club/team squad facts"> <record id="object_property" get_property="Csca" set_property="Csca"/> </container>
Spoiler
I'm also wondering how do you know which widget class to put in for whatever bit of info you want to display? Some do make sense, but some do not, like trying to put in other bits of info like nationalities represented, domestic player bias, etc. I have the id for them, but they don't display at all.
Edit: I've narrowed it down to the team squad panel. I tried copying the entire panel from another skin, and then using my own custom .xml file with all the bits of info, and it works. I have no idea what it could be, seeing that it does work after skin reload, but stops showing any info as soon as I click on any other screen.
Spoiler<panel> <boolean id="save_session_state" value="true" /> <boolean id="save_default_state" value="true" /> <layout class="arrange_horizontal_attachment" alignment="centre, extend" offset="0" gap="10" layout="340,-3" /> <layout class="stick_to_sides_attachment" alignment="vertical" apply_to_children="true" inset="0" /> <container class="main_contrast_box" red_replacement="bg lighter" force_title_borders="true"> <attachment class="vertical_arrange" vertical_layout="-1" vertical_gap="4"/> <layout class="stick_to_sides_attachment" alignment="horizontal" inset="0" apply_to_children="true" /> <container id="" height="40"> <layout class="stick_to_sides_attachment" alignment="all" inset="0" apply_to_children="true" /> <container class="club_overview_panel" file="club/team squad facts"> <record id="object_property" get_property="Csca" set_property="Csca"/> </container> </container> </container> <container class="main_contrast_box" red_replacement="bg darker"> <layout class="arrange_vertical_attachment" alignment="bottom,extend" offset="0" /> <layout class="stick_to_sides_attachment" alignment="all" apply_to_children="true" inset="8" /> <!-- Starting XI Styles --> <flags id="stxi" value="tables/standard/row/normal/row" /> <!-- Subs Styles --> <flags id="subs" value="tables/custom/squad/substitute/row" /> <!-- Sent off Styles --> <flags id="soff" value="tables/custom/cards/red/row" /> <!-- Not in squad Styles --> <flags id="nisq" value="tables/custom/squad/outside squad/row" /> <!-- Highlighted Styles --> <flags id="hida" value="tables/custom/squad/highlight/row" /> <container class="main_box_no_margin" id="plti" alignment="left" force_title_borders="false"> <layout class="arrange_vertical_attachment" alignment="top,extend" offset="0" /> <layout class="stick_to_sides_attachment" alignment="horizontal" apply_to_children="true" inset="0" /> <!-- buttons area --> <container navigation_container="true"> <attachment_group class="horizontal_arrange_vertical_autosize" horizontal_alignment="right,extend" /> <!-- top left buttons --> <container> <attachment_group class="horizontal_arrange_vertical_autosize" horizontal_alignment="left" horizontal_gap="6" /> <widget class="view_menu_label" id="TitL" auto_size="horizontal" embed_in_frame="false"> <translation id="text" translation_id="232113" type="use" value="Players" /> </widget> <widget class="view_menu_popup" id="plvi" embed_in_frame="false" auto_size="all"/> </container> <!-- top right buttons --> <container > <layout class="arrange_horizontal_attachment" offset="0" alignment="right"> <global id="gap" name="ui.button_row_gap"/> </layout> <layout class="centre_in_parent_attachment" alignment="vertical" apply_to_children="true" /> <layout class="stick_to_sides_attachment" inset="0" alignment="top,right" /> <layout class="fit_children_attachment" alignment="vertical" offset="0"/> <layout class="fit_children_attachment" alignment="horizontal,fill" offset="0" /> <!-- quick pick --> <container> <layout class="arrange_horizontal_attachment" offset="0" alignment="right"> <global id="gap" name="ui.split_button_row_gap"/> </layout> <layout class="centre_in_parent_attachment" alignment="vertical" apply_to_children="true" /> <layout class="fit_children_attachment" alignment="vertical" offset="0"/> <layout class="fit_children_attachment" alignment="horizontal,fill" offset="0"> <global id="gap" name="ui.split_button_row_gap"/> </layout> <widget class="icon_button" id="askp" auto_size="all" appearance="buttons/subtle/split/left/button" controller_button="y_button"> <translation id="text" translation_id="344655" type="use" value="Quick Pick[COMMENT - team screen team selection, contains the former Ask To Pick menu but also acts as a standalone button which picks the team, renamed for accuracy]" /> </widget> <widget class="popup_button" id="apic" fixed="true" width="45" auto_size="vertical" appearance="buttons/subtle/split/right/button"/> </container> <!-- filter menu --> <widget class="embedded_filter_button" id="plsf" target="plti" auto_size="all" /> </container> </container> <widget class="picking_panel" id="pkpn" navigation_container="true"/> <container id="ptct"> <layout class="arrange_vertical_attachment" alignment="bottom,extend" offset="0" /> <layout class="stick_to_sides_attachment" alignment="horizontal" apply_to_children="true" inset="0" /> <widget class="tactic_player_list_table" id="pltb" database_table_type="1" customisation_context="play" mode="fill_rows, stripe_rows, printable, store_sort_state, drag_rows, drop_on_rows, show_bullets, select_rows, select_multiple, show_insert_column_popup,keyboard" column_mode="resize_columns, move_columns, custom_views" popup_menu_class="popup_button_table_header" row_height="30" navigation_container="true" default_focus="true"> <boolean id="save_session_state" value="true" /> <boolean id="save_default_state" value="true" /> <integer id="contextual_handler_column_id" value="Pnms" /> <!-- default sort by playing position (primary), then picked position, then name --> <list id="default_sort_column"> <integer value="PtsL" /> <integer value="PpsC" /> </list> <!--default view--> <flags id="default_view" value="sltn" /> <!--available views--> <list id="viws"> <record id="geni"> <translation id="name" translation_id="247410" type="use" value="General Info" /> <!-- Define attributes/properties to view in this view type on the panel. Any properties not defined here will be hidden for this view. --> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="PpsC" /> <!-- position --> <flags id="Pbpc" /> <!-- best position --> <flags id="Pbrc" /> <!-- best role --> <flags id="PSag" /> <!-- person age --> <record id="Pnat"> <!-- person nationality --> <flags id="use_format" value="short" /> </record> <flags id="Pcpt" /> <!-- agreed playing time --> <flags id="Pcac" /> <!-- current ability --> <flags id="Pppc" /> <!-- potential ability --> <flags id="Pcww" /> <!-- wage --> <flags id="Pced" /> <!-- contract expiry --> <flags id="Pdva" /> <!-- value --> </record> </record> <record id="ctrt"> <translation id="name" translation_id="230163" type="use" value="Contract" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="Psnu" /> <!-- squad number --> <flags id="Pcpt" /> <!-- agreed playing time --> <flags id="Pcif" /> <!-- full time or part-time contract --> <flags id="Pcww" /> <!-- weekly wage --> <flags id="Pced" /> <!-- contract expiry --> <flags id="Pdva" /> <!-- value --> <flags id="Pwof" /> <!-- new wage --> <flags id="Pcof" /> <!-- new date --> </record> </record> <record id="trnf"> <translation id="name" translation_id="230119" type="use" value="Transfer" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="Pagn" /> <!-- person agent --> <flags id="Pcoo" /> <!-- transfer options --> <flags id="Pctr" /> <!-- transfer status --> <flags id="Pcls" /> <!-- loan status --> <flags id="Papr" /> <!-- asking price --> <flags id="Pdva" /> <!-- value --> </record> </record> <record id="hgst"> <translation id="name" translation_id="275860" type="use" value="Home-Grown Status" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <record id="PSag" auto_hide_priority="3000" /> <!-- person age --> <record id="Pnat" auto_hide_priority="1000" /> <!-- person nationality --> <record id="Phgs" auto_hide_priority="2000" /> <!-- home grown status --> <record id="Phdd" auto_hide_priority="4000" /> <!-- home grown due date--> <flags id="Pdva" /> <!-- value --> </record> </record> <record id="info"> <translation id="name" translation_id="247860" type="use" value="Full Player Status[COMMENT: player full status information: heading]" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnms" /> <!-- person name --> <flags id="Pnfa" /> <!-- full player status/info --> <flags id="Pdva" /> <!-- value --> </record> </record> <!-- This view will show the player unique IDs in a list (visible if 'show unique id' preference set) --> <record id="unid"> <translation id="name" translation_id="247858" type="use" value="Unique IDs" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="duni" /> <!-- unique id --> <flags id="Pnms" /> <!-- name --> <flags id="Pclb" /> <!-- person club --> <flags id="Pnat" /> <!-- nationality --> <flags id="Pdva" /> <!-- value --> </record> </record> <record id="----" /> <!-- shown for club teams --> <record id="sltn"> <translation id="name" translation_id="326989" type="use" value="Selection Info[COMMENT: button in view_menu on squad screens; choose to view club stats]" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <record id="PpsC" auto_hide_priority="1000" /> <!-- position --> <record id="PcOI" auto_hide_priority="2000" /> <!-- player condition--> <record id="PftI" auto_hide_priority="2000" /> <!-- player sharpness --> <record id="Pmor" auto_hide_priority="3000" /> <!-- player morale --> <record id="Ppth" auto_hide_priority="3000"/> <!--playing time happiness--> <record id="Pfrm" auto_hide_priority="6000" /> <!-- player form --> <record id="Poap" auto_hide_priority="3000" /> <!-- overall appearances --> <record id="Pogl" auto_hide_priority="4000" /> <!-- overall goals --> <record id="Poas" auto_hide_priority="4000" /> <!-- overall assists --> <flags id="Poav" /> <!-- overall average rating --> </record> <record id="object_list_view_context"> <integer id="player_stats_scope" value="5" /> </record> </record> <!-- shown for club youth teams --> <record id="ysli"> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <record id="PpsC" auto_hide_priority="1000" /> <!-- position --> <record id="Pmor" auto_hide_priority="5000" /> <!-- player morale --> <record id="Pfrm" auto_hide_priority="6000" /> <!-- player form --> <record id="PcOI" auto_hide_priority="2000" /> <!-- player condition --> <record id="PftI" auto_hide_priority="2000" /> <!-- player sharpness --> <record id="Ppth" auto_hide_priority="1000"/> <!--playing time happiness--> <record id="Poap" auto_hide_priority="3000" /> <!-- overall appearances --> <record id="Pogl" auto_hide_priority="4000" /> <!-- overall goals --> <record id="Poas" auto_hide_priority="4000" /> <!-- overall assists --> <flags id="Poav" /> <!-- overall average rating --> </record> <record id="object_list_view_context"> <integer id="player_stats_scope" value="0" /> </record> </record> <record id="plat"> <translation id="text" translation_id="423877" type="use" value="Playing Time[COMMENT: FR 14013, contract promise type]" /> <record id="view"> <flags id="PtsL"/> <!-- picked info --> <flags id="Pnfo"/> <!-- player status/info --> <flags id="Pnms"/> <!-- person name --> <flags id="Pcpt" /> <!-- agreed playing time --> <flags id="Pctp" /> <!-- current playing time --> <record id="Poap" auto_hide_priority="3000" /> <!-- overall appearances --> <record id="Ppth" auto_hide_priority="1000"/> <!--playing time happiness--> <record id="Ppte" auto_hide_priority="1000"/> <!--playing time happiness--> <record id="PFpt" auto_hide_priority="1000"/> <!--future playing time--> </record> </record> <record id="fuPT"> <translation id="text" translation_id="492004" type="use" value="Future Playing Time[COMMENT: AREA: Playing Time; SUB-AREA: Playing Time Pathways; FR-BN: n/a; TONE: Informal; CHARLIMIT: None; REF-ID: n/a; NOTE: displays the agreed playing time for the player in years to come]" /> <record id="view"> <flags id="PtsL"/> <!-- picked info --> <flags id="Pnfo"/> <!-- player status/info --> <flags id="Pnms"/> <!-- person name --> <flags id="Pcpt" /> <!-- agreed playing time --> <flags id="fpt1" /> <!-- current season +1 --> <flags id="fpt2" /> <!-- current season +2 --> <flags id="fpt3" /> <!-- current season +3 --> <flags id="fpt4" /> <!-- current season +4 --> </record> </record> <record id="dyna"> <translation id="text" translation_id="447669" type="use" value="Dynamics[COMMENT: Manager Main/Top Menu; link to Dynamics screen showcasing a representation of interpersonal relationships at the club]" /> <record id="view"> <flags id="PtsL"/> <!-- picked info --> <flags id="Pnfo"/> <!-- player status/info --> <flags id="Pnms"/> <!-- person name --> <flags id="Pmbm"/> <!-- promises --> <flags id="Pmor"/> <!-- morale --> <flags id="THic"/> <!-- player hierarchy category --> <flags id="DRsd"/> <!-- player social group --> <flags id="Pohl"/> <!-- player overall happiness--> </record> </record> <!-- shown for international teams --> <record id="csln"> <translation id="name" translation_id="275847" type="use" value="Club Selection[COMMENT: button in view_menu on squad screens; choose to view club stats]" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <record id="PpsC" auto_hide_priority="1000" /> <!-- position --> <record id="Pmor" auto_hide_priority="5000" /> <!-- player morale --> <record id="Pfrm" auto_hide_priority="6000" /> <!-- player form --> <record id="PcOI" auto_hide_priority="2000" /> <!-- player condition --> <record id="PftI" auto_hide_priority="2000" /> <!-- player sharpness --> <record id="Poap" auto_hide_priority="3000" /> <!-- overall appearances --> <record id="Pogl" auto_hide_priority="4000" /> <!-- overall goals --> <record id="Poas" auto_hide_priority="4000" /> <!-- overall assists --> <flags id="Poav" /> <!-- overall average rating --> </record> <record id="object_list_view_context"> <integer id="player_stats_scope" value="5" /> </record> </record> <!-- shown for international teams --> <record id="intf"> <translation id="name" translation_id="275848" type="use" value="International Selection[COMMENT: button in view_menu on squad screens; choose to view international stats]" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <record id="PpsC" auto_hide_priority="1000" /> <!-- position --> <record id="Pmor" auto_hide_priority="5000" /> <!-- player morale --> <record id="Pfrm" auto_hide_priority="6000" /> <!-- player form --> <record id="PcOI" auto_hide_priority="2000" /> <!-- player condition --> <record id="PftI" auto_hide_priority="2000" /> <!-- player sharpness --> <record id="Poap" auto_hide_priority="3000" /> <!-- overall appearances --> <record id="Pogl" auto_hide_priority="4000" /> <!-- overall goals --> <record id="Poas" auto_hide_priority="4000" /> <!-- overall assists --> <flags id="Poav" /> <!-- international average rating --> </record> <record id="object_list_view_context"> <integer id="player_stats_scope" value="7" /> </record> </record> <record id="coac"> <translation id="name" translation_id="292814" type="use" value="Reports[COMMENT: top level menu title for player reports screens]" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="PpPs" /> <!-- player style --> <flags id="Pbpc" /> <!-- best position --> <flags id="Pbrc" /> <!-- role --> <flags id="Pbdc" /> <!-- duty --> <flags id="Page" /> <!-- age --> <flags id="Pcac" /> <!-- currant ability --> <flags id="Pppc" /> <!-- potential ability --> </record> </record> <record id="inju"> <translation id="name" translation_id="247861" type="use" value="Injuries[COMMENT: squad list view menu, injuries menu item label]" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="PpsC" /> <!-- position --> <record id="injr" auto_hide_priority="3000" /> <!-- player injury --> <record id="iida" auto_hide_priority="4000" /> <!-- player injured date--> <record id="iito" auto_hide_priority="5000" /> <!-- player injury time out --> <record id="PcOI" auto_hide_priority="2000" /> <!-- player condition --> <record id="PftI" auto_hide_priority="2000" /> <!-- player condition --> </record> </record> <record id="RskA"> <translation id="text" translation_id="447655" type="use" value="Risk Assessment[COMMENT: FR20159; team injuries panel; panel title for assessing player injury risk]"/> <record id="view"> <flags id="PtsL"/> <!-- picked info --> <flags id="Pnfo"/> <!-- player status/info --> <flags id="Pnms"/> <!-- person name --> <flags id="PpsC"/> <!-- position --> <flags id="PMlo"/> <!-- player match load --> <flags id="PTWl"/> <!-- player training load --> <flags id="PInS"/> <!-- player injury susceptibility --> <record id="PcOI"/> <!-- player condition --> <flags id="PftI"/> <!-- player sharpness --> <flags id="POvR"/> <!-- player overall injury risk --> </record> </record> <record id="stts"> <translation id="text" translation_id="247412" type="use" value="Stats" /> <list id="items"> <record id="gatp"> <translation id="name" translation_id="284341" type="use" value="Goal Attempts[COMMENT: team information panel; stats section; column heading]" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="Pogl" /> <!-- player overall goals --> <flags id="POsa" /> <!-- player overall shots --> <flags id="POst" /> <!-- overall shots on target ratio --> <flags id="POps" /> <!-- overall penalties scored --> <flags id="POpt" /> <!-- overall penalties taken --> <flags id="POlg" /> <!-- overall minutes since last goal --> </record> <record id="object_list_view_context"> <integer id="player_stats_scope" value="5" /> </record> </record> <record id="genp"> <translation id="name" translation_id="284349" type="use" value="General Play[COMMENT: team information panel; stats section; column heading]" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="POpC" /> <!-- player overall passes completed --> <flags id="POpa" /> <!-- player overall pass attempts --> <flags id="POgm" /> <!-- overall mistakes leading to goal --> <flags id="POhc" /> <!-- overall headers won --> <flags id="POha" /> <!-- overall aerial challenges attempt --> <flags id="POcc" /> <!-- overall crosses completed won --> <flags id="POca" /> <!-- overall crosses attempt --> </record> <record id="object_list_view_context"> <integer id="player_stats_scope" value="5" /> </record> </record> <record id="disc"> <translation id="name" translation_id="284353" type="use" value="Discipline[COMMENT: team information panel; stats section; column heading]" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="Poap" /> <!-- player appearances --> <flags id="POtc" /> <!-- player overall tackle completed --> <flags id="Pofm" /> <!--overall fouls--> <flags id="POta" /> <!-- overall tackle attempt --> <flags id="Poyc" /> <!-- overall yellow cards --> <flags id="Porc" /> <!-- overall red card --> </record> <record id="object_list_view_context"> <integer id="player_stats_scope" value="5" /> </record> </record> <record id="goak"> <translation id="name" translation_id="284359" type="use" value="Goalkeeper[COMMENT: team information panel; stats section; column heading]" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="Poap" /> <!-- player appearances --> <flags id="POcs" /> <!-- player overall clean sheet --> <flags id="Poco" /> <!--overall goals conceded--> <flags id="POs%" /> <!--save ratio--> <flags id="POx%" /> <!--expected save ratio--> </record> <record id="object_list_view_context"> <integer id="player_stats_scope" value="5" /> </record> </record> <record id="ExGo"> <translation id="name" translation_id=" 514224" type="use" value="xG[COMMENT: AREA: Team Stat; SUB-AREA: Expected goals stats FR: 32708; TONE: Formal; CHARLIMIT: None NOTE: expected goals short string]" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="Poap" /> <!-- player appearances --> <flags id="Pogl" /> <!-- player overall goals --> <flags id="POsa" /> <!-- player overall shots --> <flags id="PoxG" /> <!-- player XG --> </record> <record id="object_list_view_context"> <integer id="player_stats_scope" value="5" /> </record> </record> <record> <translation id="text" translation_id="227741" type="use" value="Competitions" /> <list id="items"> <record id="ncst"> <translation id="name" translation_id="320538" type="use" value="Non Competitive[COMMENT: squad list view type]" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="Poap" /> <!-- overall appearances --> <flags id="Pogl" /> <!-- player overall goals --> <flags id="Poas" /> <!-- overall assists --> <flags id="PoxG" /> <!-- player XG --> <flags id="Pomo" /> <!-- overall man of match --> <flags id="Popa" /> <!-- overall pass completion ratio --> <flags id="Pota" /> <!-- overall tackles per game ratio --> <flags id="Podr" /> <!-- overall dribbles per game ratio --> <flags id="Post" /> <!-- overall shots on target ratio --> <flags id="Poyc" /> <!-- overall yellow cards --> <flags id="Porc" /> <!-- overall red cards --> <flags id="Poav" /> <!-- overall average rating --> </record> <record id="object_list_view_context"> <integer id="player_stats_scope" value="0" /> </record> </record> <record id="lgst"> <translation id="name" translation_id="320539" type="use" value="League[COMMENT: squad list view type]" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="Poap" /> <!-- overall appearances --> <flags id="Pogl" /> <!-- player overall goals --> <flags id="Poas" /> <!-- overall assists --> <flags id="PoxG" /> <!-- player XG --> <flags id="Pomo" /> <!-- overall man of match --> <flags id="Popa" /> <!-- overall pass completion ratio --> <flags id="Pota" /> <!-- overall tackles per game ratio --> <flags id="Podr" /> <!-- overall dribbles per game ratio --> <flags id="Post" /> <!-- overall shots on target ratio --> <flags id="Poyc" /> <!-- overall yellow cards --> <flags id="Porc" /> <!-- overall red cards --> <flags id="Poav" /> <!-- overall average rating --> </record> <record id="object_list_view_context"> <integer id="player_stats_scope" value="1" /> </record> </record> <record id="cpst"> <translation id="name" translation_id="320540" type="use" value="Cup[COMMENT: squad list view type]" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="Poap" /> <!-- overall appearances --> <flags id="Pogl" /> <!-- player overall goals --> <flags id="Poas" /> <!-- overall assists --> <flags id="PoxG" /> <!-- player XG --> <flags id="Pomo" /> <!-- overall man of match --> <flags id="Popa" /> <!-- overall pass completion ratio --> <flags id="Pota" /> <!-- overall tackles per game ratio --> <flags id="Podr" /> <!-- overall dribbles per game ratio --> <flags id="Post" /> <!-- overall shots on target ratio --> <flags id="Poyc" /> <!-- overall yellow cards --> <flags id="Porc" /> <!-- overall red cards --> <flags id="Poav" /> <!-- overall average rating --> </record> <record id="object_list_view_context"> <integer id="player_stats_scope" value="2" /> </record> </record> <record id="ctst"> <translation id="name" translation_id="320541" type="use" value="Continental[COMMENT: squad list view type]" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="Poap" /> <!-- overall appearances --> <flags id="Pogl" /> <!-- player overall goals --> <flags id="Poas" /> <!-- overall assists --> <flags id="PoxG" /> <!-- player XG --> <flags id="Pomo" /> <!-- overall man of match --> <flags id="Popa" /> <!-- overall pass completion ratio --> <flags id="Pota" /> <!-- overall tackles per game ratio --> <flags id="Podr" /> <!-- overall dribbles per game ratio --> <flags id="Post" /> <!-- overall shots on target ratio --> <flags id="Poyc" /> <!-- overall yellow cards --> <flags id="Porc" /> <!-- overall red cards --> <flags id="Poav" /> <!-- overall average rating --> </record> <record id="object_list_view_context"> <integer id="player_stats_scope" value="3" /> </record> </record> <record id="teat"> <translation id="name" translation_id="229413" type="use" value="Technical" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="Poap" /> <!-- overall appearances --> <flags id="Pogl" /> <!-- player overall goals --> <flags id="Poas" /> <!-- overall assists --> <flags id="PoxG" /> <!-- player XG --> <flags id="Pomo" /> <!-- overall man of match --> <flags id="Popa" /> <!-- overall pass completion ratio --> <flags id="Pota" /> <!-- overall tackles per game ratio --> <flags id="Podr" /> <!-- overall dribbles per game ratio --> <flags id="Post" /> <!-- overall shots on target ratio --> <flags id="Poyc" /> <!-- overall yellow cards --> <flags id="Porc" /> <!-- overall red cards --> <flags id="Poav" /> <!-- overall average rating --> </record> <record id="object_list_view_context"> <integer id="player_stats_scope" value="7" /> </record> </record> <record id="ovst"> <translation id="name" translation_id="320543" type="use" value="Overall[COMMENT: squad list view type]" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="Poap" /> <!-- overall appearances --> <flags id="Pogl" /> <!-- player overall goals --> <flags id="Poas" /> <!-- overall assists --> <flags id="PoxG" /> <!-- player XG --> <flags id="Pomo" /> <!-- overall man of match --> <flags id="Popa" /> <!-- overall pass completion ratio --> <flags id="Pota" /> <!-- overall tackles per game ratio --> <flags id="Podr" /> <!-- overall dribbles per game ratio --> <flags id="Post" /> <!-- overall shots on target ratio --> <flags id="Poyc" /> <!-- overall yellow cards --> <flags id="Porc" /> <!-- overall red cards --> <flags id="Poav" /> <!-- overall average rating --> </record> <record id="object_list_view_context"> <integer id="player_stats_scope" value="5" /> </record> </record> <record id="altm"> <translation id="name" translation_id="335947" type="use" value="All Time[COMMENT: squad list view type]" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="PAap" /> <!-- all time appearances --> <flags id="PAla" /> <!-- all time league appearances --> <flags id="PAcg" /> <!-- all time goals --> <flags id="PAlg" /> <!-- all time league goals --> </record> <record id="object_list_view_context"> <integer id="player_stats_scope" value="5" /> </record> </record> <record id="----" /> <!-- current competition stats --> <record id="ccst"> <translation id="name" value="" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="Poap" /> <!-- overall appearances --> <flags id="Pogl" /> <!-- player overall goals --> <flags id="Poas" /> <!-- overall assists --> <flags id="PoxG" /> <!-- player XG --> <flags id="Pomo" /> <!-- overall man of match --> <flags id="Popa" /> <!-- overall pass completion ratio --> <flags id="Pota" /> <!-- overall tackles per game ratio --> <flags id="Podr" /> <!-- overall dribbles per game ratio --> <flags id="Post" /> <!-- overall shots on target ratio --> <flags id="Poyc" /> <!-- overall yellow cards --> <flags id="Porc" /> <!-- overall red cards --> <flags id="Poav" /> <!-- overall average rating --> </record> </record> </list> </record> <record id="----" /> </list> </record> <record id="inca"> <translation id="name" translation_id="227820" type="use" value="International" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="Pclb" /> <!-- person club --> <flags id="Pnat" /> <!-- person nationality --> <flags id="Pntm" /> <!-- current international team picked for --> <flags id="Piap" /> <!-- player int apps --> <flags id="Pigl" /> <!-- player int goals --> <flags id="Puia" /> <!-- player int u21 apps --> <flags id="Puig" /> <!-- player int u21 goals --> <flags id="Pdva" /> <!-- value --> </record> </record> <record id="----" /> <record id="stts"> <translation id="text" translation_id="229822" type="use" value="Attributes" /> <list id="items"> <record id="ImAt" /> <record id="phat"> <translation id="name" translation_id="230003" type="use" value="Physical" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="Pacc" /> <!-- (p) acceleration --> <flags id="Pagi" /> <!-- (p) agility --> <flags id="Pbal" /> <!-- (p) balance --> <flags id="Pjum" /> <!-- (p) jumping --> <flags id="Pnft" /> <!-- (p) natural fitness --> <flags id="Ppac" /> <!-- (p) pace --> <flags id="Psta" /> <!-- (p) stamina --> <flags id="Pstr" /> <!-- (p) strength --> </record> </record> <record id="meat"> <translation id="name" translation_id="230106" type="use" value="Mental" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <record id="Pagg" /> <!-- (m) aggression --> <record id="Pant" /> <!-- (m) anticipation --> <record id="Pbra" /> <!-- (m) bravery --> <record id="Pcmp" /> <!-- (m) composure --> <record id="Pcnt" /> <!-- (m) concentration --> <record id="Pdec" /> <!-- (m) decisions --> <record id="Pdet" /> <!-- (m) determination --> <record id="Pfla" /> <!-- (m) flair --> <record id="Pinf" /> <!-- (m) influence --> <record id="Potb" /> <!-- (m) off the ball --> <record id="Ppsn" /> <!-- (m) positioning --> <record id="Ptwr" /> <!-- (m) teamwork --> <record id="Pcre" /> <!-- (m) vision --> <record id="Pwkr" /> <!-- (m) work rate --> </record> </record> <record id="teat"> <translation id="name" translation_id="229413" type="use" value="Technical" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <record id="Pcor" /> <!-- (t) corner taking --> <record id="Pcro" /> <!-- (t) crossing --> <record id="Pdri" /> <!-- (t) dribbling --> <record id="Pfin" /> <!-- (t) finishing --> <record id="Pfrs" /> <!-- (t) first touch --> <record id="Pfrk" /> <!-- (t) free kick taking --> <record id="Phea" /> <!-- (t) heading --> <record id="Plsh" /> <!-- (t) long shots --> <record id="Plth" /> <!-- (t) long throws --> <record id="Pmar" /> <!-- (t) marking --> <record id="Ppas" /> <!-- (t) passing --> <record id="Ppen" /> <!-- (t) penalty taking --> <record id="Ptac" /> <!-- (t) tackling --> <record id="Ptec" /> <!-- (t) technique --> </record> </record> <record id="goat"> <translation id="name" translation_id="230024" type="use" value="Goalkeeping" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="Paab" /> <!-- aerial reach --> <flags id="Pcoa" /> <!-- command of area --> <flags id="Pcom" /> <!-- communication --> <flags id="Pecc" /> <!-- eccentricity --> <flags id="Phan" /> <!-- handling --> <flags id="Pkic" /> <!-- kicking --> <flags id="Pooo" /> <!-- one on ones --> <flags id="Pref" /> <!-- reflexes --> <flags id="Prou" /> <!-- rushing out --> <flags id="Pttp" /> <!-- tendency to punch --> <flags id="Pthr" /> <!-- throwing --> </record> </record> <record id="deat"> <translation id="name" translation_id="247413" type="use" value="Defensive" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="Pacc" /> <!-- acceleration --> <flags id="Pant" /> <!-- anticipation --> <flags id="Phea" /> <!-- heading --> <flags id="Pjum" /> <!-- jumping --> <flags id="Pmar" /> <!-- marking --> <flags id="Ppac" /> <!-- pace --> <flags id="Ppsn" /> <!-- positioning --> <flags id="Psta" /> <!-- stamina --> <flags id="Pstr" /> <!-- strength --> <flags id="Ptac" /> <!-- tackling --> </record> </record> <record id="atat"> <translation id="name" translation_id="230042" type="use" value="Attacking" /> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="Pnms" /> <!-- person name --> <flags id="Pcro" /> <!-- crossing --> <flags id="Pdri" /> <!-- dribbling --> <flags id="Pfrk" /> <!-- free kicks --> <flags id="Pfin" /> <!-- finishing --> <flags id="Pfrs" /> <!-- first touch --> <flags id="Pfla" /> <!-- flair --> <flags id="Plsh" /> <!-- long shots --> <flags id="Potb" /> <!-- off the ball --> <flags id="Ppas" /> <!-- passing --> <flags id="Pcre" /> <!-- vision --> </record> </record> </list> </record> <record id="----" /> <record id="debg"> <translation id="name" translation_id="247109" type="use" value="Debug" /> <!-- Define attributes/properties to view in this view type on the panel. Any properties not defined here will be hidden for this view. --> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="duni" /> <!-- unique id --> <flags id="Pnfo" /> <!-- player status/info --> <flags id="PSag" /> <!-- person age --> <flags id="Pnms" /> <!-- person name --> <flags id="PCAB" /> <flags id="PPAB" /> <flags id="PPPA" /> <flags id="PCRP" /> <flags id="PHRP" /> <flags id="PWRP" /> <flags id="Pcbv" /> <flags id="Pdva" /> <flags id="Pnar" /> <flags id="PCAP" /> </record> </record> <record id="debc"> <string id="name" value="Contract Debug"/> <!-- Define attributes/properties to view in this view type on the panel. Any properties not defined here will be hidden for this view. --> <record id="view"> <flags id="PtsL" /> <!-- picked info --> <flags id="duni" /> <flags id="Pnfo" /> <flags id="PSag" /> <flags id="Pnms" /> <flags id="Pcpt" /> <flags id="Pced" /> <flags id="PCRC" /> <flags id="PCRN" /> <flags id="PCRV" /> <flags id="Pdva" /> <flags id="PMRV" /> </record> </record> </list> </widget> </container> </container> <!-- panel showing squad selection rules for the next match --> <widget class="match_squad_info_panel" id="ssnm" navigation_container="true"/> </container> </panel>
Edit2: I've also noticed that I have to reload the skin in order to see changes that I make on @_Ben_'s Statman skin. On my skin, I can just switch to a different screen, and switch back, and I can see all the changes I've made to that xml file without reloading the skin. So that might be the cause of it resetting. Then again on the Statman skin, home page's Personal information part does the same thing, where the information resets/goes blank if you switch to another screen.
This is painful
0 -
Nothing major game changing or unique here, just messing around with different layouts, using inspiration from other creators, as usual. Trying to make it look as good as possible, while also displaying some info that makes sense for the screen. Had no idea what to put in the left container, so I just placed a selector panel showing league table, it works I guess.
Probably gonna do all other screens in this style, Inbox already is in this style by default, Tactics screen is kinda similar, and I want to see how Player profile will work (main bit of player info on the left, with everything else on the right in large tab container, with selectors, other tab containers etc.).
7 -
1 hour ago, Loda said:
The full squad list and the tactics squad list (match tactics incl.) do all use the same id so I have my doubts based on this and general logic but...
Just as I feared...
1 hour ago, Loda said:Rather than point it to a panel (I'm assuming you're doing that with tesA). Have you tried pointing it to the actual table and id I allude to above?
... i.e.
If I was intent on this, I would play with the 3 variables in every permutation (i.e. tesA, pltb and the file locations, I'm unsure if pltb is tied only to the team and match folder and/or if tesA is tied only to tactics and match...(?)).
So in essence just a bit more experimentation suggestions.
I've already tried just copying that whole section of code, but without much luck.
My brain is pretty much stuck right now, and I have no idea how I would solve this. I've tried a few different things, but without any success.
Edit: Also my game now appears to be crashing when selecting custom views in that screen. On all skins, even the default. It doesn't happen when importing a view, but when selecting a saved view in that menu. Weird
0 -
I've been messing around with the tactics screen (shoutout to @_Ben_ for this beauty), I liked the idea of having tabs inside, with some different arrangements of tactics screen items.
I want to have 2 squad views, one to the right of the tactics pitch, and another on a separate tab.
I messed around with not having the squad list on the primary tab, but it's just too many clicks to go out and swap players, etc. So I want to have one smaller version on the primary screen, and another full version of the squad list on another tab.
Spoiler(My previous version had the horizontal tactics pitch covering the entire screen, with instructions to the left. I also tried separating instructions into another tab, but that also didn't seem to work, especially because comparison/player instruction popups would be on 2nd tab as well). Basically I was trying to replicate some of this, after not working on anything for a few months, but I'm just not sure anymore if it's doable, and I definitely don't have the knowledge on how to actually do it if it is possible.
The issue is, you can't place the same id twice and expect both to work. So it will work on one screen, but not the other.
I can't set a custom id, as some id is definitely required in order for the squad list to actually show up. I have no idea how to find other id's that show the squad list. This one uses the id="tesA", and the panel class is "team_squad_tactics_panel". I'm pretty sure I could use another class, but I'm not sure about the ID, as the game definitely seems to want a certain hardcoded id.
And btw, is there any way to convert those familiarity/intensity into pie/donut charts? I've tried, but it didn't seem to work.
0 -
3 minutes ago, _Ben_ said:
In my most stupid/creative moment yet, I've created thirty two new classes in order to show a rating for statistics. This is how it looks right now:
To explain...
I took data from nearly 4,000 outfield players in European top flights with over 2000 minutes and created some percentile values linked to colours.
- No data - background
- Below the 25th percentile - background
- 26th to 50th percentile - red
- 51st to 75th percentile - light blue
- 76th to 90th percentile - dark blue
- 91st to 100th percentile - gold
Yeah, so, that's what I've made tonight! Let me know what you think and, without spoiling too much, be prepared to be amazed at what @GIMN is creating because we've been sharing a few ideas on this and, to be honest, his blows this out of the water!
See, now this changes things a lot for me. I personally wasn't a fan of pure stats/data based skins, because I had no way to interpret and compare that data.
I don't know if x number of y is good or bad, but now with this, I can easily see if that certain stat/piece of data is something good or bad (like you can do with fbref for example).
Brilliant work yet again.
0 -
38 minutes ago, ElJuanvito said:
Sorry if I wasn't clear, I don't want the lopsided defensive line.
We've struggled with this for years now, it's not really possible to make it not lopsided and for it to perfectly resemble a back 3 in buildup/possession. Although there are a few ways to make it somewhat work.
You could use something like this. In possession you would have a back 3, and in defense it kinda does work like a back 4, where the RCB will shift to the RB spot, kinda...
1 -
Wingbacks kind of do everything.
Sometimes Dalot (more so than AWB I think) sits narrow, in the midfield to form a double pivot, an IWB-S basically. Sometimes he would underlap while the winger stays wide, and lurk around the edge of the box IWB-S/-A. And sometimes, if the winger is narrow, he would overlap like a regular Wingback-S/-A.
Similar thing happens on the other side with Shaw/Malacia. Sometimes he would form a back 3 with other 2 CBs, and sometimes Eriksen drops deep to form a back 3, while the WBs push higher. They often do use this 3-1-6 shape, and sometimes they use 3-2-5/2-3-5.
Recreating all of that is kinda impossible in this game. Movement and positioning is way too fluid and interchangeable, where players need to occupy certain positions based on where the other teammates are positioned. You could make a very rigid replication, where a RW for example, would always stay wide, and where the RB would always sit narrower and underlap. Or you could do it the other way around where the RW always sits narrow, and WB always overlaps, but I think the first version would be closer to real life. You could also add a overlap to IWB-S to encourage him to make those overlapping runs when there's opportunity to do so.
Replicating Eriksen dropping deep in the buildup to form a back 3 with 2 CBs, while the WBs are pushed forward, is simply impossible. It's similar with using one fullback to form a back 3, but at least it does work sometimes.
I'm not sure whether I'd use a 4-2-3-1, or a 4-1-2-3 (4-3-3), as those also change often. I really dislike the 4-2-3-1 (both with DMs and CMs) in FM23, as the AM, even on Support duty is often placed right on top of the striker in a lot of situations, and he would often go to the side of the striker to from a front 2. And that's on support duty.
0 -
On 26/01/2023 at 08:28, _Ben_ said:
Looking to get a little bit of feedback on these please:
I can use attribute bars to show strength in different areas, creating almost a comparison. I, personally, find that I get very little from the personality/media handling of a player and - essentially - I now know what constitutes being a Model Citizen etc so this just helps show that a little differently. There are things like consistency that show up on scout/coach reports so it's not like it's new but I've always been against show hidden stuff for some reason - with the rationale that 'it's hidden for a reason!' Therefore, I started to create a few with some attributes too but I'm less sure of that anyway - mainly because you can only show one attribute, rather than a collection of several.
What do people think about these? Do you prefer personality stuff or attributes? Would you use them if they were in a skin/put them in your skin?
I love it. I don't know why some of the attributes are hidden, and I definitely want to see what the player is really like, but I also feel weird when I view those attributes on a 1-20 scale (feels like cheating).
I'd definitely put this in my skin.
0 -
2 hours ago, hyrule_king said:
What do people think of the colour scheme, need to go through and sort out all the buttons etc...
1 hour ago, hyrule_king said:Its a bit like the coffee one I did , it wasn't too every taste. Is there anything in particular that your not a fan of?
If it was for personal use, I'd just say go for whatever looks good to you. But since you asked..
That color just isn't well suited as a background color, its simply way too strong and there isn't enough contrast when looking at other items, mainly the text. Black text doesn't have enough contrast when compared to that orange background, it needs to stand out more.
To solve this, you should pick a darker and a more gentle color as a background, and change all text to white, or use a much lighter background and dark/black text (which is much harder to do, as there's probably a ton of text that needs to be changed in a few dozen different xml files).
I know most people here probably don't have any knowledge of color theory, other design principles (contrast in this case), or modern design trends, as most of us are just doing this for ourselves, for fun. But I would suggest reading up on it, and learning some of that stuff, as it can greatly help with designing nice color schemes, and good looking skins.
2 -
On 13/01/2023 at 23:30, bababooey said:
- Pressing is.... Weird. Hear me out. It feels like pressing is, at times, both insanely powerful and completely ineffective. "What do you mean, that's not possible." Well, it just depends on the context.
There are WAY too many instances of players being caught in possession with nobody near them. This typically happens to a DM or CD. They'll receive a pass in an area that is basically wide open (given their position you can understand that would happen) and all of a sudden, someone is closing them down like a bolt of lightning, and the ball ends up in the net. This happens both FOR and AGAINST the user. This seems entirely unrealistic to me. At least, at the frequency it's currently happening at. The player is in acres of space just doddling on the ball. Are they blind? Unable to see someone charging at them from like 25+ yards away? This happens so often.
There are also way too many instances of players not pressing at all. Or, said differently, teams that play very deep and cautious are able to just cycle possession back and forth between their defenders far too easily.
Absolutely. Pressing just doesn't work in any sort of a realistic way. The game overall just doesn't feel fluid, and you can obviously spot some triggers if you watch enough matches. Like players just wouldn't do anything, but as soon as X thing happens (or when the ball reaches the middle or final third), they completely change their behavior, from 0 to 100. The problem is, we can't control those triggers, or at which point we want players to change their behavior. It just happens suddenly after a certain invisible line is crossed. It's hard-coded, and we're at mercy of the devs and the way they see football and deem it should work in-game.
Your players often can't really play a high press, as the CBs (and/or fullbacks) will be left with tons of space to recycle the ball, without being closed down (even when they're closed down, they can make pin-point passes under pressure). It was an issue in previous versions as well, where players just don't close down as much, until the ball comes to the middle third, when all hell breaks loose, and they suddenly start closing down the player with the ball.
So many players are left open, with tons of space, it's almost like marking is non-existent.
It goes without saying that allowing us that much freedom will inevitably lead to game-breaking, exploit tactics (though you could argue they already exist).
The other option isn't that much better either, as it would require an even more complicated and complex code, leading to an even more realistic simulation of football, and I doubt that's happening any time soon.
Since a realistic representation of football/tactical creator isn't on the table, what they should focus on is making the game feel more like....a game. That means gamifying certain areas, so they don't feel like a chore and a 2nd job.
Anyways, it's been a while since I posted feedback in this thread, mostly because I just stopped playing the game. I just got tired of seeing the same old stuff, the same old mistakes and bugs, the same old inability to create and replicate certain real-life tactics, which includes player movement and positioning, etc.
The game strives to be as realistic as possible, but it's so far off from being that. Maybe my expectations are high, but after playing this game for 6-7 years, I haven't seen that much progress in that area (not saying there wasn't any, as that would be a lie).
2
I think Football Manager's formation system needs to change to keep up with modern football.
in Football Manager General Discussion
Posted
But nobody's saying that it is, or that it should be a "crazy tactics simulator". It's about creating realistic representations of real life tactics.
The argument against it, was how the AI couldn't keep up, and their argument is how they don't care, as it is a single-player game, and the way you play the game doesn't affect others - if you want to exploit it, you do you, if you don't want to exploit it, then just don't. I don't know how you managed to get the "crazy tactics simulator" from all of that.
A CM/DM moving to RB in possession, isn't crazy, and it's something that does happen in real life. Just like a RB moving more narrow to form a back 3 and act as a CB is nothing new nor crazy.
Pep's tactics and his usage of space is nothing new. He just finds new ways to do it, latest example Stones moving from CB to DM like a libero. This is already in the game, except you can only use the Libero role in the middle of a back 3.
The way the tactics system is designed is very rigid. Roles/duties are just presets you're allowed to play with, you don't have much say on how you want them to move or what positions to occupy in the buildup, in the middle third or in the final third, just like you don't have a say in how they play in transition or defence. That's already determined by the devs and their interpretation of what a role should be and how it should move and play. Your job is to select whatever preset the devs have given you, and hope it matches what you actually want the role to do.
The thing with that is, it may have been okay 10 years ago, but nowadays it is possible to create something better - and I'm also including a smarter AI here, as the technology has improved massively from the days of FM12/13.