
Originally Posted by
Syranide
Hmm, that's odd.
I've never encountered it myself, and it is from the function Wire_Link_Clear meaning I have no idea what caused it and it shouldn't be egate2 causing it (although it probably is).
I'll try and see if I can replicate it somehow but I doubt it.
Actually, I just found the cause, if you change an output it gets like that for some reason, but I can't see how the egate2 would cause it. I'll look into it, thanks!
EDIT: Oh I just found it, it was an old fix I made for when one adjusts outputs it would previously not remove the wires, however there was a spellingmistake in the "special" version that egate2 uses (since it supports types). This is fixed in the latest revision.
lol i just figured it out too lol, but yea it happened whenever i changed a wired input or output name and tried to spawn it
ADD: just saw that if you dont place the } at the end of the statement then it displays this error Code:
entities\gmod_wire_expression2\core/init.lua:659: attempt to index field 'readtoken' (a nil value)
instead of missing } at line *** chr *** or something like that
Bookmarks