node watch
for initial compilation and to watch for changes
node serve
to start local server
node generate-declarations
to update declarations for localization strings
Game will start at http://127.0.0.1:3333/
Complete all tasks before deadline
- Each week consists of 5 work days and 2 weekends
- Each day is split into 24 hours
- Player actions advance time in 1-hour increments
- Work starts at 10:00 and ends at 18:00
- At all times, player has access to apps on their laptop
- Wrike
- Calendar
- Messenger
- IDE
- Browser
- Player can finish their day at any point and skip time until 10:00 the next day
- With each hour passing
health
decreased by 3 - After player ends their day, each hour skipped increased
health
by 4 - Player has a team of randomly generated coworkers with randomly generated skillset
health
- starts at 100, game over if it reaches 0company status
- starts at 100, game over if it reaches 0burnout
- starts at 0, game over if it reaches 100productivity
- starts at 100, decreases time it takes to completetasks
- Wrike
- Table View
- List of all
tasks
for this project, their statuses and assignees - This is where player can take on new
tasks
- List of all
- Inbox
- List of messages requiring player attention
Task
requires your review- Bug discovered on production
- Bugs have a completion deadline, after which they will decrease
company status
each hour
- Bugs have a completion deadline, after which they will decrease
Task
was returned to development from QA
- List of messages requiring player attention
- Table View
- Calendar
- Events which player can attend
- Skipping events decreases
company status
- Possible events
- Daily Standup - 1h, daily
- See Daily Standup section
- One on One - 1h, twice per week
- Increases teammate
skill level
- Increases teammate
- Candidate Inteview - 2h, once per week
- Lead Meeting - 1h, once per week
- Knowledge sharing, 1h, once per week
- Increases
productivity
- Increases
- Lunch - 1h, daily
- Increases
health
- Increases
- Daily Standup - 1h, daily
- Messenger
- Allows answering to your teammate messages
- Whenever a teammate is
stuck
with atask
, they will message player
- IDE
- Allows working on current assigned
task
in 1h increments- Work done per hour is increased based on
productivity
- Every hour worked randomly adds
bugs
to thetask
code
- Work done per hour is increased based on
- When a
task
is done, player can- Write instructions for QA
- Decreases time
task
is inIn Testing
status
- Decreases time
- Cover code with tests
- Eliminates some
bugs
- Eliminates some
- Pass it to review
- Reviews of player
tasks
take fixed time and always pass
- Reviews of player
- Write instructions for QA
- Working after work hours increases
burnout
- Allows working on current assigned
- Browser
- Spend time on Jabr. Increases
productivity
- Spend time on YouCube. Decreases
burnout
- Spend time on Jabr. Increases
- Estimated time
- Work done
- Array of required
skills
- Status
- New
- In Development
- In Review
- In Testing
- Done
- Dart
- TypeScript
- JavaScript
- Java
- SQL
- CSS
- Each teammate has a random skill level based on game difficulty
- Teammates have different random
skills
- Work
- Each hour of work day teammates work on tasks assigned to them
- Based on skill level, teammate can become
stuck
for a random amount of hours- When that happens, they message player in Messenger, asking for help
- Player can spend 1h to remove the
stuck
status - Otherwise the status is removed once the required number of hours pass
- Each teammate reports on the status of their currently assigned
task
- Continue working on
task
if it isn't done - Report being
stuck
on thetask
- Report that
task
is completed- Player can select which
task
a teammate can take from top backlogtasks
- After selecting a
task
it's transferred toIn Development
and assigned to that teammate - For each skill required in
task
but not possessed by teammate, thattask
's estimated time increases
- Player can select which
- Continue working on
- If player skips the meeting, teammates take
tasks
randomly