This is insane, thanks for making this!
I was looking for this too and just found that you can use
local param = definedNamespace.definedPacket.wait()
and it will return the value which was fired on the client once, didnt test using on server tho since its not within my scope atm
I was able to reproduce this problem by not defining the namespaces on the client. What’s likely the culprit is that you’re sending things to the client before the client can define namespaces. The error is because the packet is nil, so adding this below that line in read will stop the error and drop the event.
if not packet then
break
end
Alternatively (if the event is important), you can wait for a namespace to exist by adding this beneath the while loop:
local packet = ref[buffer.readu8(incomingBuffer, readCursor)]
local tries = 0
while not packet and tries < 5 and game:GetService("RunService"):IsClient() do
tries += 1
packet = ref[buffer.readu8(incomingBuffer, readCursor)]
if not packet then
task.wait(1)
end
end
if not packet then
return warn("[ByteNet] A packet was dropped - no packet/namespace defined")
end
I doubt that this will be fixed for a while.
1 Like
Good remark, that is in fact possible.
I already opted for the first solution until now (drop the packet).
1 Like
Hey!
Does anyone know if it’s possible to make a ByteNet packet subscribable? (Equivalent to RemoteFunctions)
If you’re looking for a RemoteFunction implementation for ByteNet I recommend @Lightning_Game27’s fork called ByteNet Max : )
2 Likes
How do you send instances using uniqueID’s?
Hi
Okay, my previous response wasn’t great because I thought you had the same issue as me but I made an adjustment to the module to allow for packet disconnections at runtime. Here’s the process below (also if anyone has any improvements to the code I added please let me know):
src/packets/packet.luau
I added a return in the .listen() function to get the index of the listener in my main script.
Next I added a new .disconnect() function which intakes the listenerIndex, and removes it from the table of listeners.
function exported.listen(callback)
table.insert(listeners, callback)
return callback
end
function exported.disconnect(callback)
for i, listener in pairs(listeners) do
if listener == callback then
table.remove(listeners, i)
break
end
end
end
Here’s how it looks in my script:
script.lua
local packet = require(path.to.packet)
local connection = packet.packetName.listen(function(data)
...code here...
end)
-- When you're ready to disconnect
packet.packetName.disconnect(connection)
connection = nil
I tested this in my code and it seems to work as expected, hope this helps anyone who’s had trouble with this, hopefully ffrostfall adds this natively soon!
EDIT: I noticed an issue with this where if you removed a certain listener say index 2, but the total listeners are say 5, this would push back the listener table indices which would make the other listeners defined after index 2 invalid. Instead I’m just returning the callback function now into the variable so that way when you disconnect it checks the for the function rather than index tho there’s probably a better way to do this, but I’m not entirely sure and dont have the time to figure it out rn, I updated the scripts with the fix…
2 Likes
anybody know the difference between this and red?
Red doesn’t use buffers and is deprecated. A better question is a difference between ByteNet and Zap.
Generally, Zap is easier to use and ByteNet has slightly better performance. But others might it see differently with ease of use.
1 Like
Hello! Im looking through the documentation and I’m a bit confused as to what define Namespace actually does. What does passing the string value actually do?
local ReplicatedStorage = game:GetService("ReplicatedStorage")
local ByteNet = require(ReplicatedStorage.ByteNet)
return ByteNet.defineNamespace("messaging", function() -- what does the string "messaging" do?
return {
printSomething = ByteNet.definePacket({
-- This value field is very important!
reliabilityType = 'unreliable',
value = ByteNet.struct({
message = ByteNet.string,
})
}),
Other = ByteNet.definePacket({
reliabilityType = 'reliable',
value = ByteNet.bool,
})
}
end)
Namespaces allow different groups of packets, allowing ByteNet to organise them. This means u could have the same ‘printSomething’ packet under “messaging” and “sending” namespace for example. As ffrostfall himself says: “Because the ordering needs to be consistent and deterministic, and this ordering is relied on to sync client/server structs.”
1 Like
Why isn’t there a .Disconnect/destroy function
ByteNet uses a singular remote event. There’s no point disconnecting one function.
the documentary didn’t help and I’m still confused:
- where can you possibly find the “path to packets”? the documentary shrugs it off like you’re supposed to telepathically know its directory. the examples are constantly telling me about “path.to.packet”, but shouldn’t it be obvious that the desired packet is somewhere inside the bytenet module?
^ (as I was writing this, turns out you need to use a ModuleScript which lets you access the packets, but the only reason I knew about this is because of someone else’s screenshot featuring the OLD documentary)
- if I wish for the packet to have no other value besides the player that requested for it to fire, how can I set it up?
3 Likes
is it worth it to understand using a network library while only having 6 months of roblox studio experience? lowkey i don’t understand anything in the documentation 
honestly i don’t think it’s you, i think the documentation just sucks
this is a common sentiment when people first learn bytenet
1 Like
i honestly think i’m stupid bro, i like learning by seeing examples of code rather than just reading and the documentation didn’t help me at all
It’s definitely because the documentation is straight up dog water just like everyone has been saying since the beginning. I just randomly decided to stay up at midnight like 2 months ago I think and I forced myself to learn ByteNet and I was able to.
8 Likes
