JPipes

trying to change the /p key to /j i did manage to get it changed before but for some reason it wont work this time

 

Line 368

Code:

[ChatCommand("p")]

change the p to j

 

already done that still wont work just says unknown command let me resave and reload again just to be sure/. by the way with the perms do i need to grant group name of perm


for some reason it didnt want to save it the first few times lol its working on j now for me

 

I'm working on proper config option for it now.

 

TheGreatJ updated JPipes with a new update entry:

0.5.2

 

Version 0.5.2, I have a player trying to install new Jpipes, and sometimes (not always) when he tries to upgrade or hit it with a hammer to change settings, he gets Kicked: Packet Flooding: Client Command. Place, upgrade, hit with hammer, kick.

 

Change "drawflowarrows" to false in the Config. Then do "reload JPipes" in the server console.
Let me know if that fixes it.

 

Yep, seems to have worked, I'll let you know if it happens again. Thanks!

 

Getting same thing but if draw flow arrows is false then issue no longer happens.

 

try and set your setting like this and it will stop any kicks this is for the default players i found it was to do with the upgrade perm when they go to upgrade there pipes it would kick with either packflood or no kick message so this fixed it for me so the perms would be if you going from how i set my perms up for the default group

grant group default jpipes.level.defaultpipe

grant group default jpipes.level.uplimitlevel

grant group default jpipes.level.pipelimitdefault

Code:

"
"permlevels": {
  "defaultpipe":{
  "pipelimit":20             <------------ sets there pipe length
  },
  "uplimitlevel":{
  "upgradelimit":4          <------- This is to let them upgrade to stone, wood, metal, hq
  },
  "pipelimitdefault":{
  "pipelimit":-1,
  "upgradelimit":4         <------- This is to let them upgrade to stone, wood, metal, hq
  },

 

The Problem:
The flow arrows are very clunky due to the limitations of server-side scripting. They are drawn line by line by sending the "ddraw.line" command to the client every 3 seconds when they have the hammer equipped. The command for each line with all of the parameters looks like this

Code:

""ddraw.line" "3" "0.2,0.4,1,1" "-290.633,31.862,-746.757" "-289.248,32.902,-746.566""

Each command is, on average, 86 characters long.
So let's do some math to demonstrate how inefficient this is:
one arrow on two sides = 1 cmd * 4 lines = 4 commands (344 characters)
"Armored" level pipe = 4 cmds * 5 arrows = 20 commands (1,720 characters)
"Armored" level pipe; 5 segments long = 20 cmds * 5 segments = 100 commands (8,600 characters)
20 "Armored" level pipes; each 5 segments long = 100 cmds * 20 pipes = 2,000 commands (172,000 characters)

The packetflooding kick is triggered when a player is sending/receiving too much data at once to prevent from DDoS-like attacks.
Which is why you get kicked while connecting to the server or upgrading a pipe.

TL;DR
The server kicks you when too many arrows are being sent to the client.
This has already been sort-of fixed for the next update where only one arrow is drawn for all upgrade levels and I decreased the render distance.

 

...And now the Rust update broke the arrows...

 

TheGreatJ updated JPipes with a new update entry:

0.5.3

 

My version 0.5.2 works fine.

 

I just wanted to properly disable them so that the server isn't still sending the "ddraw.line" commands and causing packet flooding when it's not even showing up for the client.

 

Why can one of my pipes send only one thing?

 

What is it connected to? Pipes auto-filter items based on the container receiving them (Ex. furnace only receives fuel or "smelt-able" items). Or it's set to single-stack.

 

It seems that JPipes.cs conflict with GatherControl.cs and there is a mess.

 

What is the mess? Is GatherControl not letting to items be transfered properly?

 

I do not have these plugins conflicting (jPipes.cs + GatherControl.cs). All is well.