If this is expected behaviour please treat me gently, but I've come here as I'd heard OC persists robot state over chunk unload/load and server quits / restarts.
I tried building a robot in Creative single player and running the following from the Lua prompt:
for i=1,1000 do robot.up() robot.down() end
I then tried various things to try to 'break' the persistence, and sure enough it works beautifully if I quit to title and resume.
But if I quit the Minecraft client entirely (CMD-Q on Mac) without dropping to the title screen first then I've seen the robot 'slip' upwards one block (but continue running), and I've also seen it throw errors or reboot on repeated attempts.
I've included what I hope is relevant information below, and I'm happy to file a bug with more if its warranted. However if this is expected (and I should avoid quitting - other than from the title screen) then please let me know.
Minecraft version: 1.6.4
Launcher info:
[00:31:40 INFO]: Minecraft Launcher 1.5 (through bootstrap 5) started on osx...
[00:31:40 INFO]: Current time is Jul 29, 2014 12:31:40 AM
[00:31:40 INFO]: System.getProperty('os.name') == 'Mac OS X'
[00:31:40 INFO]: System.getProperty('os.version') == '10.9.4'
[00:31:40 INFO]: System.getProperty('os.arch') == 'x86_64'
[00:31:40 INFO]: System.getProperty('java.version') == '1.6.0_65'
[00:31:40 INFO]: System.getProperty('java.vendor') == 'Apple Inc.'
[00:31:40 INFO]: System.getProperty('sun.arch.data.model') == '64'
[00:31:41 INFO]: Loaded 6 profile(s); selected 'OC Java 1.7 for 1.6.4 Forge'
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Hi folks
(Complete noob warning)
If this is expected behaviour please treat me gently, but I've come here as I'd heard OC persists robot state over chunk unload/load and server quits / restarts.
I tried building a robot in Creative single player and running the following from the Lua prompt:
I then tried various things to try to 'break' the persistence, and sure enough it works beautifully if I quit to title and resume.
But if I quit the Minecraft client entirely (CMD-Q on Mac) without dropping to the title screen first then I've seen the robot 'slip' upwards one block (but continue running), and I've also seen it throw errors or reboot on repeated attempts.
I've included what I hope is relevant information below, and I'm happy to file a bug with more if its warranted. However if this is expected (and I should avoid quitting - other than from the title screen) then please let me know.
Minecraft version: 1.6.4
Java Settings:
Mods
Link to post
Share on other sites