From our board:

Now we send fleet in three steps. The idea is to reduce this process to one window. Like this

This would make "Speedsafe" against interception more effectiv .... and this is in my opinion one more step to kill "skillgame" !

Don't think it would speed up sending fleets.
Looks kinda messy when it's all in one page.

imo, it's fine how it is, changing it would most likely cause more problems than it's worth...

It's not bad but there is too much on one site. This is quite confusing.

Scripters would love this, they can send fleets with a single http request then. No need anymore to parse intermediary pages or simulate a human clicking 3 times, just send out requests and launch 5 fleets per second.

Especially for avoiding phalanx attacks: prepare the request to send and just flood the server around send time. All it can do is send back a launch failure a lot of times, instead of currently where you need 3 pages between fs arrival and incoming attack.


And as said: way too complex for normal people who don't use scripts.

I wouldn't say it's easier like this. You know, if you make a mistake You can't get back, just "send" and and it's in move. In a few steps there is a chance to think about the movement and possibility to return.

I'll like to be how it's now
the change will kill " esthetics" and you make a mistake selecting sth wrong you can not return

I must admit that what you proposed Dimmetr is really practical in time of needs . Though it will remove the esthetic part of the fleet pages as said Lao Tzi .

usability engineering often tells you to split functionality instead of making one big dialog because this can overwhelm ppl. usability should be kept in mind for the decision.

marshen wrote:

usability engineering often tells you to split functionality instead of making one big dialog because this can overwhelm ppl. usability should be kept in mind for the decision.

+1
Current way is nice and easy to understand, and doesn't "overwhelm" people who are new to the idea of fleeting