This is a read-only snapshot of the ComputerCraft forums, taken in April 2020.
CCJJSax's profile picture

Can anyone confirm this is a bug with CC?

Started by CCJJSax, 27 November 2013 - 08:26 PM
CCJJSax #1
Posted 27 November 2013 - 09:26 PM
First off I know there is a bug section. I think this is probably better since I can't confirm 100% it's computercraft.

I'm on FTB Unleashed with gregtech from FTB Unhinged.

Here is a link with a list of mods. (it's the FTB Wiki)


The issue is rather common on this server I'm playing on, and 3 turtles have had this issue (or at least they seems the same). Every now and again previously working turtles stop responding. We can't even Ctrl + t or r the program. The startup program is in a spoiler below, but I know for a fact that it doesn't have an os.pullEventRaw() in there. none of these turtles did. Even when breaking the turtle and restarting the server the problem persisted. One time (maybe 2) the turtle came up with an error. this time it was "startup:19: vm error: java.lang.ArrayIndexoutOfBoundsException: 13" I have the program in a spoiler below.

Whenever we interact with the turtle, the server cmd goes crazy with errors involving CC. (pic below)

startup for one of the turtles
SpoilerThis had been working exactly as intended.
This particular turtle had an XP upgrade (misc peripherals) but not all of them did.


xp = peripheral.wrap("right")
xp.setAutoCollect(true)

function clear()
  term.clear()
  term.setCursorPos(1, 1)
end

function clearInv()
  while turtle.suck() do
  end
  for i = 1, 16 do
	if turtle.getItemCount(i) > 0 then
	  turtle.select(i)
	  turtle.dropUp(turtle.getItemCount(i))
	end
  end
  turtle.select(1)
end

clearInv()
timer = os.startTimer(1)

while true do
  print("I have "..xp.getLevels().." levels to spend!")
  for i = 1, 20 do
	while turtle.attack() do
	end
	sleep(.5)
  end
  clearInv()
  if turtle.getItemCount(1) > 0 then
	error("Consult JJSax reguarding this issue. \n Item in inventory at wrong time.")
  end  
  clear()
  turtle.select(1)
  while rs.getInput("left") == true do
	print("Enchanting mode active.  I have "..xp.getLevels().." xp points")
	print("Put the Item into slot 1")
	while turtle.getItemCount(1) == 0 do
	  sleep(1)
	end
	xp.enchant(30)
	print("Please take your newly enchanted item")
	while turtle.getItemCount(1) > 0 do
	  sleep(1)
	end
	clear()
	print("Please turn off lever")
	os.pullEvent("redstone")
	clear()
  end
end




cmd log
Spoiler[attachment=1403:Untitled.png]

The owner of the server didn't add any resource packs or mod the base CC APIs. fyi
Edited on 27 November 2013 - 10:57 PM
theoriginalbit #2
Posted 27 November 2013 - 10:06 PM
I vaguely remember an identical problem on a server that I used to join. We discovered that MiscBugs was the cause. Not sure if it is in your case too, but it might be worth a shot.
Edited on 27 November 2013 - 09:06 PM
Lyqyd #3
Posted 27 November 2013 - 10:07 PM
What's the server's tickrate like?
CCJJSax #4
Posted 27 November 2013 - 10:16 PM
I vaguely remember an identical problem on a server that I used to join. We discovered that MiscBugs was the cause. Not sure if it is in your case too, but it might be worth a shot.

MiscBugs? Are you refering to MiscPeripherals?

What's the server's tickrate like?

Overall: 20.00 TPS/7.56MS (100%)

Overworld[0]: 20.00 TPS/8.98MS (100%)
Nether [-1]: 20.00 TPS/0.20MS (100%)

pretty quick
distantcam #5
Posted 27 November 2013 - 10:20 PM
I've noticed that with CC if you manage to break the mod itself (as in trigger a bug in the CC code, not the Lua BIOS) then all computers break.

So it may be some other computer that is nuking CC and causing all computers to break.
CCJJSax #6
Posted 27 November 2013 - 11:39 PM
I've noticed that with CC if you manage to break the mod itself (as in trigger a bug in the CC code, not the Lua BIOS) then all computers break.

So it may be some other computer that is nuking CC and causing all computers to break.

Possibly, but I have one advanced computer that is working. (there I go jinxing myself ;)/> ). So I did a quick os.getComputerID() and found that there are only 6, one got blown up, the other we burned once it had the issue. Ya, know. It was a nice proper burial.