Need feedback & ideas for my remote framework

Help and Feedback Scripting Support
, ,
1

INTRODUCTION

Currently, I’m working on a new Remote Framework that works like a Restful API using expressJs as a basis for all of my design.

Right now, I’m collecting the community’s feedback to figure out the best way of implementing this project in a way that the end user can employ to make Server/Client Communication Development easier

< CODE SAMPLE >

-- i want To do Something close to this 
remote.setCookie(player)

remote.get( port , action ):andThen(callback(req,res)):catch(warn)

remote.send(port,action):andThen(data):catch(warn)

remote.sanity(port,optional Action):andThen(function(dataObject)
-- do Something
end)

WHY AM I SHARING THIS BEFORE FINISHING THIS FRAMEWORK ?

The fact of the matter is I want to design this framework for usability, simplicity, and extensibility.

To realize those goals I need to know the kind of problems you face when it comes time to making big or small games.

I want to know what you find to be tedious about the bare-bones Roblox remote client Framework.

I want to know what kind of solutions to specific problems you’ve had when it came to replicating and sending Data to preventing exploits and hence forth.

If it isn’t too much trouble, could you paste your answers like the format below :slight_smile: ?

Intro

Introduce your self here

My pain With remotes is

  • List them Off using bullet Points

My Ideas To Make your Framework Better

Explain in 8 sentences more or less
if you have a code example, go ahead and Post it like so below

Example Code

.. code here

Last but not least

My Opinion of this Idea Is?

Write your Opinion and your Thoughts Here

Watch The GitHub ?

GitHub Link: GitHub - DeathToTheStadium/RoExpress: An remote Based api the Uses expressjs like Framework to handle remotes

2 Likes
2

Intro

Hello, I’m DeathToTheStadium.

I’m a Scripter/web Developer,

I’ve been with Roblox for +9yrs & in those yrs I’ve been scripting on Roblox for +3yrs

My pain With remotes is

  • My first pain with using remotes is how tedious setting up can be, it takes just about 5 lines of code to instantiate a remote not including connecting the client to said remote as well
1. >local remote = instance.new('RemoteEvent')
2. >remote.Parent = replicatedStorage
3. >remote.Name = 'FireFoo'
4. >remote.OnServerEvent:connect(function(player,...)
5. >end)
  • My second pain is passing values back & forth through the remotes in a consistent, structured manner.
    I know this complaint makes me sound like I’m lazy because obviously that’s up to me, but I’m talking about when games get big to keep track of all those remotes can get ludicrously unmanageable sometimes and managing the data passed through them even more so

My Ideas To Make your Framework Better

If you can, pls reduce the amount of code needed to make new remotes and connect to them.

I like your idea of making remotes like ports, which means I can simply generate a new port for a new task or action. But id’e also like the ability to name my remote externally and then reference it in the code

Example Code

remote.getRemote(Name)

one more idea, if you can find a way to structure the data I send in a meaningful way that would be extremely helpful :slight_smile:

My Opinion of this Idea Is?

I think this resource could prove beneficial to beginners and seasoned devs as well

keep up the good work Me :slight_smile: