# HG changeset patch
# User alys
# Date 2021-05-08 21:30:05
# Node ID 1b9e291d8552954d07cbe17592c1f8f75681ab62
# Parent  b7992263d80c34283e081ff7251088f56717de7a

Loads of new ideas, many from thinking about when I'm not coding and some from just now.

Note that instead of doing leisure next, I'm doing events next. I honestly might switch back
but I have ideas for dialog that fit nicely into a focus on events.

diff --git a/TODO.taskpaper b/TODO.taskpaper
--- a/TODO.taskpaper
+++ b/TODO.taskpaper
@@ -47,8 +47,8 @@
 		Don't want to be too derivative
 		- Employee training mechanic @maybe
 	Leisure:
-		- Add way to mark off area for leisure  @milestone(4: Leisure)
-		- Basic satisfaction @milestone(4: Leisure)
+		- Add way to mark off area for leisure  @milestone(6: Leisure)
+		- Basic satisfaction @milestone(6: Leisure)
 		- Set 
 	End games/outcomes:
 		- Financial mismanagement @milestone(5: Events)
@@ -92,7 +92,7 @@
 Structure:
 	- Add modes @milestone(5: Events)
 	- Refactor stuff out of FNAGame
-	- Saving @prototyped
+	- Saving @prototyped @milestone(4: Beginning)
 	- Encompass @maybe
 		Currently thinking about a hybrid model where the Simulation class receives a lot of the events from Encompass. so things like Events, Contracts, and Research agreements are handled by Encompass. Perhaps Input, too?
 		- Ensure library loads
@@ -101,18 +101,54 @@
 			- macOS
 	- Decide how to handle ImGUI ref parameters
 		Basically have to decide whether to embrace its style or go toward a more functional approach
-		
+	- Add a start screen @milestone(4: Beginning)
+	- Add a create park dialog @milestone(4: Beginning)
+		- Procgen park names (that player can override)
+			- Button to generate new name?
+		- Allow player to choose title @maybe
+			Some possibilities: Mr., Ms., Mx., Director, Dr., Professor, Miss, Col., Herr Dr. Dr. nothing, custom
+			Might be fun to have tiny acknowledgement of choice — probably dialog only, no mechanical change. (E.g., a researcher might allude to you having a PhD. or an enby character might say something comiserating.)
+		- Allow player to choose difficulty
+			I'm thinking: Easy would be constant subsidy, Medium would be declining subsidy, and Hard would be none.
+			Could name them Benevolent, Austerity, and Hostility? Or Conservationist, Austerity, Libertarian? (Maybe too pointed!) I kind of like describing these as the government's "orientation" or "attitude" toward park.
+		- Allow player to choose profile image @maybe
+			Same style as rest of the game (dithered b&w, at least right now)
+	- Basic In-game menu @milestone(4: Beginning)
+		At minimum, New Game, Quit, and Quit to Menu
+	- Graphics options
+		- Add to in-game menu
+	- Additional in-game menu
+		- Save
+		- Save & Quit
 
 Other features:
 	Accessibility:
 		- Verify contrast
 		- Option to Increase display size
-		- Option to Turn off bad outcomes or disasters?
+		- Option to Turn off bad outcomes or disasters @maybe 
+		- Dyslexic-friendly font @maybe
+		- Screen reader support @maybe
+			Would probably be a big undertaking (sort of opposite to the web, where things tend to be accessible unless you start reimplenting things or going more advanced)
+			- Investigate .NET support for screen readers
+			- Ask on social media
+				- Moontools Discord
+				- FNA Discord
+				- Mastodon
+			- Figure out a good screen reader to use for testing
+				- macOS
+				- Windows
+				- Linux
+			- Look for prior art
+			- Add a "describe" button/key that speaks the current scene @maybe
+			- 
 	Other QoL things:
 		- Adjust display size
 		- Toggle trees translucency
+			Right now we hide trees outright, which probably should be limited to debugging
 		- Right click to center
-		-
+	Internationalization:
+		- Probably won't pay to translate or anything, but should consider setting up the structure @maybe @milestone(4: Beginning)
+			If nothing else, might be useful for future projects.
 Bugs:
 	Graphics:
 		- Trees jump around when pressing show/hide grid