← all posts site ↗

vdot511 tip system and endgame

vdot511 is getting rebuilt from scratch, the old folder of code and assets ignored. the loop: first person view where the head moves with clamp ranges, and you can step into a laptop screen view. on the laptop there is a status bar with apps, opened by clicking, each with minimize and maximize in its window. a social media feed sorted newest first, with one of the early posts about the killer himself. a map with a modal of cctv camera views, carrying two buttons: scan and submit a tip.

scanning runs an analyzer app that screenshots the camera view, reads it, and logs every car in frame, camera number, location, color, headlights on or off, all the descriptors. the critique from the other day was that clicking around a map lacks agency, and this mechanic set answers it. the tip is the agency.

the ending never changes, he always arrives. but the tip grades you and paces the endgame. submit and a news post lands: police seeking a red sedan, right mirror intact, headlights on. the world echoes your deduction in the city's own voice. if your tip was wrong, the news describes a car that does not exist, and a careful player can catch that, watching cops hunt a car they know is wrong. no ui ever tells you that you were wrong. submitting also compresses the killer's remaining path and starts the finale: cams near you die one by one, your lot's dead camera flickers alive, the car appears in it, then headlights in your mirror, a knock, cut to black.

the end card is a case file comparing your submitted descriptors against the truth, check and cross marks per attribute, no score number. the false post that fooled you shows up as a cross, which is the replay fuel. never submit and the path still completes, he arrives anyway, empty end card. the ending is a beat, not a mechanic, and that note from the other day holds.