[CC 1.6][SSP] multishell:3: attempt to call nil

Description of Bug:
I cannot use any advanced computer, in any world.
Loading up a computer, it comes up with:



The computer then immediately shuts down.

Steps to Reproduce Bug:

1. Place an advanced computer.
2. Load up it's GUI.

That's the line that calls term.current. Have you done anything to alter the term API, or are you attempting to use multishell in an older version of ComputerCraft?

Lyqyd, on 02 April 2014 - 01:34 AM said:

That's the line that calls term.current. Have you done anything to alter the term API, or are you attempting to use multishell in an older version of ComputerCraft?

Nope, just using bog standard stuff from ComputerCraft 1.6.1. No changes, no older versions. Nothing. :wacko:/>

Didn't someone post a (very short) video of this issue a few days ago? Can't seem to find it now.

Bomb Bloke, on 02 April 2014 - 02:29 AM said:

Didn't someone post a (very short) video of this issue a few days ago? Can't seem to find it now.

On YouTube? I'll go search for it now.

Here we go.

Bomb Bloke, on 02 April 2014 - 07:39 AM said:

Here we go.

Yes, that is exactly what's happening.

To be clear, 1.6, or 1.61?

What versions of MineCraft and Forge? Numbers, please, "latest" isn't much use.

Are any other mods installed?

If you place a startup script on a disk, and set that up in a drive next to an advanced computer, does the script run?

If you go up to a regular computer, and type into the CraftOS prompt:

lua
term.current

… what does it say?

I thought perhaps that this might be the "new error" for those who extract the CC archive, but surprisingly, on testing that I found no issues - guess that'll please all those people wanting to edit ROM without having to restart the whole game each time.

I'm using ComputerCraft 1.61.
Minecraft 1.6.4 and was previously using Forge 9.11.1.933, using the current forge 9.11.1.965 made no difference.
No other mods are installed, not even peripheral mods.
A startup script on a disk did nothing and term.current returns nil.

joshmanisdabomb, on 02 April 2014 - 05:33 PM said:

I'm using ComputerCraft 1.61.
Minecraft 1.6.4 and was previously using Forge 9.11.1.933, using the current forge 9.11.1.965 made no difference.
No other mods are installed, not even peripheral mods.
A startup script on a disk did nothing and term.current returns nil.

Reinstall CC. If it persists, try a fresh install.

Apemanzilla, on 02 April 2014 - 06:47 PM said:

joshmanisdabomb, on 02 April 2014 - 05:33 PM said:

I'm using ComputerCraft 1.61.
Minecraft 1.6.4 and was previously using Forge 9.11.1.933, using the current forge 9.11.1.965 made no difference.
No other mods are installed, not even peripheral mods.
A startup script on a disk did nothing and term.current returns nil.

Reinstall CC. If it persists, try a fresh install.

Isolating a version of Minecraft in it's own .minecraft folder fixed the problem.
I'll try to use ComputerCraft like this from now on, unless someone can point me in the right direction as to why it won't work in the standard .minecraft folder.
Thank you guys so much for the help. :)/>

Beats me, I've got it working fine at the default location (inside my user folder).

Assumingn you've still got access to your buggy install, what about term.restore? Does that also give nil, same as term.current?

Bomb Bloke, on 03 April 2014 - 01:50 PM said:

Beats me, I've got it working fine at the default location (inside my user folder).

Assumingn you've still got access to your buggy install, what about term.restore? Does that also give nil, same as term.current?

He can't really test it if it crashes every time he boots up the computer XD

This is likely caused by a botched install. You have some old lua files hanging around in either a resource pack or extracted, and they're overwriting the ones in the mod. closing