[Help] aspects: 15: attempt to index ? (a nil value)

  • Please make sure you are posting in the correct place. Server ads go here and modpack bugs go here
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Thraxx

New Member
Jul 29, 2019
9
0
1
So I am using direwolf20's code for his manabeans aspects computer and I don't know why it is giving me this error. I tried setting it up the same, with a peripheral proxy on 52 aspect jars and one on a request pipe but (so it's an exact copy) but I still get this error.
Here is the code for startup and for aspects - http://pastebin.com/JMc6BJiN

I also tried setting up a monitor like DW20 did and it does not work, I would assume it is because the aspects program is not working, but here is the code for it anyway
http://pastebin.com/K8MFb3w6
 

rouge_bare

Well-Known Member
Oct 4, 2014
969
324
79
Code:
peripheral.wrap("LogisticsPipes:Request_0")
This line puzzles me, I think you mean to wrap the side the pipe is on relative to the computer. For instance if the pipe is to the left of the computer/turtle then this needs to be peripheral.wrap("left")
 

Thraxx

New Member
Jul 29, 2019
9
0
1
Code:
peripheral.wrap("LogisticsPipes:Request_0")
This line puzzles me, I think you mean to wrap the side the pipe is on relative to the computer. For instance if the pipe is to the left of the computer/turtle then this needs to be peripheral.wrap("left")
Hmm, doesn't the 15 mean the problem is in line 15? Or am I wrong in that. Also the peripherals are all hooked up with peripheral proxies.
 

Thraxx

New Member
Jul 29, 2019
9
0
1
Also I checked and I don't know what is with the formatting on Pastebin but if the 15 does mean line 15, then line 15 is actually on line 25 of pastebin.
 

lenscas

Over-Achiever
Jul 31, 2013
2,015
1,801
248
pipe.getAvailableItems() returns nill I guess it does this because there are no items available or because the set-up is not exactly the same.
 

rouge_bare

Well-Known Member
Oct 4, 2014
969
324
79
The error point is not necessarily on the same line, it is referencing nil when you are attempting to reference pipe, (on line 15). The error is what I pointed out earlier, you need to wrap to a side, not specifying the pipe. As there is no perpiheral on side "LogisticsPipes:Request_0" it is returning nil there. No error, as the pipe variable can contain nil. But when you try and use the variable, you can't .getAvailbleItems() on nil, hence the error.
EDIT: sorry, I just realized I were well off the mark, misread your original post. I'd double check your request pipe is labelled the same as it is in your code.
 
Last edited:

Thraxx

New Member
Jul 29, 2019
9
0
1
The error point is not necessarily on the same line, it is referencing nil when you are attempting to reference pipe, (on line 15). The error is what I pointed out earlier, you need to wrap to a side, not specifying the pipe. As there is no perpiheral on side "LogisticsPipes:Request_0" it is returning nil there. No error, as the pipe variable can contain nil. But when you try and use the variable, you can't .getAvailbleItems() on nil, hence the error.
EDIT: sorry, I just realized I were well off the mark, misread your original post. I'd double check your request pipe is labelled the same as it is in your code.
How do you find out what it is labelled?
EDIT: I added on nil and it gave error - "bios: 339: [string "aspects"]:15: '=' expected" so I just removed that, idk if you even wanted me to try that but I don't know a whole lot about code so I did it.
 
Last edited:

rouge_bare

Well-Known Member
Oct 4, 2014
969
324
79
The easiest way would be to disconnect then reconnect the request pipe, it should say it's label then.
 

rouge_bare

Well-Known Member
Oct 4, 2014
969
324
79
To be honest, I haven't really played that much with modems. The only thing I can see possibly being wrong is that peripheral.wrap(). Right click the modem attached to the pipe. It should say something along the lines of "Peripheral <name> (dis)connected". The name that it gives you then should be the one that you need to use. I just realized I were a little unclear on my last post, sorry.

If you did disconnect the pipe in this manner be sure to right click the modem again to reconnect it.
 

Thraxx

New Member
Jul 29, 2019
9
0
1
To be honest, I haven't really played that much with modems. The only thing I can see possibly being wrong is that peripheral.wrap(). Right click the modem attached to the pipe. It should say something along the lines of "Peripheral <name> (dis)connected". The name that it gives you then should be the one that you need to use. I just realized I were a little unclear on my last post, sorry.

If you did disconnect the pipe in this manner be sure to right click the modem again to reconnect it.
i would assume the LogisticsPipes:Request_0 would be the proper label though, since it worked perfect for DW20 in his video. It does say "logisticspipes_pipes_basic_logisticstilegenericpipe_0" when I disconnect and reconnect it, but should the LogisticsPipes:Request_0 not work, I mean it does for him. Never the less, I will try changing it to the other label.[DOUBLEPOST=1413046372][/DOUBLEPOST]
i would assume the LogisticsPipes:Request_0 would be the proper label though, since it worked perfect for DW20 in his video. It does say "logisticspipes_pipes_basic_logisticstilegenericpipe_0" when I disconnect and reconnect it, but should the LogisticsPipes:Request_0 not work, I mean it does for him. Never the less, I will try changing it to the other label.
EDIT: Didn't work just returned aspects: 15: attempt to call nil