OOTP15 Improvements

olivertheorem · 08-19-2013, 11:22 PM

I think I posted at least one of these before, but I'm doing it again. (So there :P)

1) Ability to export draft pool only to CSV file, with the output based on the current view. For example, if you have it set to show name, handedness, and stuff/movement/control potential, then that's what you get in the CSV.

2) SOME kind of player projection model in-game. MARCELS would be simple enough to do, I'd think, and while it's not as accurate, it's also not too shabby. The greater inaccuracy of MARCELS would provide a little bit of fog-of-war as well.

That said, since the game does have the ability to calculate similarity scores (I've only seen them on the player comparison screen), why can't we go whole hog and have PECOTA (or at least PECOTA-lite)?

In either case, it could be stuck in the same spot Markus' put the new real-life stats row for historical leagues. Plus, to "disable" it all he'd have to do is hide the output row.

3) Ability to "ask" for specific positions on the trade block, as well as to specify veteran vs. prospect, or any combination of the above. I can see how this would be harder to make work correctly, but if the AI can be made to react appropriately it would make swapping from strength to shore up a weakness easier (I know the AI tries to make trades based on what IT perceives as weakness, but the AI and the player do not always agree on this).

Failing that, some way to filter the "shop player" results by position/age. I don't like scrolling through a bunch of guys I really don't want just to find the prospects that I'm being offered.

08-19-2013, 11:22 PM	#1
olivertheorem All Star Starter Join Date: Jun 2006 Posts: 1,919	OOTP15 Improvements I think I posted at least one of these before, but I'm doing it again. (So there :P) 1) Ability to export draft pool only to CSV file, with the output based on the current view. For example, if you have it set to show name, handedness, and stuff/movement/control potential, then that's what you get in the CSV. 2) SOME kind of player projection model in-game. MARCELS would be simple enough to do, I'd think, and while it's not as accurate, it's also not too shabby. The greater inaccuracy of MARCELS would provide a little bit of fog-of-war as well. That said, since the game does have the ability to calculate similarity scores (I've only seen them on the player comparison screen), why can't we go whole hog and have PECOTA (or at least PECOTA-lite)? In either case, it could be stuck in the same spot Markus' put the new real-life stats row for historical leagues. Plus, to "disable" it all he'd have to do is hide the output row. 3) Ability to "ask" for specific positions on the trade block, as well as to specify veteran vs. prospect, or any combination of the above. I can see how this would be harder to make work correctly, but if the AI can be made to react appropriately it would make swapping from strength to shore up a weakness easier (I know the AI tries to make trades based on what IT perceives as weakness, but the AI and the player do not always agree on this). Failing that, some way to filter the "shop player" results by position/age. I don't like scrolling through a bunch of guys I really don't want just to find the prospects that I'm being offered.