Debate

Why debate? Whoever is in charge of the project calls the shots.

Engine level coding is probably a huge waste of time. There is not much need to make your own engine these days. The only reason people like to do it is to earn experience and have something they can put on their resumee. It doesn't benifit the project in ANY way for ur programmers to waste their time with those things.

I say, slap them back into their place and don't let them get out of line again. It obviously went too far this time. Don't let it happen again.

Well said sharpnova and I'd taken my call but at the same time, I cant afford to lose even a single guy and want to keep them focused towards what they are doing but they generally look at the people who are working on Unreal 3, CryEngine 2 and even OGRE.
Thanks for replying...

It doesn't matter which is more challenging or less monotonous - if you have a project to run, then you need to know what needs doing, and you need to find people to do it. If you're not paying them, and they won't do what you think needs doing, then you're a bit stuck. I don't think anything we can say will change their mind on what they find most interesting.

Which is more important? Well, since you can't make a game without either, then obviously they must both be equally important (though you can buy the engine).

Which is more challenging? That is an absurd question. Which is harder to win -- a sprint or a marathon? The level of challenge depends completely on the person and the goal. A person that thinks gameplay programming is not challenging is most likely just content with mediocre gameplay.

BTW, I am an "engine" programmer and here is how I see it: the first engine can be very interesting (as with anything), but after a few times it can get boring because the job of an engine programmer is to solve the same problems and write the same code over and over.

@johnbolton
By using the word important, I actually mean the availability and comfort level as we can always buy a state of the art engine but gameplay has to be different for each game so writing an engine is not as must as gameplay.
By challenging, I exactly meant the monotonous kinda feeling which you stated in your remarks about your experience with first engine and then making it a repeat task.
Thanks for your feedback.

Try and accomodate them as much as possible; if you have engine programmers who want to get into other areas of coding, arrange a swap.

Otherwise... being on a team is about working together on a common goal, and that means pulling your own weight even if there's other stuff you'd rather do. If it comes down to some prima donna whining because he's not working on what he wants to work on, then he can find another project.

I'm leading a team of about 32 for a game right now. I've come across a couple problems such as this even though the project is just barely under way. It is essential that you let them know you they can come to you with such concerns but it is equally important that you dont let them push you about it. As others have you said, what the project leader says should be accepted as law. As long as you adress their complaint -- probably using the reasoning others have just afforded -- you can stay on their side while getting them to still "do their job."