|
44 |
✓resolved |
Add route specs |
Mercury-Atlas 11 |
Christopher Peplin |
almost 15 years old |
|
37 |
✓resolved |
Write database migrations for economic components |
Mercury-Atlas 8 |
Christopher Peplin |
almost 15 years old |
|
36 |
✓resolved |
Write database migrations for map components |
Mercury-Atlas 8 |
Christopher Peplin |
almost 15 years old |
|
35 |
✓resolved |
Write database migrations for technical components |
Mercury-Atlas 8 |
Christopher Peplin |
almost 15 years old |
|
26 |
✓resolved |
Choose map generation algorithm |
Mercury-Atlas 8 |
Christopher Peplin |
almost 15 years old |
|
30 |
✓resolved |
Design workflow and data models for growing the region |
Mercury-Atlas 7 |
Christopher Peplin |
almost 15 years old |
|
29 |
✓resolved |
Design contract parameters and data model |
Mercury-Atlas 7 |
Christopher Peplin |
almost 15 years old |
|
24 |
✓resolved |
Decide on best database backend |
Mercury-Atlas 8 |
Christopher Peplin |
almost 15 years old |
|
23 |
✓resolved |
Design workflow for inviting user to a private/public multiplayer game |
Mercury-Atlas 7 |
Christopher Peplin |
almost 15 years old |
|
22 |
✓resolved |
Design workflow for creating a public game |
Mercury-Atlas 7 |
Christopher Peplin |
almost 15 years old |
|
28 |
✓resolved |
Revisit real-time behavior |
Mercury-Atlas 6 |
Christopher Peplin |
almost 15 years old |
|
27 |
✓resolved |
Decide if a background daemon is required |
Mercury-Atlas 6 |
Christopher Peplin |
almost 15 years old |
|
25 |
✓resolved |
Diagram data model |
Mercury-Atlas 6 |
Christopher Peplin |
almost 15 years old |
|
21 |
✓resolved |
Design relationship between user and a map region |
Mercury-Atlas 7 |
Christopher Peplin |
almost 15 years old |
|
20 |
✓resolved |
Design relationship between user account and a game |
Mercury-Atlas 7 |
Christopher Peplin |
almost 15 years old |
|
19 |
✓resolved |
Design parameters for a multiplayer's region |
Mercury-Atlas 6 |
Christopher Peplin |
almost 15 years old |
|
18 |
✓resolved |
Decide object for a player in a multiplayer game |
Mercury-Atlas 6 |
Christopher Peplin |
almost 15 years old |
|
16 |
✓resolved |
Design map zone parameters |
Mercury-Atlas 6 |
Christopher Peplin |
almost 15 years old |
|
15 |
✓resolved |
Decide on map objects |
Mercury-Atlas 6 |
Christopher Peplin |
almost 15 years old |
|
17 |
✓resolved |
Design map node parameters |
Mercury-Atlas 6 |
Christopher Peplin |
almost 15 years old |
|
13 |
✓resolved |
Decide on storage types |
Mercury-Atlas 6 |
Christopher Peplin |
almost 15 years old |
|
11 |
✓resolved |
Decide on line types |
Mercury-Atlas 6 |
Christopher Peplin |
almost 15 years old |
|
9 |
✓resolved |
Decide on generator types |
Mercury-Atlas 6 |
Christopher Peplin |
almost 15 years old |
|
14 |
✓resolved |
Design storage parameters |
Mercury-Atlas 6 |
Christopher Peplin |
almost 15 years old |
|
12 |
✓resolved |
Design line parameters |
Mercury-Atlas 6 |
Christopher Peplin |
almost 15 years old |
|
10 |
✓resolved |
Design generator parameters |
Mercury-Atlas 6 |
Christopher Peplin |
almost 15 years old |
|
8 |
✓resolved |
Design single player scoring incentives |
Mercury-Redstone 4 |
Christopher Peplin |
almost 15 years old |
|
7 |
✓resolved |
Design multiplayer scoring incentives |
Mercury-Redstone 4 |
Christopher Peplin |
almost 15 years old |
|
6 |
✓resolved |
Design multiplayer, shared ranking algorithm |
Mercury-Redstone 4 |
Christopher Peplin |
almost 15 years old |
|
5 |
✓resolved |
Design single player game ranking |
Mercury-Redstone 4 |
Christopher Peplin |
almost 15 years old |
Create new ticket