Posted 17 December 2014 - 03:39 AM
VERSION:
1.65 for mc 1.7.10
DESCRIPTION:
When a computer is running a script, if it is moved by a frame machine of some sort, it will restart and loose it's progress in the script, but not shutdown however, nor print any errors in the console.
EXPECTED RESULT:
The computer should continue the script as normal, possibly pausing while the computer is mobile and resuming when back in the world. This worked perfectly in the days of Redpower2.
REPRODUCTION STEPS:
Funkylocomotion, CC and a mod to power the frame machine.
> a bit of frame, something to move it and a computer attached
> code a script (not startup) to do something in a loop, eg; " while true do print("test") end "
> run said script
> move frame at least a block in any direction, moving the computer with it
> observe the computer is nolonger running the script
I have no idea really what was changed in CC's backend to develop this issue, and/or whether Redpower2 frames were doing some other trickery to trick the VM to keep the computer running, if there's some extra calls required for correct functionality then list them and I'll forward to the FunkyLocomotion dev.
1.65 for mc 1.7.10
DESCRIPTION:
When a computer is running a script, if it is moved by a frame machine of some sort, it will restart and loose it's progress in the script, but not shutdown however, nor print any errors in the console.
EXPECTED RESULT:
The computer should continue the script as normal, possibly pausing while the computer is mobile and resuming when back in the world. This worked perfectly in the days of Redpower2.
REPRODUCTION STEPS:
Funkylocomotion, CC and a mod to power the frame machine.
> a bit of frame, something to move it and a computer attached
> code a script (not startup) to do something in a loop, eg; " while true do print("test") end "
> run said script
> move frame at least a block in any direction, moving the computer with it
> observe the computer is nolonger running the script
I have no idea really what was changed in CC's backend to develop this issue, and/or whether Redpower2 frames were doing some other trickery to trick the VM to keep the computer running, if there's some extra calls required for correct functionality then list them and I'll forward to the FunkyLocomotion dev.