Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+1)

Sure I can help out! How are you storing the colors? Are you putting them in as hex codes, pattern number, or color names? If you're using color names (like red, orange, blue, etc), this is how you would do it 

... the command script, handling colors should go in the same spot as where we handle talk sounds
 if (sum x=(extract command from char_table))>0
  # gets the current style
  o:dd.getstyle[]
  # gets the talk value
  o.tsound:first extract talk where command=x from char_table
  # heres the new code!! "color" should be replaced with the name you used in the table
  c:first extract color where command=x from char_table
  o.fcolor:colors[c]
  # end of new code
  # apply the style
  dd.style[o]
 else
... rest of the script

This should work. If you're using pattern numbers instead, instead of colors[c], you just feed in "c" directly into the fcolor (since fcolor is looking for a pattern number). Since fcolor is looking for a pattern number, you probably can't use a hex code, and instead would need to modify the color palette of your game if you want to use different colors outside of the default colors.

(+1)

Just FYI, All About Color includes a module ("col") which can handle conversion between RGB, HSV, and CSS names and find the closest match in the currently configured Decker palette.

(+1)

Thank you so much!! I was missing the part where you define c, I have no clue how that actually works but it works perfectly :')