The Shoot-’Em-Up Construction Kit, usually SEUCK, exposed the parts of a shooting game that its makers normally kept to themselves. You could draw the player, animate enemies, build the landscape, arrange attacks and save a finished game. The engine was supplied; the game’s appearance, pacing and encounters became the owner’s work.
Sensible Software made the original Commodore 64 kit in 1987, with Chris Yates programming it. It was published under Outlaw Productions, Palace Software’s label. A contemporary ZZAP!64 guide by Jon Hare shows it already in use by the end of that year. (Original guide, pp.54–55; Lemon64 credits, secondary.)
A sprite is not yet an enemy
The kit separated pictures from the things that used them. A sprite editor made individual images. An object editor assembled images into animated objects, setting their colours and animation behaviour. One object could therefore change pose as it moved, rather than being tied to a single drawing.
Backgrounds had a similar hierarchy: characters formed blocks, and blocks formed a map. The tile-map approach saved memory by reusing small pieces of scenery. Sound effects, player limitations, attack waves and level settings had their own menus. The menu reference preserves that division and its keyboard shortcuts.
Hare’s guide recommends learning the editors through one of the four supplied games. Change a player image, test it, then find why the animation behaves differently when the object turns. That process reveals the relationship between the pictures and the object’s movement without requiring a new engine first.
Design within the frame
The original C64 framework supports stationary screens and vertical scrolling. It is not an unrestricted language for describing any game. Enemy paths, shooting, lives, collisions and scrolling have to be arranged through the behaviours the kit offers. The related 3D Construction Kit solves a different problem; AMOS gives the programmer a language and a wider set of decisions.
Those limits still leave design work. Hare’s guide discusses planning contrasting sprite colours, choosing a consistent direction for light and shadow, and making the background support the action. Two of the multicolour sprite colours are shared across the game, so an attractive sprite cannot be designed in isolation from every other one. A tool that removes machine-code programming does not remove the machine’s colour rules.
A game that could leave the editor
SEUCK’s storage menu distinguishes saving editable data from saving a finished game. The latter makes a stand-alone program that someone can play without using the construction interface. That distinction let creators share a game rather than only exchange an editor project.
Later creators extended the framework with additional code. Jon Wells’s 2006 enhancement notes describe adding features after saving a stand-alone version. Such work belongs to SEUCK’s continuing use, not to the capabilities of the unmodified 1987 package. (Wells’s notes in the public compilation.)
Sources
- Jonathan Hare, “The Sensible Guide to Construction”, ZZAP!64 33, Christmas Special 1987, pp.54–55: original author’s tutorial, sample games, animation and shared colours. Original issue scan; the host file’s “Jan” label is not used to date the program.
- SEUCK Vault, C64 menu reference: community transcription of editor and storage choices (web, secondary).
- Lemon64, Shoot-’Em-Up Construction Kit: credits, publisher relationships and 1987 release (web, secondary database).
- Jon Wells, 2006, “C64 SEUCK Unused Memory Map for Enhancements”: participant technical notes, reproduced in a later compilation. These describe modification of a saved game, not standard features of the original editor.