Could you please give some context to why my take is so bad instead of just giving a random dry response?
My point still stands, donât rely on ânetworkingâ modules, specifically this one, since itâs fundamentally broken and iâve reported a issue twice and still wasnât fixed. Now itâs been supposedly abandoned and no longer maintained by being archived, very common with these modules infact.
try use older version without buffer and get the patched memory leak in ServerProcess.luau
this project is archived.
Players.PlayerRemoving:Connect(function(player: Player)
if not player then return end
if queueOut[player] then
queueOut[player] = nil
end
for _, map in { serverQueue, unreliableServerQueue, serverRequestQueue } do
for Identifier: string in map do
map[Identifier][player] = nil
end
end
for i=1,2 do
for Identifier: string in queueInRequest[i] do
if queueInRequest[i][Identifier][player] then
queueInRequest[i][Identifier][player] = nil
end
end
for Identifier: string in queueOutRequest[i] do
if queueOutRequest[i][Identifier][player] then
queueOutRequest[i][Identifier][player] = nil
end
end
end
end)
Anytime I fire a reliable event from the client to the server without having a listener on the moment of fire, it throws an error. The two solutions I have are either using unreliable event which isnât suitable or restructuring the scripts for either a permanent server listener to the events or a confirmation of the presence of a listener before firing. Is there a way to simply fire a reliable event without needing a listener on the server side?
no, you cant. and why would u have to fires the event if on the server side dont listen the event connection? i have also heard about version 1.0.13^ is buggy on the dynamic serialization (buffer), so i would recommended you to use the older version instead.
I have a task completion system and the completion of tasks is handled by firing events from the client.
Ex: Open drawer task
Anytime the client opens a drawer, it will send a task completion event to the server. If the âOpen drawerâ task is active, it will listen to the âOpen drawerâ completion event from the client. If the task is inactive, there will be no listeners to the completion and thatâs where the error happens.