LB Connection v2.3.0-beta - a module that offers an alternative to RemoteEvent, RemoteFunction, BindableEvent, and BindableFunction in Roblox Studio

v2.0.1-beta

  • Remove redundant type
  • Fixed packing byte string to binary string issue
  • v2.0.1-beta is now compatible with Rojo 7
  • Re-edit the description of the post

; are not needed in luau or strictly typed format. Your waste inlike ~0.1s each ;

Indeed, a semicolon is not needed to mark the end of a statement in Luau. Adding semicolons is just my coding style and wonā€™t affect the performance and architecture. I donā€™t see it as a disadvantage.

No, its just useless i mean your waste like your time not the performance

Well, itā€™s kinda become my habit, so it doesnā€™t actually waste my time lol

Uhh so you use a require instead of instances

Very nice release, hope you continue making/supporting this.

1 Like

This is quite a nice update. I still donā€™t have any issues with this. Good job on this!

1 Like
  • Added tips section in the description

Thank you so much. I will continue to improve and optimize the module.

Thank you! Glad to hear that there are no issues with the module at all. If you have encountered any issues, feel free to leave a comment here or report the issues in the GitHub repository.

Iā€™m having a problem when using Remote Function

It prints though idk why its not working
Server

local OpenEggFunction = LBConnection.RemoteFunction("OpenEgg", {TimeOut = 3, RateLimit = 60, RateLimitTime = 3})


OpenEggFunction.InvokeCallBack = function(Player, EggName, Action)
	print(Player, EggName, Action)
	return EggHandler.OpenEgg(Player, EggName, Action)
end

Client

local OpenEggFunction = LBConnection.RemoteFunction("OpenEgg", {TimeOut = 3, RateLimit = 60, RateLimitTime = 3})

						local Result, Message = OpenEggFunction.Invoke(CurrentTarget.Value, Type)

That is due to the incorrect usage of LBConnection.InvokeCallBack
LBConnection.InvokeCallBack is a function and it takes a function as the argument

local OpenEggFunction = LBConnection.RemoteFunction("OpenEgg", {TimeOut = 3, RateLimit = 60, RateLimitTime = 3})
OpenEggFunction.InvokeCallBack(function(Player, EggName, Action)
	print(Player, EggName, Action)
	return EggHandler.OpenEgg(Player, EggName, Action)
end)
2 Likes

v2.1.0-beta

  • New functions were added, including LBConnection.RemoteEvent.Set, LBConnection.RemoteFunction.Set, and LBConnection.Bindable.Set
  • Remove the feature of packing byte string to binary format
  • Redundant types have been removed, and new types have been added
  • A timeout feature has been added for yielding on LB Objects
  • Implemented optimizations to improve the performance and efficiency of the code
  • Adding more tips
  • Adding Q & A section

The v2.2.0-beta will focus on optimization.

Thank you for this.

Iā€™ve been recently getting back into roblox development just as a side interest and it was rather disappointing how much custom work is necessary in order to work around the known issues with remotes, especially remote functions.

I was thinking about making my own custom solution that completely shoves remote functions off the table, but hey, you did the work for me!

This makes life easier.

Things Iā€™d like to mention:

  • It would be nice if we could have the ability to modify our remote folder location. I donā€™t like having to adjust my structure just because of one package.
  • Currently your GetNearPlayer function relies on a HumanoidRootPart to be present in the character model. This will break with custom characters that donā€™t have these. I suggest referencing Chr.PrimaryPart instead.
1 Like

It still uses normal remotes and bindables, so itā€™s not an alternative, like you can do this in the command bar if set in the server

image

First, please allow me to clarify that the term ā€œalternateā€ in this context refers to an alternative approach to using pure RemoteEvent, RemoteFunction, BindableEvent, and BindableFunction. Second, my implementation does not utilize any BindableEvent or BindableFunction objects.