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

[1.33][SMP] modem_range CVAR doesn't affect anything

Started by foxxx0, 11 July 2012 - 04:43 PM
foxxx0 #1
Posted 11 July 2012 - 06:43 PM
Hey guys,

I switched over to bundled cables but I got a hint now that it might be bug and not me being too stupid.

According to the possibles CVARs in the CC config file I wanted to change to modem range and increase it to a much bigger value that I won't have to use that many repeaters which could affect the SMP server performance. So I changed my config file to this:

mod_ComputerCraft.cfg

diskItemID=4000
computerBlockID=207
modem_range=512
enableAPI_http=0
diskDriveBlockID=208
modem_rangeDuringStorm=512

But it seems that "modem_range" and "modem_rangeDuringStorm" doesn't the affect the wireless modem behavior and they still can't exceed 64 blocks of distance.

Details below.

ComputerCraft Version Information: 1.33 Client / 1.33 Server

Forge Version Information: 3.1.2.90
Forge Mod Loader Version Information: 1.0.0.68

Description of Bug: CVAR modem_range has no effect

Steps to reproduce Bug: Change "modem_range" in mod_ComputerCraft.cfg to a value above 64 (default) and check ingame with two Computers if you can exceed 64 blocks of distance.


Thanks in advance, I hope there might be a solution for this as RP bundled cables are quite annoying and slow.

Greetings,
foxxx0

PS: I'm from Germany so please excuse mistakes in language.
MysticT #2
Posted 11 July 2012 - 06:50 PM
I think the problem is the forge version. There's was bug that makes it not read configs correctly.
Try using the latest recommended.
Cloudy #3
Posted 11 July 2012 - 07:22 PM
Definitely the old forge version.
foxxx0 #4
Posted 11 July 2012 - 08:08 PM
Thanks, a newer version of forge did the trick.

Now I am experiencing massive issues while trying to get the Optifine mod to work, but that has nothing to do with CC at all.


Thanks for your help guys, awesome forum, nice community :)/>/>
Pugz #5
Posted 25 July 2012 - 01:55 PM
Hey all, :)/>/> new to the forums and this is the reason I'm here. Running a Tekkit server myself and I'm finding that the 64/17 block range for a wireless modem in an infinite world a little stingy lol. (even more so with the ideas I have)

I see you have had some luck in sorting your problem by updating Forge? I just recently updated the server to the 3.1.1 update and yes I have indeed changed the
modem_range=500
modem_rangeDuringStorm=500
and still ingame my computers are to far apart to talk to eachother in the rain, :S please help!

The latest version of Forge? I did get the latest Forge from there dev site but didn't really understand the part of where I'm supposed to put in on the server? I didn't want to do anything till I asked for some help/advice, if i were to update the servers Forge would it then stop people joining the server?

Any help would be great and well received :D/>/>
Cloudy #6
Posted 25 July 2012 - 02:34 PM
If the modem range setting doesn't work in tekkit then it is their issue as it should work in both regular and bukkit port - so take it up with them.
Pugz #7
Posted 25 July 2012 - 02:40 PM
I'm guessing your fed-up with hearing about problems technicLancher is causing ComputerCraft? fair enough though, I just hoped it would be a common problem that someone had a possable fix for.
Cloudy #8
Posted 25 July 2012 - 02:47 PM
Well the post stickied at the top of this forum states that bukkit bugs are not our concern - we do not maintain the port ourselves. Also technic do say not to report any bugs to mod authors.

I'm not trying to be mean but this does work in vanilla and the regular bukkit port - so it is really their problem.
Pugz #9
Posted 25 July 2012 - 03:10 PM
That's fine really, I did so much searching to make sure I didn't miss something already posted when in-fact I missed the most important part, so it's really my bad. I'm creating a post on the Tekkit forums now if I find a fix I'll post a link here to stop people replying to this post if they have the same issue.

Again though, my bad!