2025-04-19T04:57:48Z - 2025-07-19T04:57:48Z
Overview
16 Pull requests merged by 1 user
Merged
#331 Move the background into the true background
Merged
#330 Render character sheet sidebars for both the GM view and the Player view
Merged
#329 Switch back to trunk
Merged
#328 Set up the host and server to work separately from Trunk
Merged
#327 Set up automated tests for Visions
Merged
#326 Remove the date window reset code
Merged
#319 Fade images and limit the size of the player UI
Merged
#318 The game state is now encapsulated in a dispatcher which can route requests
Merged
#317 Apply a distinction between the Admin, GM, and Player user roles
Merged
#315 Load game views via the websocket
Merged
#314 GM View of the game
Merged
#313 Make Dashboard installable
Merged
#308 Create a user interface for managing a game
Merged
#309 Add usage information to cyberpunk-splash
Merged
#307 Set up nested routes for dealing with the design page
Merged
#305 Create the user management interface
11 Issues closed from 1 user
Closed
#325 Move the background image to the true background
Closed
#273 Serve the Candela character sheet from database
Closed
#268 Create a Candela Obscura character sheet structure
Closed
#270 Create a renderer plugin for the Candela character sheet
Closed
#199 Preserve the historical view range when entering a day detail view
Closed
#310 Player View of the play area
Closed
#257 Players must be able to see the background image that the GM has selected for the play area
Closed
#259 GM View for the play area
Closed
#316 Enforce the distinction between a GM, Admin, and Player
Closed
#306 Create a an interface for game management
Closed
#107 Create a user manager interface
12 Issues created by 1 user
Opened
#311 The player landing page should only show the games that they're in
Opened
#312 The GM landing page should show all the players and all the games they're GMing
Opened
#320 Configure the server URL in the client application
Opened
#321 Create a Nix build and install deployment for the client
Opened
#322 Players can take "takeable" cards from the table
Opened
#323 The GM can put a picture on an index card
Opened
#324 The GM can put a countdown clock on an index card
Opened
#332 Roll style elements into the visions code
Opened
#333 The GM can give a card directly to a player without notifying the other players
Opened
#334 Correctly handle all calls to unwrap and expect through the code
Opened
#335 Create a template card box and a real card box
Opened
#336 Create a tabletop
19 Unresolved Conversations
Open
#158
The GM can create a card with written text and place it on the table
Open
#159
Players can see the cards within a few seconds of the GM revealing them.
Open
#267
Create a Numenera Character sheet structure
Open
#269
Create a renderer plugin for the Numenera character sheet
Open
#104
Create a SQLite database to store all application data
Open
#105
Set up automatic database migrations
Open
#108
Bootstap the initial admin user
Open
#109
Allow users to set their passwords
Open
#156
The admin can create users
Open
#157
The admin can designate GM and player users
Open
#261
Create an auto-test suite for the application core
Open
#262
Create an auto-test suite for the Visions API
Open
#263
Create an auto-test suite for the visions API client
Open
#264
Create an auto-test suite for components and views in Visions
Open
#265
Add code coverage reports to the test suite
Open
#282
Usernames in the database must be unique
Open
#300
A user must change their password on first login
Open
#301
Create a user settings page
Open
#302
Send an email to a new user when the user gets created