The CTRL + F8 command which returns the WR for that combo is pretty cool.
But... could it show the splits of said WR too?

I think it would be nice to have.

You'd hit CTRL + F8 and receive a WR by :Someone: (13.67) (46.20) 1.15.290 for instance.

If it's not too much work to add it and others agree, can we have it?
I think it would be cool to have the splits too instead of "only" the WR time.

+1, that's a pretty good idea.

+1 .. I like it too.

+1

+1

Would make it easy to see how much and where your loosing time

+1

:iagree:

I'm +1 on that. Always wanted the splits to appear whenever I check the WR for a new track, so I know what is actually fast

anyone?

i don't know how this improvement forum works...
so this idea gets on a list or something?

Quote from Meanie :

anyone?

i don't know how this improvement forum works...
so this idea gets on a list or something?

The way it works is quite simple, actually: Devs read the suggestions, think about it and add the requested feature if they feel it's a good idea. When they will add it is a different matter, though.

+1 i like this idea to it can sometimes help people when driving a new circuit.

I'd like to get my HL position on the chart too, when I type /w HL.

+1

Quote from Linsen :

The way it works is quite simple, actually: Devs read the suggestions, think about it and add the requested feature if they feel it's a good idea. When they will add it is a different matter, though.

Yeah, cool.
I just wanted to know if a well accepted idea would get into a "list" or something or if just a thread like this would suffice?

As with the recent change with pb messages, the problem arises that a message quickly becomes too long to fit on 1 line.

There is room for 63 characters in 1 line.
24 characters of them must be reserved for the username and a <space>
7 more characters are reserved for the line prefix "LFSW - "
So that's 63 - 31 characters = 32 characters for the rest of the message.

See if you can come up with a decent use of space and I'll implement the best option you come up with

The only thing i can think of is to have something like this
/w wr splits
LFSW - <username of WR holder> Split 1: xx: xx.xx
<new message>
LFSW - <username of WR holder> Split 2: yy:yy.yy
<new message>
LFSW - <username of WR holder> Split 3: zz:zz.zz


Im not 100% sure but i think that there is a 1st and 2nd split, and the 3rd split is the finish line. I hope you understand what i mean, if not i will try and get a screenie of what i mean by using /msg commands on one of my servers or something.

<edit> - added image

maximum split count is 3, excluding finish line - so some tracks have 1,2,3,F - 4 times to display.

1:23.45 1:23.45 1:23.45 1:23.45

As such, having all splits on 1 line just isn't possible. Like you said multiple lines would then be the alternative, though I've always tried to prevent that at all cost.
If it really must be so, i'd try to keep it on two lines though.

LFSW - wr by <username> : 1:23.456
LFSW - Split1 1:23:456 - Split2 1:23:456 - Split3 1:23:456

for example

Good job i checked the thread before i took a screenshot of my other idea, exact same as what you just posted .

alternative :

LFSW - wr by <username>, set on 1 Mar 2007
LFSW - s1 1:23:456 - s2 1:23:456 - s3 1:23:456 - L 1:23:456

Vic, that's cool.

Quote from Victor :

alternative :

LFSW - wr by <username>, set on 1 Mar 2007
LFSW - s1 1:23:456 - s2 1:23:456 - s3 1:23:456 - L 1:23:456

That would be grand.
59 characters on second line? It's doable then, right?

That would be really really useful.
I think it would be best for it to be "linked" to the /w wr command.
And not having a /w wr splits or /w wr s command.

Anyway, i (and many others) hope it gets implemented then.

Thanks Vic.

Quote from Victor :

alternative :

LFSW - wr by <username>, set on 1 Mar 2007
LFSW - s1 1:23:456 - s2 1:23:456 - s3 1:23:456 - L 1:23:456

Second line perhaps clearer this way:

LFSW - WR laptime 4:44.444 (1:11.111 - 2:22.222 - 3:33.333)

Also WR in upper case please, it's an acronym. BTW, why is there 64 char limit, anyway?

There has to be some sort of limit, the string will have a defined length. 64 characters has been deemed an appropriate length.

Quote from Victor :

alternative :

LFSW - wr by <username>, set on 1 Mar 2007
LFSW - s1 1:23:456 - s2 1:23:456 - s3 1:23:456 - L 1:23:456

I suggest the second line becomes


That would save space

Quote from duke_toaster :

I suggest the second line becomes


LFSW - 1:23.456+1:23.456+1:23.456=1:23.456


That would save space

I think it's better as Vic suggested.
If it's going to exist a new line anyway it would be nicer for it to be easier to read than to be shorter and "too crowded" (my english sucks but i guess you get the point).

I think Victor isn't really worried about the numbers of characters.
He's "worried" about lines.
Since it's going to be 2 lines anyway might as well make the best out of it.