I tried using this but it just stops my code…
I added some debugging and it stops printing after i require the Warp module from a local script.
How to fix?
1 Like
@Eternity_Devs Is there server-sided rate limiting available? I’m able to easily circumvent the rate limit from the client which means that exploiters can too; or are we expected to use our own implementation?
1.0.12 has middleware feature, u can try that.
2 Likes
Yes, i would like to get the answer to the first question too.
I want to make remotes for each tool respectfully
Nevermind, After reading Warp source code, I understand how it works now.
@scel5525pro2 To your question about unique Remotes.
I’m using this for a gun system, I’m wondering on the gun client, do i need to do Network.client(“Remote”… Player.Name)?
Yes, you need to create an Index (aka Remote) with unique Identifier (aka Name) that is aviable on both Server and Client. Stuff like Warp.Server(GUN_NAME .. "_" .. Player.UserId) should work.
Also you must use :Destroy() on Indexes (aka Remotes) to Disconnect all Connections
However I have noticed that Indexes are not being Garbage Collected and stay in memory even after calling :Destroy()
Ive done remote.create yayadada(“Gun”…Tool.Name…Client.Name)
I don’t know if it is a problem with me but sometimes some Signals are not registered on the client. I have tried different versions yet nothing seems to fix this issue.
Getting this issue too, it’s very annoying
seems like you dont require it on server side first.
Hi, @Eternity_Devs, I have encountered a bug in your module.
This bug never happened before, I tried switching to version 1.0.9 and version 1.0.12 but the error was still persistent.
I run this code in my script (local script) and I print the table t and the result is this:
But when I fire the table and other values to the server and I print the result I get this strange print:
Any help is appreciated thanks!
1 Like
is this always happens or just sometime? and have you also tried v1.0.11?
What’s inside table._items? Is it a mixed table?
If yes, then that’s the issue 
Always happens and no I did not try the v1.0.11, I’m going to try it right now!
1 Like
Nope does not work either on v.1.0.11.
how is the .items table looks like?
This are the array items:
["_items"] = {
[1] = Template --template is an instance (it's made for testing)
}
oh, you cant send instances to mixed table through remote event’s
Ok thanks, now I will think about how to serialize the instance.
1 Like
yeah you can serialize the instance into tables as the data of property/attributes.
You definitely can do that as far as I know…
It’s because of the replication, if the instance is only on the client, it will be nil on the server.
But if it were a player for example, it’ll still exist on the server.