Game Development Stack Exchange is a question and answer site for professional and independent game developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I just added an option to my game that makes it so that all the enemies will have a random color for their clothes instead of the regular blue. I use this code to draw rectangles over the shirt of the enemy.

BufferedImage image = new BufferedImage(z.getWidth(), z.getHeight(), 
    image = File("C:\\Program Files (x86)\\ZombieGame\\
}catch (IOException ex) {
int j, k, red, green, blue;
    for(j = 0; j < z.getWidth(); j++){
        for(k = 0; k < z.getHeight(); k++){
            Color c = new Color(image.getRGB(j, k));
            red = c.getRed();
            green = c.getGreen();
            blue = c.getBlue();
            if(red == 0 && green == 0 && blue == 178){
                Rectangle r = new Rectangle(j,k, 1, 1);
                Path2D.Double rect = new Path2D.Double(r, at);

The thing is that when I apply this the game will run twice as slow (before I added this code I got a solid 80 fps but as fast as I added it I got around 30 fps). Is there a better way in which I could change the color of specific parts of the image without lowering the fps drastically?

share|improve this question
Unrelated to the question, but hardcoding C:\Program Files (x86)\ZombieGame is a bad idea. – msell May 21 '13 at 15:26
up vote 2 down vote accepted

You would probably be better off having your artists produce variations on the default color set, and decide which one to use when the zombie is initially created. The implementation you are using now performs per texel checks to only change a specific color, and say your image is 100x100, that is 10,000 color checks per zombie, on top of the final draw calls. This is a ton of run time overhead just for changing a color. Instead, you could simply select a random texture when the zombie is initially created using a single call to a random function.

share|improve this answer

Evan seems correct. It may also be possible to divide the zombies into two textures; one consisting of any parts of them not likely to change color (ie, skin) simply floating in midair, and another for parts of them that may change tint (ie, shirt). You could draw these on top of each other, and specify a tint color only for the second texture in the SpriteBatch call.

I still feel like there may be a better option; I'm fairly sure there was some innovative approach to this in RTS's like Age of Empires and Starcraft (in which each side's units have bits of a certain color on them).

share|improve this answer

You could reserve a certain color value in your image to be the "tint color", something you are unlikely to actually use like (0, 255, 0). Then create a function that copies the image and loops through all the pixels, every time you find the tint color replace it with some other color using setRGB().

Then for each zombie variant, create a new variation of the image:

BufferedImage redZombie = tintImage(image, red);
BufferedImage greenZombie = tintImage(image, green);

If you were using openGL or DirectX I would have recommended just doing it in a pixel shader.

share|improve this answer
I'd be concerned about doing this in a pixel shader IFF it involved a test and branch - I have a pathological dread of stalls :-) – Mark Mullin May 22 '13 at 1:00

Evan is right if you have the artist bandwidth, otherwise, you could make this algorithm a lot more efficient. The issue you have is that you're twiddling individual bits in about the most expensive possible way you could.

Right now, you're testing each pixel individually to see if it's blue and changing it if it is - however, you said that you're drawing rectangles

A) Consider making a Boolean, say IsBlueEnemy that indicates that the enemy instance is in fact blue - or you could make this a color property with value 0,0,178, eg EnemyColorProperty

B) If the enemies are all of the same size, then either define constants that give the X and Y origin and the width and height of the rectangle, or define a static rectangle that you reuse (I did the former to illustrate, but the latter is preferable)

C) Now fill the whole rectangle in one fell swoop (note I am not defining g2d and at since you didn't either :-) )

     Path2D.Double rect = new Path2D.Double(r, at);
     IsBlueEnemy = false;

If you don't really have a solid rectangle, i.e. there are occlusions you don't want to paint, then you need to dig into the image and get a hold of the raw bits and manipulate those - the bottom line is that the routines you're using are very expensive and are really only useful for messing with a few bits at a time if you're concerned with performance

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.