Yeaaah... sure.
It worked even though I only did the normal amount (10).  The text originally said 0 while I was doing the quest, but I knew the real number.  Then when I talked to Old Mac, it suddenly changed to this.  Weird.
Screenshot below.
                
            You Know a Quest is Bugged When...
Shamarah

Than
                    Wow, those must be really good...
                
            pfb
                    I had similar - it said I needed 0, gave 7 and got the same number in the Quest Summary once Joe had eaten...
                
            
Drakharran Zealot
I haven't fed him anything.

Canook
                    thats nuts...never happened to me    
                
             
                
Rhombus
                    lol, talking about a hungry devourer  . I do know some other buggy quests: bring some guy his recruits, in post-searing ascalon. I bring the recruits, but they die during the quest. he tells me I failed the quest, but i talk to him again and I made it
. I do know some other buggy quests: bring some guy his recruits, in post-searing ascalon. I bring the recruits, but they die during the quest. he tells me I failed the quest, but i talk to him again and I made it  
                
             . I do know some other buggy quests: bring some guy his recruits, in post-searing ascalon. I bring the recruits, but they die during the quest. he tells me I failed the quest, but i talk to him again and I made it
. I do know some other buggy quests: bring some guy his recruits, in post-searing ascalon. I bring the recruits, but they die during the quest. he tells me I failed the quest, but i talk to him again and I made it  
                Judas Hawksriff
                    lol OMG classic programming error - obviously using an unsigned int to represent the count instead of a signed one (so when the count goes less that zero instead of saying that it wraps round to the highest number).
unsigned_____hex_______signed
4294967295 = 0xffffffff or -1
4294967294 = 0xfffffffe or -2
4294967293 = 0xfffffffd or -3
4294967292 = 0xfffffffc or -4
4294967291 = 0xfffffffb or -5
Its probably got a check in the code as well like;
if ( count < 0 ) count = 0;
But, again, because its unsigned its never actually less than zero nice
 nice
                
            unsigned_____hex_______signed
4294967295 = 0xffffffff or -1
4294967294 = 0xfffffffe or -2
4294967293 = 0xfffffffd or -3
4294967292 = 0xfffffffc or -4
4294967291 = 0xfffffffb or -5
Its probably got a check in the code as well like;
if ( count < 0 ) count = 0;
But, again, because its unsigned its never actually less than zero
 nice
 nice
                
Rhombus
                    says the programmer...
                
            