The documentation can be found here.
A system built to help combat input latency when using physics on Roblox. This system is built using the principles described by TheNexusAvenger in this article on his website.
- Support for multiple items inside of the Buffer
- Security features that help protect against abuse of the system
This module creates a Folder that stores all items added to the Buffer via the server, such as projectiles. When an item is added to the buffer it will have its NetworkOwnership assigned to whichever player is given ownership over the buffer (e.g the player who is holding a weapon).
Buffered items are held suspended far away from the play area. When the client needs to create a new projectile, such as when the player activates a weapon, instead of creating a new Instance we instead pull an existing one from the Buffer. Since the Instance already exists and we have NetworkOwnership over it, we can instantly start controlling the physics of the item.
As nice as the system sounds, it does come with some clear caveats that may influence if you decide to use this system over something else:
- This method is not supported natively by the Roblox Engine. This comes with some weird downsides, such as how buffered items need to be stored as descendants of the Workspace, or how buffered items cannot be Anchored until they are removed from the buffer.
- The client has control over the physics of items in the buffer. This comes with the usual security concerns of giving the client NetworkOwnership over parts.
- Grab the latest release from the releases tab on GitHub.
- Insert the module somewhere accessible on the server/client, such as inside of
ReplicatedStorage. - Review the Configuration module under
BufferModule.Configurationand tweak it to your liking.
See the documentation to find out how to implmenet the system in your own experiences. An example place can be found in the releases tab.
