Player Features and Ideas Discussion

I began this thread by considering the capital jump drive and related issues in Eve. I saw massive Titan fleets and hotdrops on one or two players at a gate or in an anomaly; many of which I took part in. Instant movement of major enemy forces across large distances and deep into enemy space (normally considered the role of black ops). Consideration of these issues led to interesting discussion concerning hyperspace technologies and cyno-jamming fields. Have you ever wanted to fly ships like the Enterprise, the Dedalus, or the Destiny, traveling between systems using your own ship's hyperspace drive? I have, and not just for capital ships either. Here we will also talk about siege/triage, doomsday devices, and other hot topics of capital ship warfare. Much of the material in this OP was consolidated from my later posts.

The various main sci-fi franchises typically utilize hyperdrives and FTL drives for interstellar travel, though ships do travel through stargates if they are small enough (Stargate franchise). You can read many more interesting facts about interstellar travel here http://stargate.wikia.com/wiki/Hyperdrive , "It is estimated that the Prometheus' Asgard hyperdrive is capable of speeds around 803.52 trillion miles per hour, or about 136 light-years per hour, or about a kilo-parsec per day." The facts here form a basis for the hyper drive proposal to follow.

Cynojamming jams cynos thus preventing the jump drive from obtaining a lock. Currently, there is only a sov-based pos array. I want to add a cynojamming HIC script, a pos module not requiring sov, and a sov upgrade in the IHUB.

The hyperdrive proposal:
A ship can fit a hyperspace drive as either a medium slot propulsion-style module, or as an astronautics rig. Both will consume capacitor for fuel depending on the ship type. The medium slot module will use isotopes (depending on ship race) after the capacitor falls below 2/3 in order to supplement the capacitor to maintain peak cap regen. Lacking the module or the isotopes, the travel speed and capacitor usage will be proportionally reduced to match the capacitor peak recharge. The medium slot module consumes 20 GJ/s or 500 GJ/ly The cycle time is one sec and activation is 20 GJ. The maximum range given sufficient capacitor or fuel is 15.5 ly. The maximum travel speed is 2.4 ly/min. Hyperspace travel may be stopped at any time during the trip with Ctrl-space. In order to travel, right-click on the ship's capacitor after the most recent gate jump/session change is required to set the destination to any celestial object, bookmark, or 100% scan result in any system or in deep space within range and a distant marker will display on the overview for alignment. The ship must not have any hull damage, else the ship's hull will be torn apart while in hyperdrive.

In order to enter hyperspace: The ship will align toward the destination point and fuel will be consumed when the module is activated, and once it reaches the required speed (same as for warp), the ship will enter hyperspace travel at the same time that a hyperspace window opens with 2500 m in front of it. Any ship with a hyperspace drive will be able to align and lock onto the same window by right-clicking the capacitor so long as the ship is traveling in hyperspace and the following ships have sufficient fuel/capacitor to follow. Ships that enter hyperspace at the exact same moment may lock each other and engage in capacitor warfare and energy transfer. If at any time the capacitor falls below 2/3, fuel loaded in the medium slot module will be drawn as much as is needed to fill the capacitor up to 1/3 + 20 GJ for the next cycle. Once the isotopes fuel is depleted or in the case of the hyperspace rig (which cannot use isotopes), the ship will automatically reduce speed in hyperspace to match the peak capacitor regen rate. All other ships will fly past and "off-grid" at that point and all locks will break. If the ship leaves hyperspace, the hyperspace drive will cool down for 2 hours before it can be engaged again. The ship may cloak and wait out the time/log off after all timers, or sit there uncloaked and be scanned out by deep space probes. Those ships which entered the hyperspace window (which remains up while any ship is traveling through it) will continue to the target even if the originating ship dropped out of hyperspace early. Their hyperdrives will also have to cool down for two hours. Only one hyperdrive may be fit per ship. 25 CPU and 1 PG. Being completely different from warp technology, nothing can stop a hyperdrive from engaging once the hull hp (100%), alignment and fuel requirements are met.

New interstellar probes can scan down ships stranded between systems to provide a point to which a hyperdrive can lock. Fleetmates can enter hyperspace and travel to each other if the travel takes them out of their current system.

Triage and Siege should both be changed to allow both incoming RR and incoming energy transfer. They should also allow fighters (carriers) or drones, warp, movement and incoming eWar, including warp disruptors.

Important information has been consolidated to the original post.

Posting in a stealth "I don't like having to run a Cyno alt" thread.

Also agreeing with Danika but too lazy to re-type all of what (s)he said.

Your thoughts on the op's post is "Tartarus Ventures?"

Since a cap ship travels in a straight line to the system it jumps to, you can't "hop off" at a system along the way because seldom would the straight line ever pass through another star system. Also cynoing is akin to instantaneous stargate transportation as opposed to in system warping. Suck it up and keep using those cyno alts.

It would certainly be amusing if ships that ran out of fuel midway got stranded in deadspace.

Great discussion.

Good information about distances and travel speeds. Let's consider non-cap ships traveling on their own drives between systems. This happens routinely throughout other sci-fi franchises.

You know, you have an interesting idea of using of the warp drive outside the system. If a ship got stuck between systems because it doesn't have fuel to power its hyperdrive for the 6 minute journey across 13 ly, then if it could use its warp drive to travel to the nearest system then it would take 25.1 hours per 1 ly. The warp drive would continuously pull capacitor so that the entire amount of capacitor for the distance was not required all at once at the beginning. The warp speed could be lowered to make the ship cap stable and not require rests to regen cap. The ship simply aligns the direction that it wishes to warp and then engages warp in continuous mode. When it gets to the place it wishes to stop, then it exits warp by deactivating the continuous warp icon. A specific distance could be entered into the continuous mode warp to exit warp automatically at a certain location/system. Or the ship could just use the hyperdrive again after the cool-down timer.

... bit surprised no one has offered the counter-proposal "biomass yourself" to the OP.

GUYS LOOK HOW COOL I AM, I FLY A CAPITAL