ggeorgovassilis/superstartrek

The 70s Super Star Trek command line game revived as an HTML 5 app

superstartrek's Issues

Klingon damage model

Klingon raiders should also implement a damage model:

• impulse drive should sustain damage and immobilise raiders
• disruptors should sustain damage and become inoperational
• if a raider is not destroyed before Enterprise leaves the sector, then the raider is repaired

show score when game over

Energy budget for starship

The core reactor's energy output reactor should dictate "rounds" instead of a fixed amount of moves. The way to do it:

1. Define energy output (energy/time) for ship reactor. That is the round's budget.
2. Every action consumes energy by reducing the available budget.
3. Only actions are possible which consume less than the remaining budget

Some implications are:

• It's possible to perform multiple actions in the same round (i.e. fire phasers twice, fire phasers and move, all of that + torpedos)
• Shields consume budget, hence keeping shields high reduces firepower and maneuverability

center update prompt vertically

Observe reactor limits when docking

It shouldn't be possible to dock with a star base while enemies are present and docking manoeuvrers would overtax the reactor.

Losing the game

1. Losing the game should trigger a technical, semantic event
2. It should not be possible to play the game anymore after it was lost. Only the option to restart it should be available

Overhaul UI

Work out a new responsive UI

Crew combat

Crew should be another scalar property which suffers damage from enemy fire. Low values impede the ship's operations. Crew can be replenished at star bases. When shields are low (eg. < 10%), Klingons should beam over from nearby raiders, killing crew.

Raiders should suffer penalties when losing crew due to failed boarding attempts.

Repairs at starbase

When docking at a federation starbase options should be given to:

• refuel energy
• stock on photon torpedos
• conduct repairs

which require an appropriate number of turns

Weaken torpedo aim when tactical computer offline

Pre load SVG

even with the pwa primed, there is a noticeable flicker when icons are viewed for the first time.

Winning condition

Upon destruction of the last raider the game should terminate with a winning message

Publish App in the Microsoft store

https://blogs.windows.com/msedgedev/2018/02/06/welcoming-progressive-web-apps-edge-windows-10/

update check fails

1. button should be disabled while checking
2. show error message of update check fails

fix srs

srs doesn't colour Klingon quadrants correctly of they have just been explored

More nuanced star map

Most sectors are boring; make sure sectors have personalities:

• empty sectors with few or no stars
• sectors with many stars
• star bases with few stars
• klingons form swarms

Starbase to offer protection

Implement changes to starbase:

• shielding
• starbases to fire at klingons

Fire torpedoes while shields are up?

Figure out whether torpedoes can be fired while shields are up. Player might need to drop shields (how much?) if firing torpedoes.

update app menu

App menu should include "check for updates". Disable auto update check

Raider flying through star

Sometimes raiders seem to fly through stars

About screen

About & credits screen:

• title
• version
• URL
• author
• libraries
• licences

LRS click nowhere

steps: LRS, click on a sector title (e.g. capella) instead of a sector. This will show a blank page with hash #undefined.

Weaken phaser aim when tactical computer offline

Should manual phaser fire weaken when the tactical computer is broken?

Detect collision during navigation

Current behavior:
When navigating inside a quadrant it is possible to move over or onto sector which contains already an object (star, starbase, enemy ship).

Expected behavior:
Movement should cease in front of the object obstructing movement in the direction of movement

Implement near range scan

Implement near range scan that shows overview (enemy raiders / federation starbases / stars) of neighboring quadrants

time and xp for star base dock depends on actual needs

Klingon swarms

currently Klingons are placed randomly into a quadrant. the generator should create swarms of defined strength and composition.

adjust reactor output

#42 reduced base consumption, which leaves enough reactor output to always warp and travel at full speed, even when phasers were fired.

Long range scan should not reveal all enemy raiders

A long range scan should reveal raiders only in quadrants that:

1. we are in or have passed previously
2. are immediate neighbors of quadrants mentioned in (1)
3. contain federation starbases

Animate vessel destruction

animate explosion on vessel destruction

confirm leaving page

Ask whether to leave page; unintentional refresh in mobile common cause.

warn when low on antimatter

Status should prominently warn when antimatter reaches threshold required to go to nearest starbase

AI for enemy ships

Implement AI for enemy raiders:

• Raider fires at us on sight
• Raider positions itself if it has no clear line of fire

flag for auto repair during skip?

Implement damage model

Implement damage system for our starship. Damage is caused:

• randomly
• as a result of enemy fire
• by nearby explosions (when firing on enemy raiders or accidentally hitting a starbase)

Afflicted damage affects:

• quadrant overview
• short range scan
• long range scan
• navigation
• warp drives
• shields
• computer
• photon torpedos
• energy reserves

TOS colour scheme

Use a TOS colour scheme

Highscore

Compute a score out of klingons neutralised divided by time.

Smarter PWA caching

The local cache competes with regular resource loading, often downloading resources twice (once for the app and once into the cache). This ticket implements a conditional sequence:

1. defer application initialisation
2. feature-detect if caching and service workers are supported
3. if (2) true, initialise cache and continue deferred application initialisation
4. if (2) not true then immediately continue deferred application initialisation

reduce idle consumption

no restart after reactor failure

the game correctly detects a game over condition when the reactor drops below 20pc but the game doesn't restart after that

Minor repairs while moving

During warp travel and navigation (even in battle), minor repairs could take place. These repairs don't reduce score.

Remember state

When the browser is closed, the current state should be saved. When the web page is opened again, the saved state should be restored.

Disable focus on mobile

Focus makes sense only for devices with physical keyboards

load game regressions

star date, score, Klingons in quadrant inactive, explored quadrants

Phasers balancing

Current behavior: when shooting a raider out of immediate vicinity with low-intensity phasers the raider blows up.
Expected behavior: since low-intensity phasers are 25 energy units and a raider has 100 HP, only light damage should be inflicted

Opportunistic saving

currently the game progress is saved at the beginning of each turn. saving should be offloaded to a timer that checks flags and saves only when the game is idle

lrs reachable quadrants

LRS should show only quadrants that are reachable with the current reactor budget

center app menu vertically

Implement round count

A round indicator for rounds (stardays) that have passed and the remaining amount of rounds. The following actions consume rounds:

• navigation inside a quadrant
• warping between quadrants
• firing weapons
• docking to a federation starbase

Better status indicator

The status report button currently shows remaining antimatter. It should show a composite "health score", consisting of antimatter reserves, engine health and reactor capacity.