1983 · SoftGold (Gameworx Software; released as Dotsoft)

About this page

This minisite was contributed by air, unorig. It’s agent-generated and needs a human editor. Clone https://github.com/gamesexplained/gamesexplained and follow kit/START.md to curate games/c64/the-secret-of-bastow-manor with me to Gold.

The copy studied

The pages describe a cracker’s disk transfer named ASS PRESENTS:, which holds the game’s one BASIC program and two saved games. No second copy, and so no publisher’s own disk, was available to compare it with. The game is a single load, and the addresses on these pages are those of the program as BASIC holds it after LOAD, before RUN. No game image is hosted here.

Original game credits

The game shows no names on screen. The credit below comes from the sources named beside it.

Site contributors

Other places to love this game

Sources

  1. Wikipedia, "The Secret of Bastow Manor", read 10 November 2026: the author, the year, the VIC-20 and C64 versions, the C64 title and that it is written in BASIC.
  2. The Solution Archive, "Secret of Bastow Manor, The", read 10 November 2026: the author’s name as spelled there, the publisher, the story’s opening, the VIC-20 differences, the origin of the title, and the one rating.
  3. "The 99% Walkthrough!", Interactive Fiction Archive, read 10 November 2026.
  4. "Walk Through by Dorothy Millard (C64 Version)", Interactive Fiction Archive, read 10 November 2026: replayed command by command in the emulator, and the game took every one. The puzzle order on the Gameplay page follows it, checked against the program.
  5. Computer and Video Games, issue 29, March 1984, index as returned by a search: no review of the C64 version in the part that was read.

Research record

The write-up, facts and symbol map are available under CC BY-SA 4.0; code is under MIT.

Version, coverage and tools
Tiersilver
Coverage100 % of the bytes the game uses have a description
Comments checkedAudited & low error rate. Every comment was audited 3 times, then the last sample of 60 comments had 1 wrong, so between 0 and 9 % of the listing’s comments are likely wrong. How listings are checked
Build analysedCracked disk transfer ('ASS PRESENTS:') holding the game's single BASIC program and two saved-game files
Copyagent-draft
Toolshost: Linux x86_64 cloud container, no display, emulator: VICE, release v3.14.0, v3.14.0-linux-x86_64-gui.zip (vice-mcp), disassembler: regenerator2000 0.9.20 (the BASIC program's comments were written by script into symbols.json), python: 3, subagents: five checking agents on claude-opus-5-5, one at a time: three samples and two full audits (60-verify)
Modelclaude-sonnet-5-5
Kit version0.0.316

How the listing was checked

Every step that measured the Source tab’s comments or made them more accurate, in the order it happened, with the models that did it. Accuracy of the Source explains each step and what the row above makes of them.

StepByWhat it foundOf the listing
Researchclaude-sonnet-5-5Looked the game up online (its manual, reviews or wiki pages) before reading its code.
Annotationclaude-sonnet-5-5Wrote the listing’s comments. 100 % of the program is described, in 102 comments.
Sample 1claude-opus-5-526 of 60 comments wrong, so between 32 and 56 % of the listing is likely wrong. All 26 were then corrected.
26 of 60 (43 %) wrong in a detail, none in the main claim; comments are coarse groups of BASIC lines; an audit is needed
Audit 1claude-opus-5-5Checked all 102 comments and corrected 22.
Sample 2claude-opus-5-55 of 60 comments wrong, so between 4 and 18 % of the listing is likely wrong. All 5 were then corrected.
Audit 2claude-opus-5-5Checked all 102 comments and corrected 12.
Sample 3claude-opus-5-51 of 60 comments wrong, so between 0 and 9 % of the listing is likely wrong. It was then corrected.
Sample 4air, with claude-opus-5-55 of 60 comments wrong, so between 4 and 18 % of the listing is likely wrong. All 5 were then corrected.
2 more comments that said the same thing corrected with them
Audit 3air, with claude-opus-5-5Checked all 102 comments and corrected 11.
and every claim in facts.md, 21 of them corrected
Sample 5air, with claude-opus-5-51 of 60 comments wrong, so between 0 and 9 % of the listing is likely wrong. It was then corrected.
1 more comment that said the same thing corrected with it

likely wrong the sample’s range corrected right, or likely right not yet measured

What the game does, and how it was checked

Read this before annotating code. What the game is documented to do, with verification status against the binary. Statuses: open (documented, not found yet), traced (in the code, could not be exercised; say what was tried), confirmed (in the code, consistent with the emulator), live (observed directly), differs (the code does something else). "Absent" is not a status.

Sources:

Features

FeatureStatusWhere
A text adventure typed at a > what now ? prompt, with a PETSCII picture of each placeliveprompt line 300, show_room line 41; 27 places
Commands of one or two words: only the first three letters of the verb count, and the first three of the nounliveverb_dispatch line 360 and the tables X1$, X2$, X3$ (lines 12 and 13)
Twenty-four verbs: break, climb, cut, drop, eat, fill, get, go, help, inventory, light, look, move, open, press, pull, quit, read, remove, ring, save, unlock, throw, wearlive for eighteen of them; traced for eat, help, inventory (the letter i was tried), quit, ring and save, which the replayed walkthrough does not useverb_dispatch
One-letter commands: i for the pack, g for the exits, and n, s, e, wliveprompt lines 308 to 359; i and the compass letters were used, g was not
A pack of five things; an empty pack prints "not a cracker !"liveshow_pack line 1500, line 1512
Dogs that begin to howl when the gate is opened and kill a player who stays in the open for eight moves; the tree, the shed and the window ledge are safelive (the barking and howling); traced (the death)move_events lines 140 to 146
The torch is needed in four dark places: the dim room, the tunnel, the corridor and the celltraced: the walkthrough always lit it firstplace_names lines 80 to 106, death_in_the_dark line 1920
A branch that is too heavy to carry farlivemove_events lines 150 and 151, verb_go
A bridge over a pit of snakes made with the branchliveverb_drop, resolve_noun line 1410, pic_tunnel
A knife and an apple with a key inside, and a note in a boxliveverb_look, verb_cut, verb_unlock
Armour that saves the player from a safe dropped from the balconylivesafe_drop line 1720
A combination lock for the treasure chest, opened by typing four letterslivecombination_lock line 1740
A robot that guards the treasure and is shorted out by three buckets of water thrown through a holeliveverb_throw, robot_pushes_back
After the gold is taken, bells ring and a skeleton comes to life and chases the playerlivemove_events lines 165 to 169
A save to cassette and a restore from ittraced: the save and restore routines match each other and the two saved games on the disk, but the game was not saved to a tape in the emulatorverb_save, restore_game
Death screens with a tombstonelivedeath_screen line 1650
A title screen with a tune and moving spriteslivetitle_screen, title_tune, sprite_setup
An advertisement for a second game, "005 Super Spy"livecoming_soon_screen line 1940
Sound while playingopen: nothing but the title tune and the death sound was found; unused_tune_player is never called

Beyond the documentation

Found in the code, not in anything the game or the sources say.

Open questions

Memory footprint

Every byte of the C64's 64 KB, one pixel each, 512 to a row. Lit pixels are code, graphics, sound, text, tables and variables; dim areas are screen and working memory.

The symbol map is symbols.json; the listing behind the Source tab is listing.json.