New ennemy #96
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A new ennemy vessel tries to suicide itself like the default vessel. Though this new ennemy starts a bit far from the target, lock it and wait a bit. A small back and forth announce its departure to its target, in a straight line, quickly. 300ms before it actually starts going, a small line goes from it to its target to announce its trajectory
Implemented in
890e1c8as the "lancer".It follows the brief in four beats:
and refuses to charge until the fleet is inside
lock_range(820px).holds it for a 1.2s wind-up. Nothing re-reads the fleet after that, so the
charge goes where the target was and stepping off the line works. That is
the whole reason the telegraph is worth reading, and it is the same bargain
the mothership's big laser makes.
wind-up, leaning backwards first, and does not drift sideways at all.
down the trajectory, brightening as the launch approaches, with a tick
across the locked point. Exactly the last 0.3s of the 1.2s wind-up.
Then it crosses in a straight line at 950px/s, flies through the locked point
rather than stopping on it, coasts to a halt and starts hunting again. Like
the chaser it is
dies_on_contact, so it trades itself for the vessel ithits - 2hp, so it is cheap to shoot down if you see it coming.
It is registered in
EnemyDefinitions, so the setup editor can place it on anymap, and the roaming spawner gives it a 25% share - otherwise a new enemy would
exist only in the editor and never be met in open space.
Covered by
tests/test_lancer_enemy.gd. Measured on the last run: rocked 30pxback and forth with 0px lateral drift, line up for 0.30s of the 1.20s wind-up,
charged 1124px at 950px/s with 0px off axis, and the ship that dodged when the
line appeared survived with the locked point landing 400px away.