Jump to content

jkadms

Members+
  • Posts

    67
  • Joined

Everything posted by jkadms

  1. This is only true if the attributes aren't set to attribute label, though if attributes are displayed on one page using a class to assign an image based on the attribute value, which I think they are in the mustermann skin, then it's also possible to display the attributes on a seperate page, as is the case with the statman skin
  2. you can do, this is the panel that controls the popup buttons at the bottom of the match screen (quick sub, tactics, mentality etc) just check the file from the wtcs skin and make sure it doesn't reference any other files, as if it does you will also need to transfer those over
  3. Yeah that would've been better lol. I tried the code that you just posted an unfortunately it still isn't populating with the traits. This is the code that I was using. I also tried referencing a different preferred moves file and still got nothing, <!-- Traits --> <container class="tcs_table_trans" transparency="0.8"> <layout class="stick_to_sides_attachment" alignment="horizontal" apply_to_children="true"/> <layout class="arrange_vertical_attachment" layout="15,-4" gap="0"/> <widget class="label" alignment="left,centre_y" colour="faded text"> <translation id="text" type="use" value="Traits" /> </widget> <container class="scrolling_box"> <widget class="preferred_moves_panel" file="player/tcs/tabs/popup/player information preferred moves profile" id="pfmp" alignment="left,centre_y" auto_size="vertical"> <record id="object_property" get_property="objt" set_property="objt" /> </widget> </container> </container
  4. Anyone know why I can't get traits to populate on the player popup panel? Within the player attributes popup panel Tried using a couple of different traits panels and also added <record id="object_property" get_property="objt" set_property="objt"/> in a couple of places but nothing has worked
  5. Decided to make a light version of my skin! Once again won't be releasing as there isn't much original content in here
  6. Yeah this is possible, you'll need to replace the attributes with the bars. Not sure where the attributes are located in the current version of the skin, but the bars should be located at Statman1.6/panels/player/Tabbed/main/attributes/player stats no polygon attribute panel.xml
  7. Well I did use your skin as the base, so I didn't have to create that much from scratch. Honestly the work that everyone in here does is incredible, I had a lot of trouble whenever I had to figure something out for myself instead of just moving around things that people smarter than me had already created lol I appreciate the compliment, though! I'm very happy with the skin and excited to actually, you know, play the damn game now
  8. Thank you! This panel is the one that I'm probably proudest of, just a little frustrated that I can't get the 'games played in position' to populate! It would help with putting the stats into context The only one that is a single value is flair, couldn't really think of an appropriate grouping for that one A couple of others are weighted, since your design for the bars requires three attributes to make up the full bar. I don't actually mind this though, as the weightings help imo. So crossing is crossing, crossing and technique Physicality is strength, strength, and jumping reach Long shots are long shots, long shots and technique Quickness is pace, pace and acceleration The rest of them are all 3 attributes, but some of them are changed from your skin
  9. Almost finished with this TCS x Statman x Mustermann Frankenskin with a couple minor additions from other skins as well Not going to be releasing as it takes far too heavily from other skins, although I am happy to share some stuff that I worked on myself (mainly the classes and graphics for the charts / attributes) with @_Ben_ @TCSSkin and @GIMN if they want to use anything here in their own skin It took an embarrassingly large amount of time to make, as I had 0 prior skinning experience. The majority of the work went into the minor details, as I am very picky with regards to aesthetics so getting things to be perfectly aligned took a while. Also extra details such as data collection for the FBREF / Pizza charts that scales based on position group etc. And also quite a few panels that aren't shown here. Really happy with how it turned out, and am especially pleased with the player comparison page Sidenote: If anyone has any clue how I can get the 'games played in position' table to populate on the player comparison page, that would be great. I tried putting so many <record id="object_property" get_property="objt" set_property="objt"/> into the code but nothing worked lol
  10. How can I change the contents of a container based on whether a player plays for my club or not? I have a few selector panels that keep resetting / overwriting each other when going between players who are at my club and ones who aren't, so to get around this I just want to have the contents of the containers be fixed
  11. The player profile page really is incredible, I think I'm gonne have to ditch the one I was working on for my own personal skin and just use this with a few tweaks I have noticed a minor issue with one of the features, though. When I go onto a player's profile, the positions button isn't active until selecting and then deselecting the custom report button
  12. Ah ok, suppose that's why it did nothing then Yeah! I just set up a google sheets formula to do the hard work for me so all I had to do was copy and paste into the classes, most of which already existed Last step now is creating the 100 unique pictures for each threshold. Happy to share the classes with you when I'm done if you'd like them for your own skin, it is still mostly your work that I'm using after all
  13. Unfortunately no success, as I said I'm a little unsure what I'm doing in that area so just tried a bunch of random things hoping they would work They're all in the person properties.xml, AMR for example is: <!--AMR--> <record> <integer id="id" value="Pamr" /> <integer id="width" value="48" /> <translation id="name" translation_id="248647" type="use" value="Right Winger" /> <flags id="customisation_context" value="none" /> <boolean id="sort_ascending" value="false" /> <record id="widget_edit_info"> <symbol id="class" value="number_edit_box" /> <flags id="edit_event" value="CDBd" /> <integer id="min_value" value="1" /> <integer id="max_value" value="20" /> </record> <record id="column_widget_properties"> <flags id="alignment" value="centre" /> </record> <record id="column_heading"> <flags id="alignment" value="centre" /> <translation id="text" translation_id="349062" type="use" value="RW[COMMENT: right winger]" /> <translation id="hint" translation_id="248647" type="use" value="Right Winger" /> </record> </record> I tried assigning those id's for each position to the relevant chart like this: <record id="object_property" get_property="Pamr" set_property="Shwn" /> And a few other random solutions but nothing worked. I just settled on creating an overall chart, with unique metrics for each positions and more granular steps (0-100). Still a work in progress but it's almost done
  14. No worries! Is it possible to create properties? So a property could be created based on a player's ability to play a certain position? Or potentially for the charts to be displayed by default based on other criteria? Maybe some custom classes could be created based on positional ability? I know that when you click on a player's profile, certain positions are highlighted by default based on staff's assessment of the player's best position / role , so I wonder if there's a way to link that to the correct chart. As I said, this is the part of skinning that I'm not as knowledgable on, so I appreciate the response even if nothing can be done If not I'll probably just create a general chart that's displayed by default for everyone to keep some consistency, and then just use the buttons for each individual position as and when it's needed. Amazing work with the skin, by the way EDIT: Just had a poke around in person properties.xml and there are properties based on individual positions with values of 1-20. There has to be a way to link these with the charts. I'll have a play around with it today
  15. of course, just tried to make my question as general as possible as i have it mostly figured out, just need to find the right ID if it exists when things get to properties and widgets etc i'm a little out of my depth since information on that area seems harder to come by thank you!
  16. I'm looking to edit the default FBref charts from the statman skin. At the moment, the default chart is set by properties "pide" for defenders, "pimi" for midfielders etc: <record id="object_property" get_property="Pide" set_property="Shwn" /> But that results in many situations as shown in the attached picture, where the chart for a DM is shown for a winger, or CB is shown for a fullback etc. I've tried stuff like "pifb" or "piam" but they dont' seem to work. Also haven't been able to find anything like that in person.properties.xml in any of the skins that i have dowloaded, or the default skin. Are there any properties specific to each position? Or would it be possible to make them?
  17. Looks incredible! Seems like you've fully ditched the attribute groupings then Is there any chance that, if you aren't realeasing this skin, you could share the DNA bar there? Would love a DNA indicator but not really a fan of the attribute polygons
  18. I have edited a widget so that it shows personality for players on my team, and media description for everyone else. Is there a way to make it so that players on other teams, but only those who have been scouted, can show personality as well?
  19. Hi, is there any chance that anyone could tell me the xml files that specifically control the area of the performance hub and the old attributes hub from 1.1 that are shown in the screenshots? The skin is quite complex so I'm having a bit of trouble pinning down the exact areas
  20. Does anyone know how I could remove this button in the news tab? WTCS skin with all news panels / folders removed so it reverts to default if that makes a difference
  21. In fairness, how often do you see this in real life? Doubt Liverpool would strip VVD of the captaincy if he did his ACL again. That's what vice captains are for.
  22. As said in the title, injuries that happened after the your world cutoff date are still there in game. Olise and Timber being the big two that I've noticed so far.
  23. On Timber's injury, even when starting a game in the 'Your World' mode, where everything should be as it was on July 3rd, Timber is rightly still at Ajax, but also still has the ACL injury he picked up at the start of the season. Injuries sustained after July 3rd should also not be included in this mode.
  24. found it and it's working perfectly now, thank you so much
×
×
  • Create New...