What is wrong with this?

[Antoni]

function createExplosion(thePlayer, command) 
    local x,y,x = getElementPosition(thePlayer) 
    y = y + 20 
    local createExplosion(x,y,z, 0) 
    if createdExplosion == false) then 
        outputChatBox("Failed to cause an explosion.",thePlayer) 
    end 
end 
addCommandHandler("explosion", createExplosion) 

I wanted to make a simple command /explosion that will make an explosion near the player, what is wrong with it?

[DNL291]

Try this:

function createExplosionFunc(thePlayer, command) 
    local x,y,x = getElementPosition(thePlayer) 
    y = y + 20 
    local createdExplosion = createExplosion(x,y,z, 0) 
    if createdExplosion == false then 
        outputChatBox("Failed to cause an explosion.",thePlayer) 
    end 
end 
addCommandHandler("explosion", createExplosionFunc) 

[Antoni]

No I don't think that worked either.

[DNL291]

The code has no errors. Make sure that the meta.xml is correct and the resource is running.

[Antoni]

Why is it createExplosionFunc and where would the explosion take place?

[DNL291]

You can't use a name of a MTA function (not in your case) as a name of a function.

[Antoni]

What? I thought that was the entire point, so for each function I just make it up?

[ixjf]

createExplosionFunc is the handler of the command - you want to call createExplosion inside of that function. You were recursively calling itself (since you overwrote createExplosion, you were now calling itself) and it will end up throwing an error.

Edited April 13, 2013 by Guest

[Puma]

Nah, not a stack overflow, because the second time he executes createExplosion from within the createExplosion function, his createExplosion function will miss parameters (player) and will throw up an error.

He himself made a createExplosion function and that overwrites the default MTA createExplosion function. Just rename your "function createExplosion(thePlayer, command)" to something else like "function createExplosionCommand (thePlayer, command)", don't forget to change "addCommandHandler("explosion", createExplosion)" into "addCommandHandler("explosion", createExplosionCommand)" and you're done.

[ixjf]

Nah, not a stack overflow, because the second time he executes createExplosion from within the createExplosion function, his createExplosion function will miss parameters (player) and will throw up an error.

Indeed, I'm sorry for the mistake, I haven't seen the code carefully.