[solved(except not really...)]cc[1.5] redpower bundle cable not working for rednet?

So does redpower bundled cable not work for rednet communication anymore?
Am I out of the loop here or something? I remember it working on 1.3, but now I try "rednet.open(side)"
and it tells me "No modem on left side"
Dafuq?
There is so a "modem" on the left side!

and before you ask me if I'm dyslexic or something…


As you can see in the background, bundled cable

Yes. They removed that function because it was obsolete and unneeded.

I don't consider it obsolete…why..Why did they get rid of it? Why no just stop updating it? Wouldn't that take MORE effort? ARGH… Should have just considered it deprecated…jerks…

They are adding their own cables, bro. You shouldn't call the devs of the mod you are playing jerks for removing a feature.

Sammich Lord, on 12 February 2013 - 02:00 PM said:

They are adding their own cables, bro. You shouldn't call the devs of the mod you are playing jerks for removing a feature.

Quite obviously I wasn't being serious..unless you actually take "jerk" as some form of viable insult…lol…

However, I gotta say, I can't wait for the cables they bring us. Hope they're just as useful as the bundled cables though…

Copy the rednet API from 1.481 onto your computer, load it, and run it. Then you'll have bundled cable support.

It was removed due to upcomming cables and the fact that it used an extra corutine on every computer. And LuaJ for some random reason makes a new thread for every coruitine.

Cruor, on 20 February 2013 - 04:10 PM said:

It was removed due to upcomming cables and the fact that it used an extra corutine on every computer. And LuaJ for some random reason makes a new thread for every coruitine.

Doesn't 1.5 use an extra coroutine just to translate modem_message events into rednet_message events?

yea, its the new replacement for rednet.run

immibis, on 20 February 2013 - 04:41 PM said:

Cruor, on 20 February 2013 - 04:10 PM said:

It was removed due to upcomming cables and the fact that it used an extra corutine on every computer. And LuaJ for some random reason makes a new thread for every coruitine.

Doesn't 1.5 use an extra coroutine just to translate modem_message events into rednet_message events?

I have no idea :P/> might aswell be in the same corutine that rednet runs in? :P/>

immibis, on 20 February 2013 - 04:41 PM said:

Cruor, on 20 February 2013 - 04:10 PM said:

It was removed due to upcomming cables and the fact that it used an extra corutine on every computer. And LuaJ for some random reason makes a new thread for every coruitine.

Doesn't 1.5 use an extra coroutine just to translate modem_message events into rednet_message events?

Yeah, although to be honest I'd rather change that so we throw two events from the modem - and I'll speak to dan about that.

Cloudy, on 21 February 2013 - 12:28 AM said:

immibis, on 20 February 2013 - 04:41 PM said:

Cruor, on 20 February 2013 - 04:10 PM said:

It was removed due to upcomming cables and the fact that it used an extra corutine on every computer. And LuaJ for some random reason makes a new thread for every coruitine.

Doesn't 1.5 use an extra coroutine just to translate modem_message events into rednet_message events?

Yeah, although to be honest I'd rather change that so we throw two events from the modem - and I'll speak to dan about that.

I personaly think that you should only get rednet_message events if you have a modem opened via rednet api, but that might just be me :P/> that sounds logical to me atleast XD

You only get modem_messages when you have a modem opened anyway… rednet_message is only there for backwards compatibility.

You only get modem_message if you receive a message on a channel you've previously opened. You only get rednet_message if you've called rednet.open().

Makes sense! So basically, exactly what Cruor said it'd make sense if it happened :P/>