Player Features and Ideas Discussion

I would like the ability to plot a course with a short sequence of text commands, e.g.

L120 10km repeat

Which would give me a triangle course with 10km legs (left 120 degree turn, 10km straight). Left / Right / Up / Down OK for directions (or Port/Starboard for navy traditionalists)

Set speed could be nice for fleet actions, as F/C could call out a turn:

R20 200ms (right turn 20 degrees, maintain 200 m/s)

Edit:
Would be even better if all commands could be done from the keypad.

+ or - : right or left
++ or -- : bank up / down
* : set leg distance
... : repeat

So previous example would become:
+120*10...

I would say allow some limited number of scripted maneuvers to be added to the ship control console, then don't allow the FC to control it, it would be called out.

Seems better than "orbit the anchor!" Shoot B-U in the Harbinger!" "next is blah blah"

I like this idea, +1

you should use headings instead of L/R +/-

http://en.wikipedia.org/wiki/Cylindrical_coordinate_system

what would this allow you to do that cannot already be done? besides just being formation flying, what does it bring to eve gameplay (not saying it doesnt bring anything, just need you to explain it to me)? this would seem to me to require decently sized code that would cause more server-side resource utilization (not that im an expert) so it would stand that it would need a decently sized justification.

It will not need any server side resources omg. It would all be client side and client would send same data as usual to the server (3 variables for heading including desired speed).

It would not increase / make more easily to bot, since we talk about relative control of yours ship no absolute commands like "fly here to this thing".

Soo while it can be done, I really think its not time for this. I can see some plan like this:

1) First ships are modeled as vectors. CCP needs to change that from 6 variable (3 position, 3 heading+speed) into at least 7 (3 position, 3 heading, 1 speed) or make some changes to calculation of speed (like if heading vector x^2 + y^2 + z^2 < 1 ship stays put) so that ships will remain theyrs heading even at 0 speed (and will therefor not move to align to a plane).
If you would like to have real space model, you would need 6 variables just for position (3 axes + 3 rotations) and another 6 for movement (3 axes + 3 rotations).

2) LOS (line of sight; line of shoot) needs to be implemented, this will make blobs harder and will be start to actual tactical combat.

3) bumping model should be improved to be at least eliptical (we have sphere now) or to include more spheres for single ship.

After this (and yes these things would be huge increase in server's load) more precise way to move yours ship would have meaning.

Glad you asked. The example I ran into the other night was when I was webbing a sleeper BS which was just at the edge of my logi's range. If I orbited the ship, even in a close orbit, it took me out of range, and I didn't want to stay still. What I ended up doing was zigzagging back and forth by manual piloting.

As for server-side resources, the types of course directions proposed are actually much easier to compute than an orbit calculation, and it avoids the joystick problem of overwhelming the server with client-side course updates. Sending a course from client to server is one request, after that the server can perform all course calculations server-side.

Also, from an immersion perspective, starship commanders are supposed to call out courses, not tell their helmsman, "steer a little left and up from the star ahead. No, not that star, the little blue one..."

LOL I don't think what he's asking for would make botting "easier" it's easy enough already. This seems like a standard cop out comment when someone does not like the idea.


I dig the idea. If for no other strategic value than formation flying. Calling "right 20 degrees down 30 degrees speed 150 execute in 3 2 1 now." would maybe not be an often used tactic but ti would help provide some epic videos! :)

The code should be hardly anything. I'm guessing it would be client side except for the direction the ship needs to turn to. IE they could possibly simulate a double click on the screen at the correct spot.

User clicks on a designated button and the client sends a call to the double click function with the location being the new calculated spot based on the ships current heading.

Speed could be adjusted separately. A few options for changing direction together would be pretty choice though.