Skip to content

Arcade › Tech Support First Call

Tech Support First Call

  • 3d
  • first-person
  • tech-support
  • investigation
  • office
  • choice-driven
0
Remix it Discord

1 play

How to play

Click the game above and it runs right here in your browser. No download, no installer, no account needed. ushariff818 built it with Cinevva, so it works on a phone or a tablet too.

Discussion

Nobody has said anything about Tech Support First Call yet. Play it, then tell ushariff818 what you would add next.

Make your own game

Tech Support First Call was built by ushariff818 with the Cinevva game creator: describe the game you want in chat, watch it get built, and play it in your browser minutes later.

Remix Tech Support First Call opens the real game in the creator and forks its actual files, chat and design doc, so you start from the code rather than from a description.

Read the build brief for Tech Support First Call

Cinevva's analyzer read this game's design doc and its source, then wrote the brief below. "Make your own" hands it to the game creator as your opening message, so you start from a real spec rather than a one-line idea.

Create a first-person 3D tech-support investigation game titled “TECH SUPPORT: FIRST CALL.” The player is a support technician in a bright, stylized modern office and must resolve a customer’s laptop with a black screen. Use an FPS camera with mouse look, WASD movement, Shift to run, jumping, and E to interact; show a small pale-blue plus crosshair at screen center. The office has a light blue atmospheric background/fog, a neutral floor with a blue-gray rug, a large back window showing a simple blue sky and blocky skyline, warm wood trim, ceiling light panels, a wood bookshelf with colorful books on the left, a whiteboard with simple blue diagram marks on the right, and a leafy plant. At the center/back is a wood customer desk with dark legs, drawer unit, two glowing dark monitors, a pale mug, and a prominent open silver/gray laptop. Put a seated blocky customer character behind/in front of the desk, facing away from the player. Use soft shadows, cool blue lighting, warm wood accents, rounded simple low-poly forms, and a clean polished game-like presentation.

Implement the gameplay as a linear case workflow represented by state and UI. Start with objective “Find the customer” and bottom hint “Walk to the customer and press E.” Pressing E opens a customer dialogue (the interaction can be triggered by the key as in the reference implementation). The customer says: “My laptop turns on, but the screen is completely black.” Present a grid of selectable questions, including useful questions such as whether the power light comes on, whether the fan can be heard, whether there is a faint glow, whether it was knocked recently, whether it made a sound, and whether the charger is plugged in. Each useful choice adds the corresponding customer note to the Case Notes panel; asking irrelevant questions such as what color the desk is or asking about turning it off costs 2 score and increments a Mistakes count. Begin with score 100. After four notes, close the dialogue, change the objective to “Inspect the broken laptop,” and change the hint to “Walk to the laptop and press E.”

In the upper-left, show a translucent dark rounded panel with the uppercase blue eyebrow “CURRENT OBJECTIVE” and the current objective text. In the upper-right, show a translucent dark rounded “Case Notes” panel with sections “CUSTOMER NOTES” and “EVIDENCE”; initially both say “No notes yet.” / “No evidence yet.” and collected entries appear as green checkmarked rows. Include a top status label reading “WASD move · Shift run · Mouse look · E interact · Tab notes.” Tab toggles the notes panel. Use a translucent rounded dialogue panel at the bottom center with a CUSTOMER label and selectable blue buttons arranged in two columns (one column on narrow screens).

In the diagnosis phase, E opens “Diagnostic station: choose a test.” Provide buttons for Check power LED, Listen to fan, Check charging LED, Test external display, Flashlight test, Try brightness keys, Hard reset, Replace RAM, and Choose root cause. The first tests add evidence such as “Power LED solid — power OK,” “Fan spinning,” “Charging LED — charging OK,” “External display works — GPU and motherboard OK,” “Faint image appears — backlight or cable,” “Brightness keys have no effect,” and “Hard reset made no change.” Choosing Replace RAM is a wrong turn: subtract 8 score, add one mistake, and add “Wrong turn: RAM replacement unnecessary.” Choosing root cause opens a choice among Display cable disconnected, Dead motherboard, Failed battery, and Corrupted operating system. The correct choice adds “Root cause selected: display cable disconnected,” closes the dialogue, changes the objective to “Repair: power off and unplug,” and shows “Press E near the laptop.” Wrong root causes subtract 6 score and increment mistakes, then display feedback that the machine powers on and external display works and let the player review evidence.

In the repair phase, E opens a safe ordered repair sequence. Present one action at a time: “Power off and unplug,” “Remove back cover + battery,” “Discharge residual power,” “Locate loose display cable,” “Reseat display cable,” “Reassemble + reconnect power,” and “Power on” (the final dialogue can say it is ready to verify the repair). Each correct action increments the repair step and adds evidence beginning with “Repair: ”; update the objective to the next repair action. Also offer “Do something out of order,” which subtracts 3 score and increments mistakes, then shows a safety hint telling the player to follow the safe order before touching the cable. On all seven completed steps, mark the case complete, set objective to “Case complete,” hint to “Case resolved,” make the laptop screen glow bright blue to indicate restoration, and show a centered dark report card. The report should say “TECH SUPPORT: FIRST CALL,” “Case Resolved,” and “DISPLAY RESTORED,” then list “Root Cause: Display Cable Disconnected,” “Resolution: Display Cable Reseated,” plus pills for repair steps performed, mistakes, final score (never below 0), and XP equal to at least 10 or score + 25. Include the explanatory text that the faint glow, working fan, and successful external display test pointed away from the panel and toward the display cable. Add light confirmation/error tones for choices if audio is available.

More free browser games

Browse the whole Arcade →