Thoughts about a monochromatic option for FFR gameplay?

[iironiic]

It was a random thought that came to me one day and I am curious if this is a good or bad idea.

I don't see how having this option gives a player an unfair advantage to scoring well. All it does is make FFR more readable for some charts and perhaps lessen mindblocks for some people on some files, especially very colorful ones. What are your thoughts on this?

[Kibblre]

Seems like it could just be implemented as a noteskin similar to flat in DDR. Wouldn't give anybody an advantage like you said.

[justin_ator]

It's VERY easy to implement in Velo's engine, I'd assume it's not much harder in the official.

All I did (did something of the sort toying around with velo's engine before on the community engine site) was to set up a mod (similar to stealth) just instead of the opacity value being changed, just have an overwrite for the color values for each note changed to whatever color is decided on.

my_color = new Color(_root.main.gameboard["a" + dir]);
        myColorTransform = new Object();
        switch (_global.noteBox[0][2])
        {
            case "blue":
            case "red":
            {
                myColorTransform = {ra: "100", rb: "0", ga: "100", gb: "0", ba: "100", bb: "0", aa: "100", ab: "00"};
                break;
            } 
            case "green":
            {
                myColorTransform = {ra: "100", rb: "255", ga: "100", gb: "0", ba: "100", bb: "-107", aa: "100", ab: "00"};
                break;
            } 
            case "orange":
            {
                myColorTransform = {ra: "100", rb: "0", ga: "100", gb: "100", ba: "100", bb: "-255", aa: "100", ab: "00"};
                break;
            } 
            case "pink":
            {
                myColorTransform = {ra: "100", rb: "255", ga: "100", gb: "-25", ba: "0", bb: "-255", aa: "100", ab: "00"};
                break;
            } 
            case "purple":
            {
                myColorTransform = {ra: "100", rb: "255", ga: "100", gb: "41", ba: "100", bb: "231", aa: "100", ab: "00"};
                break;
            } 
            case "white":
            {
                myColorTransform = {ra: "94", rb: "157", ga: "50", gb: "-84", ba: "100", bb: "50", aa: "100", ab: "00"};
                break;
            } 
            case "yellow":
            {
                myColorTransform = {ra: "100", rb: "255", ga: "100", gb: "255", ba: "100", bb: "255", aa: "100", ab: "00"};
                break;
            } 
            case "cyan":
            {
                myColorTransform = {ra: "100", rb: "204", ga: "100", gb: "185", ba: "100", bb: "-255", aa: "100", ab: "00"};
                break;
            } 
            default:
            {
                myColorTransform = {ra: "100", rb: "0", ga: "100", gb: "100", ba: "100", bb: "255", aa: "100", ab: "00"};
                break;
            }

so for this "mod" you'd just change the color values to all be the same thing, thus making it a "flat" noteskin. I'm assuming this only works with the regular noteskin, and also assuming Velo didn't change the way the engine uses the default noteskin.

edit: I guess my point in posting this is that the reason for not doing it should be a valid "We don't think it's a good idea" not a "we don't feel like implementing it"...

followup edit: I recall Velo showing us an example of a customizable swf for all the noteskin colors, so I do believe that his goal was to have all the noteskins run on the same "color" code for each "note", which would mean that this "mod" I posted about above could apply to all noteskins in his newer engines if he stuck to his original plan.

[Velocity]

Noteskins in Legay/Velo uses a single image which has a color transform applied to it.
R^2 uses 2 layered png's and a color transform to change colors.
R^3 just uses a external swf that has all the notes precolored.

[justin_ator]

So is this potentially an option (or 'mod' if you will) that you would consider adding?

[qqwref]

Originally Posted by justin_ator

It's VERY easy to implement in Velo's engine, I'd assume it's not much harder in the official.

All I did (did something of the sort toying around with velo's engine before on the community engine site) was to set up a mod (similar to stealth) just instead of the opacity value being changed, just have an overwrite for the color values for each note changed to whatever color is decided on.

You don't have to overwrite it at all, just add an if statement It would be something like if (_root.flatmod) { [blue colored note] } else { [normal color code] }.

[justin_ator]

Valid point

[TC_Halogen]

+1; flat noteskin would be great for a number of reasons.

[customstuff]

It would be really cool if you had options for each type of note (4th, 8th, 16th, etc.) to enter a hex code or something like that. +1 for this idea from me too.

[Raining Nails]

This is a great idea.

Would the integrity of the blue-note and/or crazy-background files (like Party4U, Caprice, FoTBB etc.) be lost if you could, say suddenly color the notes red to make them stand out more? I know you can switch noteskins to circles and heart etc. which can help a bit, but I figure a lot of scores would suddenly increase on those Legacy songs.

I might be totally off-base, but I thought I'd mention it.

[Mourningfall]

Originally Posted by Raining Nails

This is a great idea.

Would the integrity of the blue-note and/or crazy-background files (like Party4U, Caprice, FoTBB etc.) be lost if you could, say suddenly color the notes red to make them stand out more? I know you can switch noteskins to circles and heart etc. which can help a bit, but I figure a lot of scores would suddenly increase on those Legacy songs.

I might be totally off-base, but I thought I'd mention it.

Anything that makes the notes standout more on the legacy songs with backgrounds
or the dynamic squares/circles/whatever has my full support. I normally try to avoid them at all cost.