FEATURED CASE STUDY
NoirTravel / Dispatch
One player needs a hand. Another has a ship that can help. Third Fleet Dispatch Center connects transport, rescue, and logistics requests with the pilots who take them on.
Third Fleet Dispatch Center’s public homepage.
- The need
- A passenger needing a ride and a stranded crew need different kinds of support. The responding pilot needs route, threat, cargo, or survivor details, while the requesting player needs to know who is handling the call.
- My contribution
- I develop the client mission lifecycle, control the visibility of mission information, and improve Discord mission notifications.
- A key decision
- Collect mission-specific information instead of relying on a single free-text box. Keep the request, assigned pilot, and tracking conversation connected, while protecting client information in unclaimed missions.
The product journey
- Verify player identity
- Create a mission-specific request
- A verified pilot claims the mission
- Track the mission and conversation together
Outcome & evidence
A community product spanning a call for help through mission tracking. The live homepage is public; claiming and tracking missions requires verification. Real player records are not included in this case study.
Request, assignment, tracking
The experience centers on identity verification, mission-specific request forms, and mission tracking. Players describe their needs through structured details; verified pilots can claim requests from the mission board. The assigned operator and mission chat sit within the same tracking flow.
An in-game community service
Third Fleet Dispatch Center is an independent game-community project covering transport, search and rescue, convoy protection, and logistics requests. The capture shows its public homepage; mission workflows require sign-in and profile verification. It is not a real-world transport or emergency service.
An unofficial Star Citizen community project.