daid / daid/EmptyEpsilon

SUGGESTION - "Charging" Warp

Open
#399 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lua
Stars
869
Forks
222
Avg merge
18h 33m
Merged PRs (30d)
1

Description

Jump and Warp are quite different and interesting ways for long distance travel, each with it's advantage and drawbacks. In pvp, both are appealing and offer diversity on the battlefield.

Our tests in pvp have shown that warp can also be used in an odd way that seems to get out of the boundary of it's own purpose (long distance travel). It's instead used as a short burst, exactly the same as the "maneuver boost" pad, but better and with unlimited use. It put a lot of inequality in a fight.

The suggestion is to add a small charging time when using warp, during which time the ship could not move (or have diminished speed/maneuver). In fact it could simply be the same as when you Jump, but for 3 seconds. This 3 secs, would go faster if the warp engine is overcharged by engineering. That would aims to make the player use the Warp engine in a more strategic way, and to leave other players a chance to react during combat.

Here's an exemple of warp drive in Rebel galaxy :

https://www.youtube.com/watch?v=K0ZMAlcD7XA

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the warp implementation and comparing it with Jump and the maneuver boost behavior; done means Warp has a short movement restriction or reduced-speed charge, and engineering overcharge affects that charge time as described.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
game-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.