So, updating ComputerCraft messes with scripts?

[MortalDanger]

I admit to knowing nothing about it, but I was using Lolmer's big reactors script:
http://pastebin.com/fguScPBQ

Error: 273: attempt to call nil

Anyone mind taking a look at it? It's a great program.

 

[rhn]

I admit to knowing nothing about it, but I was using Lolmer's big reactors script:
http://pastebin.com/fguScPBQ

Error: 273: attempt to call nil

Anyone mind taking a look at it? It's a great program.

It is caused by a change in the CC API. The term.restore was removed. You can fix it most places by replacing it with term.native, but you really should go get the new version of Lolmers script instead:
https://github.com/sandalle/minecraft_bigreactor_control
It have been massively updated since the version you have to now work with all CC versions, work properly with turbines and much more.

 

[MortalDanger]

That's the same one, is it not?

 

[rhn]

That's the same one, is it not?

Ahh so it is. Assumed you were talking about the 1.58 ->1.63 CC upgrade issue.
What version of CC did you update to?

 

[MortalDanger]

I updated to CC 1.73. When I logged in the monitor was bonkered, and I tried redoing everything to no avail - so I assumed it was a CC API update that broke it.

 

[rhn]

I updated to CC 1.73. When I logged in the monitor was bonkered, and I tried redoing everything to no avail - so I assumed it was a CC API update that broke it.

If you look at the part that caused the problem you would see why:

local function termRestore()
  local ccVersion = nil
  ccVersion = os.version()
        if ccVersion == "CraftOS 1.6" then
                term.native()
        elseif ccVersion == "CraftOS 1.5" then
                term.restore()
        else -- Default to older term.restore
                printLog("Unsupported CraftOS found. Reported version is \""..ccVersion.."\".")
                term.restore()
        end -- if ccVersion
end -- function termRestore()

Simple fix would be to change the "Default to older" part to a term.native() I suppose and remove the "printLog....." that is causing problems.

 

[MortalDanger]

That'll do it. Thank ye.

 

[lolmer]

I updated to CC 1.73. When I logged in the monitor was bonkered, and I tried redoing everything to no avail - so I assumed it was a CC API update that broke it.

Just FYI, Lolmer's EZ-Nuke as of 0.3.16 supports ComputerCraft 1.7x.

If you look at the part that caused the problem you would see why:

local function termRestore()
  local ccVersion = nil
  ccVersion = os.version()
        if ccVersion == "CraftOS 1.6" then
                term.native()
        elseif ccVersion == "CraftOS 1.5" then
                term.restore()
        else -- Default to older term.restore
                printLog("Unsupported CraftOS found. Reported version is \""..ccVersion.."\".")
                term.restore()
        end -- if ccVersion
end -- function termRestore()

Simple fix would be to change the "Default to older" part to a term.native() I suppose and remove the "printLog....." that is causing problems.

Yeah, I had a typo in there, sorry. Also fixed in 0.3.16 above.

 

[rhn]

Just FYI, Lolmer's EZ-Nuke as of 0.3.16 supports ComputerCraft 1.7x.



Yeah, I had a typo in there, sorry. Also fixed in 0.3.16 above.

Excellent.
While you are here, would it be possible to request an option to alter the passive reactors temperature regulation range on screen? The size of the range could be fixed, but an option to increase/decrease the mean of the range would be awesome.
Sometimes you play a pack/in a situation where fuel is not an issue and you don't care that much about efficiency and just want power, other times you want as much power as you can out of your precious fuel. Would be nice not having to deal with having modified copies for each situation

 

[lolmer]

Excellent.
While you are here, would it be possible to request an option to alter the passive reactors temperature regulation range on screen? The size of the range could be fixed, but an option to increase/decrease the mean of the range would be awesome.
Sometimes you play a pack/in a situation where fuel is not an issue and you don't care that much about efficiency and just want power, other times you want as much power as you can out of your precious fuel. Would be nice not having to deal with having modified copies for each situation

Sure thing, file a feature request so that I can track it. I'd just have to find a spot to put it on the UI, it's getting quite busy, especially with the changes in 0.3.17.

EDIT: Also note that you can modify the reactor configurations (with the program stopped, or it'll overwrite your changes on the next save cycle ) in BigReactors-Reactor_ID# via reactorMaxTemp=- and reactorMinTemp=. The values saved on the first run are just defaults and, after that, they are read from these files and obeyed by the script to the best of its ability.