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
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.
Hey, so I’m trying to update some CFrames to the server, and then back to other players for leaning replication and whatnot, except the cframes on the server (gray print), is completely different to the cframes on the client (orange print), does anyone know how to fix this
Hi, I have the same issue:
This issue also persists in Bytenet2. I believe it is caused by multiplying an identity cframe matrix (default for CFrame.new(vec3)) by the rotation serialized within the buffer. The way my library BufferConverter2 does it is by quaternions so I do not experience the same issue, however this issue can be fixed just by doing OrientationCFrame + PosVector3 instead of OrientationCFrame * CFrame.new(PosVector3) (I am not too sure though)
Honestly I don’t know how this hasn’t been caught earlier considering many many people would be using these modules for replication which involves CFrames
I thought this was an issue caused by me using ByteNet incorrectly and not understanding it due to the documentation. Apparently it was just never my fault :;/
What’s this bufferWriter spamming my output?
The cframes i sent to the server came out all wonky, so i went in the code and found that moving this random line up fixed it. not sure why it was below in the first place but maybe this will help someone
honestly just use zap (blink if you’re studio only like me)