|05-15-2015, 04:45 PM
Join Date: Oct 2000
Location: Canton, OH
Specific Interface Question 1: Player Stats
I'm going to further break down my interface thoughts.
In general, my theory is that the game is a workplace, and you should be able to set it up to fit your screen. Open the game, move windows where you like them - if you have screen space then you should have the opportunity for several windows.
Player Cards are difficult. The "old" idea was to present them like you present a football card. One "side" is mostly career stats, the other "side" is player information and links to actions.
One idea that's been presented is to use the card to show only the most recent season of stats, and only the stat set most relevant to that player's position. You would then click on a button or that stat field to show the full statistics card.
That way, the player card can be completely reorganized to feature ratings, player information, etc. The down-side is that you'd be one more click from the player stats, one more click from the award list, one more click from the transaction list.
Does this seem like a good idea? Which lists should be as they are now - fully iterated on the main player card? Which lists should be one click away? Is scrolling acceptable for all lists or just some lists?
Thanks for your thoughts.
|05-16-2015, 07:15 AM
Join Date: Nov 2004
Location: Newbury, England
I like the new idea of having ratings and current season stats on the front page, and clicking through to get full details.
Although you can argue that you are one more click away from certain screens, with more info on the front of the card by definition you must also be one less click away from certain info, and you have to click through to get stats anyway atm, so that sounds like it would remain unchanged.
With a player front card being a player home page it should also allow more cope for creating a softer, more appealing look to modernise the GUI and hopefully attract more new players.
'A song is a beautiful lie', Idlewild, Self Healer.
When you're smiling, the whole world smiles with you.
|05-16-2015, 06:45 PM
Join Date: Mar 2011
I like the idea, it would be nice if all the info available during draft time combine was was available for the player later on. Like Sol. You join a league a see players for trade namely QB's but are missing some important info on figuring them out.
Had you been in th eleague when the player was drafted you'd likely know that.
Thank you Nawlins fan and Shanethemaster for the helmet/logo work for the Richmond Rhinos of the WOOF.
|05-17-2015, 09:32 PM
Join Date: Nov 2003
I'd go for, perhaps, the past three years worth of the basic stats on the front of the player card, and then the rest of the stats being a click or two away wouldn't bother me much. More or less, the most important 4 to 6 stats would suffice on the front of the card...
Award list and transaction list are secondary information to me. Perhaps there could be some flag on the front of the player card that indicates whether a player has a notable injury history, but, other than that flag, the actual injury list is secondary as well...
|05-17-2015, 09:34 PM
Join Date: Nov 2003
Dola, scrolling for stats is a pet peeve of mind. I'd encourage the player card not to have scrolling. For information that needs to be scrolled, I don't mind that being a click away.
|05-19-2015, 02:35 PM
High School Varsity
Join Date: Nov 2010
Location: Near Cleveland
Yeah, I'm a fan of how OOTP handles stats. You're never going to have all the stats on one screen, so clicking through is going to happen regardless.
But to have some basic box score-esque* stats on the same page as ratings? Yes, please!
Unless, of course, you'd like to go on record and say that bars > stats and you can ignore stats completely.
*Catches, yards, TDs; etc.
|06-16-2016, 10:39 PM
Join Date: Dec 2003
I think the OOTP\FM model for player cards is the best and I would vote to emulate that
but then again I think the GUI of those games is far and the away the best I have seen in all games and I think emulating that whole model would be best
|Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)