Get .RBXM from github
With Wally
also added some test benchmark result (also sorry for the minor typo on test benchmark result where supposed to be warp not wrap.
I agree with this sentiment, why not just update one of the other ones to be more optimized instead of making a new one to deprecate an older one? It makes it harder for developers to quickly switch over to a better system since they’d have to fully change it in their workflow.
update fixed the issues in my bot game , but still my render cant retrieve colours.
besides from the chat bit i think it got confused since there’s a server connected to it, client connected and another client. its created in one client script then accessed by the others server and client how do i control the flow of the event? shall i use the rateLimit?
also i put false in every fire bit in like 5 scripts before firing them (not using reliable events)
i dont get what u mean
####### igrone
just noting for using unreliable (not reliable type) event that can just be dropped it self once it fails, unreliable unlike reliable where its not ordered but there chance it get dropped off and that things on unreliable dont happens to reliable event. like unreliable event good for something like pvp thing or pinging server, and dont use unreliable at all here. for more information about Unreliable Event here.
yeah i know, but i set it to not send unreliable for both chat and gameid events, since it works with unordered orders and it could mess up the timer. ill look into it more since it is a issue with one of my scripts and i might aswell split my client code to a server script since it handles better for all players in the server.
this what it rate limit looks like with Packet profiler plugin. it using default rate limit configuration. you can disable the rate limit by setting interval to 0 or below 1 like this:
local remote1 = Warp.Server("Test", {
maxEntrance = 200, -- this is the default value
interval = 0
})
with maxEntrance 50 and interval 1:
download the playground here:
WarpPlayground.rbxl (100.1 KB)
il try out the playground to learn more about it
well i learned stuff from it and its the same how i initialized it, tried sending messages in that playground it works, but why not tables with 3 elements?, i cant rewrite my render to work with strings since it works well with strings, like i said, does it support tables or no?, if not add support then. and on to the bot game,
client to server doesn’t look like it work, but server to client can, here’s my function in the client script that I created the event from:
local function sendMessage()
local success, response = pcall(function()
local chatInstance = TextBox.Text
ChatEvent:Fire(false,player,chatInstance)
end)
when i run the script it doesnt error and nothing just happens.
it can when i last used remote event i can send the text of a textbox to a server script
Scripter on DevForum try not to upload a network resource challenge (impossible).
If it is what it claims to be, I will probably be switching from BridgeNet2 to this, mostly because of unreliable remote support.
it supposed to support both (tuple and table)
well i rather know more of errors in my code and have safer code then me getting confused whats happening. and some people trying to mess up with the bot
oh ok, if it works with tables, then in your next update could you add logging to you module so i can see whats going thru.
In ClientProcess, I cant imagine the queueInRequest variable is supposed to repeat twice.
e u can remove that one its just a mistaken
add --!native at first line in ur scripts to make it have some better performance.