For some reason the cybernetics are said to be disconnected even though my glitter net hub is fully opperational. the hub says its only connecting to one person how do i change that

Sounds like a conflict. Please upload your log with HugsLib so I can try to reproduce it.

so what happened to this? I have the same problem

I never received a log so I was unable to troubleshoot it. If you send me your hugslib log I can take a look at it.

Having a problem where the SootheAura mood buff will toggle every 2-3 seconds. The part itself will stay connected to the Glitternet while the mood toggles. Turning off the Glitternet and caravanning the pawn has no effect after they reconnect.

https://gist.github.com/1e159e5dfbd3202061da0a2e154da3ae
Also here is the HugsLib log since my guess is you need it

@kpunk21 I'm having trouble understanding exactly what the behavior you're describing is. Does the mood buff get removed than added again every couple seconds or something else?

That is what happens, yes.

@kpunk21 This is some kind of conflict. I don't really have a better way to find which mod is causing the conflict than guessing, since this isn't a Harmony-type conflict, and since you're running with 206 mods that takes an inordinately long amount of time. Unless you can determine which mod is the one that's conflicting with CyberNet I won't be able to fix this.

i noticed that the cybernet wireless hubs always work whether is toggled on or off. i suspect that this isn't intentional as i also tried it with the glitternet processors and those turned on and off properly.. i also get no errors

@arendjvr I forgot to check if access points were operable when determining the total bandwidth of a network. This also affected access points that were broken down or unpowered. I've put out an update that fixes this.

great work. now i can torture my prisoners and slaves when they misbehave

So i have been having trouble with the wireless access points. It might be an incompatability issue with a different mod, but as far as I can tell it is something in the mod itself. My wireless access points are not connecting to the mainframe. They say that they are connected, but do not lend any of their bandwidth to the mainframe. In addition, if i install a Cybernet implant or body part it will immediately go online and say that it is throttled, but if I then uninstall the wireless access points they all become disconnected even though they never were using any actual bandwidth. If i then reinstall said access points or build new ones, any already implanted body parts will remain disconnected although their bandwidth will suddenly start to register on the access points which in turn still do not lend any of their bandwidth to the network's mainframe. I tried moving them around (always making sure they had power and cyber connection) with no change. To further complicate the matter, even I then went ahead and implanted more parts into my pawns, the new parts would show as being throttled, but the old parts would remain disconnected. Something is not registering bandwidth. Glitternet itself is working great without any issues or bugs showing up, so it is something that happens when I start using Cybernet. Hope this is clear.

@starkleshjsservices Please give me your HugsLib log. I've been trying to corner this issue for months but no one has ever given me a log with it. I'm fairly certain it's a conflict since I've never been able to replicate it in my GlitterNet and CyberNet test setup.

There was once an issue with the symptoms you describe when I was developing the mod, but there I implemented a couple of different checks for part registration which fixed it. However, these checks rely on a vanilla comp tick, and I once fixed a conflict in GlitterNet that caused my vanilla tickers to never occur. The solution there was to use HugsLib tickers, but because of architectural differences I can't use that solution in CyberNet.

Anyway, if you can give me a log and I'm able to find the mod causing the conflict I might finally be able to put this issue to rest.

@ Galo Itaipava Cigarro  I've put out a patch that fixes the first issue. Could you check if the second issue persists? If it does, please upload a HugsLib log so I can try to debug it.