Lazer Firing Mechanic Rework

Based on the recent playtest, most players dislike our current lazer firing mechanic.

The common complaints are:

• Dislike charge up time (too long)
• Dislike movement lock
• No incentive to use mirrors
• Projectile speed too low
• Projectile range too short
• Projectile reflect level too low

Proposed Rework:

1. Change firing mechanic to use "drones" (Implemented in #103)

• Drones are deployed when the player attacks, and performs the lazer charge-up and firing on behalf of the player
• Players are no longer movement-locked
• Players have drone charges, which are consumed when firing and regenerate at a fixed rate up to a max capacity
• Players are (hopefully) more incentivized to use reflects and such, since their damage is now made more indirect

2. More powerful lazers

• Buff projectile speed
• Buff projectile range (experiment with infinite range)
• Buff projectile reflect level to 3 (a reasonably visible amount of reflects)
• Experiment with lazer pierce
• Note: Increases to powerup values and/or spawn rate can also remedy the above issues

Issue History:

There are two solutions, and the community has been engaged to pick one.

1. Cooldown/Ammo System

• Instant firing of lazer, no charging!
• You can fire as many times as you have ammo
• Ammo refills by 1 every x seconds (up to your capacity)

2. "Bomb" system

• Similar to bomberman bombs
• You leave behind a drone, which does the charging and firing for you so you are free to move about
• The drone also blocks other players' movement, watch out that you dont trap yourself!

The results will be tallied tonight (3 Apr), 2359 and this issue will be updated.
Edit: Results are a tie, the team has decided to go for the bomb system.

Start by reviewing the drone implementation referenced in #103 and the issue's final decision to use the bomb system. Compare the current behavior with the listed goals for movement, charge regeneration, projectile speed, range, reflects, and pierce. Done is not precisely defined because the issue leaves several values for experimentation and does not name files or tests.