Week 5 #

Play our Demo #

Also avaliable with multiplayer capabilities for Windows, Linux, and MacOS on Itch.io.

Or you can play the single player version here:

Feedback #

Sessions #

First session: #

• A visual cue is needed to show which room they can be sent to.
• The controls feel awkward: scrolling the map with the mouse-wheel is great, but both selecting and sending employees are on the left-click. It would be clearer if sending were done with the right mouse button to avoid mis-click errors.
• If player clicks outside the panel, the anomaly-work menu stays open. With the employee list already open, clicking the anomaly again stacks the job list on top of it.
• The employee list should appear under the chosen job, and the job list itself should stay open after you pick one.
• Holding a modifier key (e.g., Shift) should let player left-click-drag to select several employees at once; the whole group then moves to the target room together. When working with an anomaly, every selected employee can be shown at the top of the list.

Second session: #

• Fix cursor display bug, during which the cursor is shown twice and in the wrong place.
• Ability to select multiple agents using drag select.
• Ability to close all menus with X button.
• Nicknames should be shown under cursors.
• Visual cue is needed to show selected room?

Third session: #

• Most of the feedback were overlapping with previous sessions.
• Highlighted bugs related to battle system.
• Ability to restart the day would be nice.

Analyze #

All sessions underlined a lack of polishing, which is expected because we were prioritizing the core mechanics first. We have prioritized and created GitHub issues for a majority of stated issues

Iteration & Refinement #

Implemented features based on feedback #

• Agent and room highlighting
• Adjusted controls
• UI fixes

Performance & Stability #

Our project is very lightweight with insignificant load times and low frame time, so performance is not our issue.

Documentation #

Our project documentation consists of the terminology, and occasional inline comments. Game projects may need documentation for modding implementation, but we don’t have plans for that. Gameplay documentation (wikis) is traditionally a community’s job.

Weekly commitments #

Individual contribution of each participant #

Plan for Next Week #

Confirmation of the code’s operability #

We confirm that the code in the main branch:

• In working condition.
• Run via docker-compose (or another alternative described in the README.md).