NAME

xomb - a game featuring @ versus the Xarci Bedo

SYNOPSIS

xomb --delay=f --err=file --seed=i --version

DESCRIPTION

xomb is a computer fantasy game. The object of the game is to survive the attacks of the Xarci Bedo and obtain a lot of gems. To win the game you must locate the Dragonstone and get it out.

A game should take under 15 minutes to complete.

Options

--delay=seconds

Floating point value to sleep after events the player may wish to take notice of. Probably should be much lower than 1.0. Default is 0.15 seconds.

--err=file

Send STDERR to this file if not already redirected.

--seed=i

Start the game with the seed set to the given integer value. The RNG algorithm will very likely change in future releases of the game.

--version

Shows the xomb version and quits the game.

An Overview of Minos III

The most recent message is shown at the top of the screen. More of these can be viewed using the M command. The status bar at the bottom

    Level 01 T10 SP[=========================-         ][ .][*] 121B

shows the level (1), the time or cost of the last energy-consuming move (10), shield points remaining, the item and ground tile of the current cell (here: no item and an empty cell), whether a gem is loaded for shield repair (yes), and finally the error code display (121B). Consult the "DIAGNOSTICS" section for details on the error codes.

The middle of the screen shows the level map. Various "Symbols" are present in this space. Note that the Field Operation View (FOV) readouts may be impacted by the harsh conditions on Minos III, and the scanner is an older model.

In examine mode (x) level map features are described, if they are in view of the FOV scanner. Range and coordinate details are also provided.

Commands

With numlock enabled a numeric keypad may be able to be used to navigate.

     y  k  u     Motion is traditional to rogue(6) as shown in the
      \ | /      compass to the left. Other commands, of which some
    h - @ - l    take time to complete, include:
      / | \             
     b  j  n                . - wait a turn      x - examine board
                          g , - pick up item     i - show inventory
    M - show messages     < > - activate gate    E - equip a gem
    p - clear PKC code    C-l - redraw screen    R - remove a gem
    ? - show help         v   - show version     d - drop a gem
    @ - show location     Q   - quit the game

    Esc or q will exit from sub-displays such as this one. Prompts
    must be answered with Y to carry out the action; N or n or Esc
    will reject the action.

Symbols

These may be inspected in-game using the examine command, assuming they were picked up by the FOV scanner. At most only one Xarci Bedo, item, and ground tile can occupy the same cell. Scientists believe this is due to particularities of the geology on Minos III, and some even speculate that there is a relationship between the gems and the Xarci Bedo.

@

Vessel location.

A crevasse in the ground that you can fall down.

%

A gate to the next level (via the > command). A gate takes some time to complete the level transition. Ascent is only possible with the Dragonstone using < on the gate. As is traditional.

#

Wall. Impassable. Generally blocks FOV, though again the FOV scanner is an older model, so there may be defects.

^

Rubble. Somewhat passable. Sometimes blocks FOV. Sometimes blocks enemy fire.

~

Acid pond. Probably an OSHA violation.

.

An empty cell.

*

A gemstone. These may be equipped from the inventory to provide shield repair over time, though this will greatly damage the gem due to harmonic stress caused by the shield module. The gem value is shown before the name in the inventory and some log messages.

The Xarci Bedo are represented by uppercase ASCII letters, and exhibit the usual fantasy tropes: Gatling Autocannon, Railgun, etc.

DIAGNOSTICS

Various messages may be shown by the Patrol Kombat Computer (PKC) in response to command inputs. Details on important codes are listed below. Consult the VP XII Operations Manual (Green) for complete scenario process control instructions. Due to memory limitations only the last error code is stored. The readout can be cleared with the p command.

PKC-0001

A move was attempted beyond the boundaries of the game. In strict mode this would normally result in the immediate termination of the contestant.

PKC-0002

The motion control guidance system has encountered a significant obstacle and signals that fact with this code.

PKC-0004

Gate activation error.

PKC-0010

Dragonstone is required for vertical ascent module gate activation.

PKC-0014

Gate is out of service, or was never enabled by the contractors.

PKC-007E

Environmental hazard proximity alarm.

PKC-0099

Gyroscopic alignment control array reports unexpected acceleration.

PKC-0101

Item retrieval command call failure.

PKC-0102

Inventory stack allocation failure.

PKC-0104

Item disposal process error. Clear item exit disposal slot before retry.

PKC-0111

Incompatible item use handler exception error.

PKC-0112

Underflow on inventory stack query request.

PKC-0113

Underflow on shield module feed slot retrieval call.

PKC-0302

Target acquisition lock failure. Often caused by excess vibration in the FOV scanner array.

PKC-1202

Executive overflow on guidance module.

PKC-1203

Spurious interrupt on data bus array.

PKC-121B

Unit is already in command mode.

PKC-1220

Background subspace communications link query negative acknowledgment.

EXIT STATUS

xomb exits with a 0 on victory, and >0 in every other case.

SEE ALSO

Game::Xomb, rogue(6)

VP XII Operations Manual (Green)

AUTHOR

Jeremy Mates

BUGS

xomb assumes that the terminal used supports various ANSI or XTerm Control Sequences. Given certain time constraints (7DRL 2020) not much portability testing has been done.