Warp/src
manee_too 5e972a7b9c
Changing Warp from a regular to a strict table. Adding the ability to use Client and Server without calling fn(); (Like Buffer)
Why Strict Table instead Regular?
- Catching early syntax errors
- Preventing changes/replacements of keys in the table
- Better Error handling with link to Documentation

Why `metatable` instead `fn()` for `Server` and `Client`?
- Flexibility (now you can use ".Client" and ".Client()" without losing typing)
-  More convenient use - for me personally, it will be more convenient to use one API retrieval interface (including for Warp), as Buffer is currently retrieved directly, but Client and Server - not.

Also, I Fixed Type Error for line 6 (RunService get) and added some comments
2026-05-07 12:14:08 +07:00
..
Client Fixed Type Annotation for Client.Connect 2026-05-04 13:06:58 +07:00
Replication chore: fix client & server processing for invoke 2026-04-22 08:41:14 +07:00
Server chore: fix lint error for studio editor 2026-04-22 08:50:59 +07:00
Util feat: add float32 precision option for vector2 & vector3 type 2026-05-04 08:15:52 +07:00
init.luau Changing Warp from a regular to a strict table. Adding the ability to use Client and Server without calling fn(); (Like Buffer) 2026-05-07 12:14:08 +07:00