1 Ordered list (repeating some of the below)
2 -----------------------------------------
4 1. Fix empathy bug with rejoining (Andrew as Zombie)
6 2. Finish implementing Empires
11 Allow players to see what their current name is (currently
12 disappearining among the list which is sorted by overall score) and to
13 change their name if desired.
15 Fix bug Andrew saw where he went into a Zombie mode: He left the game,
16 and came back. When he was back his word scores were shown, but his
17 name was left off the round scores, stayed gray in the overall scores,
18 and the overall score was never increased.
20 Bisect and fix some test-suite regressions introduced recently.
22 Features (likely) requiring only client changes
23 -----------------------------------------------
24 * Make new categories appear at the top of the list
26 Note: We may not want this for sake of keeping the UI stable---this
27 is already a bit of a problem with the "Start Game" button which is
28 now appearing at the top of the list of categories. What I mean by
29 "stability" of the UI is that we don't want a user to be reaching
30 out to tap a vote button for a category and then have the category
31 vote button shift to a different location before they reach it.
33 * Make the "vote_against" button move a prompt down to the bottom of
34 the list and gray it out. This could be a better approach than
35 making the category entirely disappear.
37 * Un-gray-out a prompt when a player votes for it
39 * Make scores available at screens other than the category-selection screen
41 Add a TWINNER achievement
43 Add support for item counts as words, such as "three little words"
45 Allow clients to see previous round scores by swiping left
47 Figure out why Nancy's computer doesn't work at all
49 Auto-focus first text field
51 Style focus highlight for TAB-based navigation
56 Convert HTML/JavaScript client to React
58 Add UI for combining/splitting empires, (modeled after the judging
59 interface in Empathy).
61 Add a chat interface for sending messages to the current empire (with
62 no history beyond a single message per sender)
64 Fix bug that allows people to re-reveal characters after game has started.
66 Flempires (flutter-based client)
67 --------------------------------
69 Experiment with minimal flutter build environment (only lib/ in git)
71 Bring client up to latest Empires API approach
73 [X] Pre-allocate a game ID in the server for flempires to use (QRST)
75 [ ] Change flempires from using https://families.cworth.org/api to
76 instead use https://lmno.games/empires/QRST
78 [ ] Add UI to ask user for a game ID, (obviating the QRST ID)
80 [ ] Add UI to generate a new game ID, (allow flempires to work on its own)
82 curl -X POST https://lmno.games/new/empires
83 Returns: "WLJG" (or some other game ID)
85 [ ] Implement player registration by POSTing to /register (without cookie)
88 -H 'Content-Type: application/json' \
89 -d '{"name": "Carl", "character": "Elvis"}' \
90 https://lmno.games/empires/QRST/register
91 Returns: 1 (or some other player ID)
93 [ ] Implement registration with /profile and then /register
95 Note: This approach requires obtaining a cookie from the
96 /profile request and then providing that cookie on the
97 subsequent /register request. The -c and -b command-line options
98 of curl can be used to demonstrate this:
101 curl -c cookie-file \
103 -H 'Content-Type: application/json' \
104 -d '{"nickname": "Cookie"}' \
105 https://lmno.games/profile
106 curl -b cookie-file \
108 -H 'Content-Type: application/json' \
109 -d '{"character": "Cookie Monster"}'
110 https://lmno.games/empires/QRST/register
111 Returns: 2 (or some other player ID)
113 [ ] Listen to the /events stream for the game
115 This will require an asynchronous mechanism that is continually
116 listening for events to come in. Events will be of the form
117 "event: <event_type>" followed by the data of the event "data:
118 <json_data_for_event>" followed by a blank line. There will also
119 be periodic keep-alive non-events sent which are just a line
122 This mechanism is called "Server-sent events" so you may find
123 code that supports the parsing of this. Or you may not. It
124 doesn't seem like this mechanism ever became all that popular
125 (before websockets came along and became popular).
129 curl https://lmno.games/empires/QRST/events
133 data: {"id":"QRST","url":"http://lmno.games/QRST"}
136 data: {"id":5,"active":true,"name":"Cookie","team":""}
139 data: {"id":2,"active":true,"name":"Web","team":""}
142 data: {"team_to_play":{"name":""}}
145 data: [{"id":1,"name":"Carl"},{"id":2,"name":"Cookie"}]
148 data: {"old_phase":"none","new_phase":"join"}
153 Fix server to reject illegal moves (not following the previous-move
156 Extend test suite to cover legal and illegal scribe moves
158 Constrain glyph diagrams to not overflow page width
160 For a very wide display, put glyph diagrams on the side of the game
161 board instead of below.
163 Detect glyphs and highlight background of squares belonging to glyphs
165 Detect winner of mini-grid and overlay sumbol of player on mini-grid
167 Declare overall winner (both in "majority" and "superglyph" mode)