[Added]/ccolor

[style!]

Do /ccolor [id] work like /ccolor [id] [id]. (Same id x2).

[Faro0s]

I didn't understand lol
You must choose 2 colors i guess.

[WuZi]

The first id is the first color and the second for the second color.

[Miau]

I think he means that the command should automatically use the same color for both indexes if the user only types the first one. For example, /ccolor 7 would be the same as /ccolor 7 7.

It's not a very big deal, but I like the idea, since most vehicles have only one color index,

[style!]

I think he means that the command should automatically use the same color for both indexes if the user only types the first one. For example, /ccolor 7 would be the same as /ccolor 7 7.

It's not a very big deal, but I like the idea, since most vehicles have only one color index,

Yes, sometimes I'm too lazy to write..

I didn't mean to change functionality of ccolor [id1] [id2], just add /ccolor [id].

Something like this:

if cmd = "/ccolor"
   if params.length = 2
      //do ccolor id1 id2
   else if params.length = 1
      //do ccolor id1 id1
   else
      //invalid sintax

[Storm]

+1. I have an addition, /ccolor "color1 color2" instead of numeric value, the player can input a string and the system will automatically get the id of that color. (Use switch-case here). E.g /ccolor blue red

[Faro0s]

Then +1

[𝙎𝙢𝙤𝙠𝙚𝙉]

+1

[Ege]

+1 to the suggestion. Also, speaking of /ccolor command, I have another suggestion:

Can we have a 3rd parameter in /ccolor to save the color? This can be optional like < /ccolor id id yes/no >
When we type yes those colors will be saved and the vehicle we drive will automatically have those colors.
Friauf should see this as he's the one addicted to one color mostly :p

[Storm]

Can we have a 3rd parameter in /ccolor to save the color? This can be optional like < /ccolor id id yes/no >
When we type yes those colors will be saved and the vehicle we drive will automatically have those colors.

That one has already been suggested by me, and it will be added. Read it here

[Altus_Demens]

Do /ccolor [id] work like /ccolor [id] [id]. (Same id x2).

+1. I have an addition, /ccolor "color1 color2" instead of numeric value, the player can input a string and the system will automatically get the id of that color. (Use switch-case here). E.g /ccolor blue red

I like both of the suggestions, +1. Yeah, it is not the most important suggestion ever, but it will simplify /ccolor usage and it is extremely easy to implement. I hope we'll see it in the future updates.

As for Storm's suggestion, ideally all of the colours should be enumerated, using, for example, this and this, so you can forget about numerical values completely. But I don't think "/ccolor chathamsblue capepalliser" will be really widely used unless we've got a lot of designers here. Talking seriously, adding 10-15 main colours would be fine.

P.S. I didn't know that the first colour (/ccolor 1 1) is not really white. My life will never be the same.

[Ege]

"/ccolor chathamsblue capepalliser"

Wat

[Faro0s]

"/ccolor chathamsblue capepalliser"

Wat

[Crash]

are you that lazy lol?

[Niks]

+1. I have an addition, /ccolor "color1 color2" instead of numeric value, the player can input a string and the system will automatically get the id of that color. (Use switch-case here). E.g /ccolor blue red

I like this idea more then numeric