| Blockland Forums > Modification Help |
| Script crashes game |
| << < (3/4) > >> |
| Red_Guy:
--- Quote from: Destiny/Zack0Wack0 on May 25, 2011, 07:30:28 AM ---2. At the moment you're scheduling for 500 milliseconds, and because it's just looping straight through them it's going to do every single shift of the brick in 500 milliseconds, rather than having a 500 millisecond gap. Either remove the schedules altogether or make it like that. The reason it's crashing is probably because you're overflowing it with useless schedules that all happen at the same time. --- End quote --- What he said.. you can also try something like this: schedule(500 * %a ,0, so your schedules wont happen all at the same time. And lastly - im not sure if the arguments are correct here: --- Code: ---schedule(500,0,commandtoserver,supershiftbrick,0,0,1); --- End code --- do a trace for supershiftbrick and check the arguments. I suspect you will need to do something like this instead: --- Code: ---schedule(500,0,commandtoserver,supershiftbrick,"0 0 1"); --- End code --- |
| Treynolds416:
Supershiftbrick has four arguments, as I'm aware. Not sure what the first one is though, it's usually a four of five digit number. |
| Placid:
--- Quote from: Destiny/Zack0Wack0 on May 25, 2011, 07:30:28 AM ---1. The %i= part of the for statement is what the value starts as, the end part is what it does AFTER the stuff inside the for loop has been processed. 2. At the moment you're scheduling for 500 milliseconds, and because it's just looping straight through them it's going to do every single shift of the brick in 500 milliseconds, rather than having a 500 millisecond gap. Either remove the schedules altogether or make it like that. The reason it's crashing is probably because you're overflowing it with useless schedules that all happen at the same time. Also, change placeBrick to commandToServer('plantBrick'); like suggested earlier. --- End quote --- Alright, so I should change it to a variable set to 500. Gotcha. --- Quote from: Red_Guy on May 25, 2011, 03:19:24 PM ---And lastly - im not sure if the arguments are correct here: --- Code: ---schedule(500,0,commandtoserver,supershiftbrick,0,0,1); --- End code --- do a trace for supershiftbrick and check the arguments. I suspect you will need to do something like this instead: --- Code: ---schedule(500,0,commandtoserver,supershiftbrick,"0 0 1"); --- End code --- --- End quote --- I looked up a servercommand list, and it's /supershiftbrick X Y Z. I'm not quite sure if that would go "x y z" or x, y, z, but I'll test around with it later. At the moment I will not be able to work on this due to finals being tomorrow. I'll work on it Friday. |
| Greek2me:
--- Quote from: Treynolds416 on May 25, 2011, 04:33:49 PM ---Supershiftbrick has four arguments, as I'm aware. Not sure what the first one is though, it's usually a four of five digit number. --- End quote --- That would be the client. It's a serverCmd, so there has to be one. |
| Treynolds416:
--- Quote from: Greek2me on May 26, 2011, 02:33:49 PM ---That would be the client. It's a serverCmd, so there has to be one. --- End quote --- That's what I thought, but it always changes, so it can't be. |
| Navigation |
| Message Index |
| Next page |
| Previous page |