Blockland Forums > Modification Help
"Should never be considering a brick bigger than us here!" -Solved
Slicksilver:
I'm still not seeing the error. Make the schedule 1000ms and see if it crashes at a specific point or right at startup.
Jardev:
--- Quote from: Slicksilver on February 22, 2012, 12:56:29 AM ---I'm still not seeing the error. Make the schedule 1000ms and see if it crashes at a specific point or right at startup.
--- End quote ---
It wasn't right at start up, at 1 ms it happened maybe about 100 bricks in, I will try to record the data at which point it crashes.
Brian Smithers:
trace(1);
-do-
-crash-
-postconsole-
tracing is always the answer.
Jardev:
--- Quote from: Slicksilver on February 22, 2012, 12:56:29 AM ---I'm still not seeing the error. Make the schedule 1000ms and see if it crashes at a specific point or right at startup.
--- End quote ---
This was actually the trick. I slowed it down to 1000ms, and it worked fine twice through. Lowered it to 20ms and it is still running fine. Looks like it was just getting overloaded.
Kalphiter:
Maybe that's one reason why saves don't load too quickly.