- Action
- Indie
- Early Access
Game
The Technician
Technician Ted was an early platformer.
The Technician is a VR action puzzle game about hacking your way through security systems. Usually while being shot at.
About The Technician
- Released
- December 2018
- Platforms
- PC (Microsoft Windows)
Where to get it
Release, studio and platform data from IGDB. Store links go to the sellers, not to us. We do not sell games and we do not host files.
Browse everything
Sorted, filterable and paged. Every link goes to the author’s own download.
From the developers
Official announcements, newest first. Posted on Steam.
- Community Announcements0.3.3Small hotfix to correctly enable the "Options" action for configuring chips when in puzzle edit mode.
- Community Announcements0.3.2First update in a long time! Still need to ramp back up into working on this semi-regularly again, so this one is bit small: Patch Notes:Started migration to SteamVR's newer input systemSome minor bug fixes for game startup/init issuesPartial index controller support - will function pretty similar to Oculus Touch controls (no finger tracking yet)Made the final stage explosive device available i...
- Community Announcementsv0.3.1Patch Notes Hotfix for bug causing the game to not launch correctly for some new users.
- Community Announcements0.3.0Update 0.3.0 is live! I decided it would be better to let people start playing around with creating content and sharing it sooner rather than later, so this update has enabled Steam Workshop support for everybody. The editor and workshop are both pretty rough still, so there's very little in the way of validation or error checking for user generated content. I expect this will lead to people br...
- Community AnnouncementsDGC @ PCConnects SeattleThe Technician will be at PCConnects Seattle on May 13th and 14th; if you’re at the show then feel free to come say hi! I’ll presumably be in a booth somewhere, but beyond that you know about as much as I do.
- Community Announcements0.2.7As I mentioned in a previous post, this month's update is fairly light since I'm tangled up in a bunch of other life activity at the moment. However, I did manage to put together a couple of things to push out: Fixed a bug with Elevator Lock handles flipping out in some specific circumstances. New component, the potentiometer: a dial that can be adjusted to modify incoming data values from 0% t...
- Mods indexed
- 6
- Versions
- 0
- Newest tracked
- none yet
- Most disruptive update
- No breakage data for this game
of 14 on Steam Workshop
Most downloaded
Measured from the source's own counts, summed across every release.
- easy board103 downloads
- Calculate, Program, UnlockTechnically "solvable," but really just for fun.79 downloads
- MarxBuild up to each advance. Don't lose your cool!15 downloads
- easy now12 downloads
- New Board by backstaiaHi Technician, here we have a special situation. There is an fully encrypted ALU on the board but dont despair our trusty friend Z3R0 has dumbed the exploit cmds of the board to the dark web. You first need to identify the initial bit of the board using the NL on board 1. Have your guys from the...12 downloads
- JacobDon't lose the spark, or you'll have to start from the bottom... There is no need to use the Rewriter or the Fuzzer. There are multiple solutions to some puzzles. If this puzzle seems too easy, try the difficulty boost! Hit both switches in Panel 01! L11 downloads
More early access games see all
Why The Technician mods break
A mod is compiled against one version of a game. When the game updates, anything that reached into the parts that moved stops working, and it usually stops working silently rather than with a message that explains itself.
That is what the table above counts. It is not a guess: each row is a mod the community has reported as broken by that specific release. The number is a fair measure of how disruptive an update was, and it is the reason people delay updating a game they have modded heavily.
Common questions
Does IndexGG host The Technician mods?
No, and it never will. Every download link points at the author's own page on Nexus, GitHub, CurseForge or wherever they published it. We index the ecosystem; the files stay with the people who made them.
Where does the compatibility data come from?
From the communities that maintain it in the open, not from guesswork. Each claim carries how it is known, so a reported breakage is never presented as though the author said it.
Why is a mod listed as broken when it works for me?
Compatibility depends on your exact game version and the rest of your load order. A mod marked as broken in one release may work fine on an older one, which is exactly why the version is recorded next to the claim rather than a bare yes or no.