By Lenard Gunda
Bradford Mansion is a largish puzzle oriented parser mystery that is possible to solve without understanding anything of the mystery. When I finished it (after 2 hours, 10 minutes and 24 seconds according to the end message) there were still four locked things, and 12 more points to achieve (out of 74). Perhaps a lot is hidden behind these points, perhaps not; without them, at least, the story was quite thin, with the biggest mystery being the behaviour of the butler. Throughout the mansion there are, however, a large amount of symbolic paintings, hinting at a strange and deep mystery that reasonably should stretch far beyond my 12 missing points. I am curious as to what I have missed, but perhaps not sufficiently to play it over again.
I don’t always mind a thin story if the puzzles are good, and for the most part, they were good enough, although not very original. Both interestingly and frustratingly, however, Bradford Mansion is written with a seemingly custom engine, running directly in the console. One one hand, this gave it somewhat of a classic parser feeling, though on the other hand, everything goes much slower without the shortcuts and assistance that modern engines provide. You can’t use pronouns, you often have to write the full name of a thing, the up arrow doesn’t bring up the last command and there was no abbreviation for ‘look’.
During my playthrough I ended up consulting the walkthrough twice. While the last one was the matter of me overlooking a fairly obvious clue, the first was the result of a very strict parser to the point where I never could have guessed the correct syntax. In fact, the parser is generally quite unforgiving here, with many reasonable synonyms not being accepted. For anyone else that would like to play Bradford Mansion – and it’s still quite likeable, despite its limitations – I’m fairly certain that you don’t need to ‘search’, nor to ‘look under/inside/etc’, something that would have reduced my amount of moves significantly had I known it.
Please note that the transcript is captured directly from my terminal output, and therefore contains all of my key presses, including backspaces and typo corrections. Some commands may look a bit strange, and if so, they were probably not entered as such.
transcript.txt (121.1 KB)