Author Topic: How to stop moveforward(3); ?  (Read 1884 times)

function serverCmdMove(%client){
commandToClient(%client,'moveForward',1);
//blah blah blah
}

But why bother when you can just press W?
« Last Edit: February 24, 2008, 09:34:37 PM by Falcondude »

that way you can force people to do it!
Or keep walking without holding a button(if I understand correctly)

But then you would also need

function clientCmdMoveForward(%val) {
   moveForward(%val);
}



Yeah, it's stupid.

Also, I forgot... a schedule, I suppose, to stop the moveForward.

Exi, moveForward doesn't need a value, in that sense; just true or false.

Lawl. You guys don't get it. I'll change it to commandtoclient, but still. All they do to stop is /arrived. Duh.
that way you can force people to do it!
Or keep walking without holding a button(if I understand correctly)
2nd one is what I'ma doing, though if I feel like abusin' ma clients, 1st one will work jus' fine.

Just a question, if I make clientCmdArrive will I be able to go /arrive?

Code: [Select]
function ClientCmdMoveForward(%client)
{
   moveforward(1);
}

function ClientCmdstopmoveforward(%client)
{
   moveforward(0);
}

function servercmdtravel(%client)
{
   commandToClient(%client,'moveForward',1);
}

function servercmdarrived(%client)
{
   commandToClient(%client,'stopmoveForward',0);
}

Now that'll make the person who calls the cmd do it, right? Methinks yes.

Yes... you may not need the 1 and the 0 in the commandToClient, though.

Not sure if you're doing that right.

Yes but you have to give the clientcmds to all the players-- put em in a .cs and post a download link.

Oh, you mean for it to work for them... that won't be a problem. Hopefully, when the project is all done, it'll have some GUIs.