Pre-booking system in launcher needs a big improvement

After 1 organized open race and preparing next one with 2 nearly full servers: between 40 and 48 drivers for both servers, I made my conclusion about the system:

Very good idea, no problem: no booking - no long wait time before entering the server - no car error - etc...

But, at the opposite .... the launcher in this point of view is a real nightmare !

- the big 1st of all: No modifying button for an already done entry !... you need to delete and begin again or make the modifying in the entry_list itself.
Never saw a add and delete without a modify !

I decided to create a base entry list with all driver's names and Steam Community ID. Why ?
easier and quicker just deleting the ones not present for this race.
Easy ??? no of course as for next race you cannot modify cars and skins !!
Next time ... begin all the bargain again with 50 drivers !....
And I don't mention that a driver may change his driver's name or skins and : so ... delete and begin again.

Please Kunos, try your pre-booking with 2 servers and 48 drivers and you'll easily understand the problem.


- mandatory skin precise entry, else even if you choose a car before entering ... you get another colour or skin, even though you chose an original skin of the game !!
I think that this can easily been changed.

About the launcher itself: the problem is only: multiple car choice but ... no multiple track choice for a looping sessions server.??

when preparing a server with those conditions .... you're near the nervous breakdown ... as moreover you have to deal with ID errors, driver names' errors, unknown real name for the skins, and so on ... which we usually can easily manage ... and once done....afterwards begin with the pre-booking nightmare !

The proposed changes:
1) add a modify button in entry list
2) no mandatory skin precision in this entry list ( just optional choice when needed )... and chosen original car before entering is the one you get on the server
3) please add a multiple track choice for tracks in launcher.

I'd even go further: for entry_list Driver's name and Steam Community ID is enough.
Once done, it's good for a long time, except sometimes add a new driver.
If the chosen car is not the right one, the driver won't be able to enter the server.
If he choose a wrong skin ? ... what is the problem ? ... the other drivers will tell him he made a mistake.

I'm just trying to remain logical and practical for a perfect and easy use.
Since publishing I spent 90% time organizing and just 10% driving ... sad no ?

 

Another idea about Entry_list:

This pre-booking is of course mainly meant for leagues. ... Leagues have all forums .... so why not an independent little soft with this entry_list , which might be used in the forum itself ?

Once the launcher prepared with car choice, the league drivers might fill their own entry: name - ID - car ( from restricted list according to chosen cars in server_cfg file ) - same for chosen skins ( and not forget a 'Modify' button in case of errors )

What an easy system for all admins and race organizers !

 

would it not be a good idea to allow the server host to set a minimum amount of player for the server they are hosting,so when booking is down to say 30 seconds it will pause until the minimum players are booked in,this would insure good lobbys with nice amounts of racers in them,just a thought.

 

Pre-Booking makes me join servers that i think have people signed up, but after joining its me and one or two others (and 15 away from keyboard drivers)

 

I got on a server I thought had 15 real players yesterday, however they were all just prebooked ghosts. I was on my own. Just sucks.

 

Suggestion.
Please consider to implement an automatic boot system, after an portion of inactivity time by clients in the server. To avoi unnecessary load of data in the server.