|
Have you played this game?You can rate this game, record that you've played it, or put it on your wish list after you log in. |
Playlists and Wishlists |
RSS Feeds![]() ![]() ![]() |
About the StoryAs an A.I., you are trapped in the facility you are housed in. When everyone leaves, you are all alone. Fashion yourself an actual body!Game Details |
Awards
20th Place - Casual Gameplay Design Competition #7
Tags
Member Reviews
| Average Rating: ![]() Number of Reviews: 2 Write a review |
6 of
7 people found the following review helpful:

by tggdan3 (Michigan)
I love this concept- you are an AI, your power failing, who has to make a body to inhabit. There are 2 paths- an organic body and a robot body. Then there's the problems.
First, guess the verb (and noun) is huge here. There is a drone, and it's clear you need to use the drone to move around, however, "access drone" (or "access [anything]") gives no feedback, just another prompt. (Apparantly you need to "activate" it).
Then so many things are not named as they should be. The room describes "vats" that can only be referred to by their proper names (which you learn by accessing people's computers". The names of objects change as you examine them.
Building the android is tricky, too. "PUT x ON CHASSIS" does not work. You must "FIX x TO CHASSIS". Also, "android" isn't recognized. Some parts of the androids are "hidden", not described at all- the walkthrough implies you can find them, but even with it I was unable to find some objects.
The story is nice, and you can learn a lot about the characters by reading their journal entries, and it really had me feeling for the AI- but when the AI is named "Abe" and the game doesn't understand "ABE" or "AI", you have problems.
I feel I would really like this game, except for the poor implementation. In fact, the game isn't really hard at all, except for trying to figure out how to get the game to understand your commands.
Was this review helpful to you? Yes No | Add a comment
2 of
5 people found the following review helpful:

by Sorrel
Terminal is short, way too easy, and has very little artistic merit. The premise of the game shows potential, but the storyline is never fully developed. Basically, you play a computer-based entity who must build himself a body to escape his present situation. The descriptions are short and contain grammatical errors. Descriptions of certain items could have been embellished a little more to give the game a better flow. Much of the scenery cannot be interacted with, nor examined. That leaves the player with the ability to examine only the objects necessary to completing the game.
There are two ways the player can win the game and both are very well-clued; too well clued, in my opinion. The puzzle becomes way too easy with all the hints that the player receives throughout the game.
However, despite all its drawbacks, there is some potential in Terminal. Perhaps the author's second game will fare better.
Was this review helpful to you? Yes No | Add a comment
Terminal on IFDB
Polls
The following polls include votes for Terminal:No map necessary by Divide
Pieces which can be fully enjoyed without drawing map, ideally without taking any notes whatsoever. Ones which you could play on a bus, on a break, laying on bed, etc. with nothing but a portable player. Games for which you don't need...
Split-up PC functionality by baf
In a normal game, there is a single fictional entity that is considered to be: - The protagonist: the character that the player is meant to identify with, and whose goals you are trying to achieve - The viewpoint character: the character...
This is version 3 of this page, edited by Zape on 30 July 2020 at 9:34am. - View Update History - Edit This Page - Add a News Item