Argon - Full featured tool for Roblox development

I will look into that after I finish my current goals. Tho I’m not sure if it will be possible because this extension utilizes VS Code API.

Getting

  18:34:32.648  The current identity (5) cannot set a Character's name (lacking permission 4)
  18:34:32.648  Stack Begin
  18:34:32.648  Script 'cloud_11263738833.Argon.Main.FileHandler', Line 30 - function parse
  18:34:32.648  Script 'cloud_11263738833.Argon.Main.FileHandler', Line 43 - function getChildren
  18:34:32.648   ▶ Script 'cloud_11263738833.Argon.Main.FileHandler', Line 41 - function getChildren (x3)
  18:34:32.649  Script 'cloud_11263738833.Argon.Main.FileHandler', Line 194 - function portInstances
  18:34:32.649  Script 'cloud_11263738833.Argon.Main.GuiHandler', Line 251 - function portToVS
  18:34:32.649  Stack End

This error when porting to VSC

2 Likes

I know what causes this problem I’m gonna fix that right now. Could you tell what is the name of this instance that causes that problem?

Alright just updated the Roblox plugin so please install latest version.

I really don’t see why we should use this over Rojo.

You lose out on a lot of tooling that makes Rojo worth it- the project.json files make a lot of tooling run. I believe that selene, wally, Luau LSP, Roblox LSP, roblox-ts, all require project.json files and meta.json files. Rojo also has CLI, which allows you to do things like build standalone Wally packages.

charlimitcharlimit

I don’t know what you mean by “It’s for small teams using Roblox’s Luau”. Rojo doesn’t make any assumptions or have any design based on how large a team is- you can use it solo completely fine. With 3-5 people it works completely fine. You lose so much tooling by not following Rojo’s format- and that tooling is the reason many want to use Rojo in the first place.

As per the second part- there’s almost no reasons to put code inside of instances anyway, as it gets extremely messy and screws with your achitecture. If you do though, as said, meta.json files exist for a reason- to let tooling like LSPs understand and give good intellisense. One of the pros for Rojo is that it forces you into this, which ensures better practices.

2 Likes

I was rather thinking about “working with ton of external frameworks, libraries”.

You still don’t get it. I don’t wanna use any externals tools. If you do then just use Rojo and that’s it.

As as mainly UI programmer I think it’s less messy to put code inside ScreenGui instance. If I’m wrong then I just prefer that way.

As I said in one of my previous posts I thing that meta files are extremally inconvenient, at lest for me. About the LSPs I have plans to fork/commit to this extension. So in the future I will be supported in Argon too. Actually only thing that does not work is module scripts detection. But when your are using extensions like Tabnine it not that big problem.

So to sum up if you want to use external tools/frameworks/libraries just use Rojo. Argon fucuses on simplicity. And as a reminder I created this for myself only reason why I shared it is because I know there may be some niche of people who will find Argon useful.

I don’t wanna compete with Rojo I want to create something different that focuses on different things.

6 Likes

Rojo has been really annoying for me (death to .meta)

and I would rather end up using something way more simple as I don’t want to have to figure out how to use .meta and instead just have it work and rojo was not designed for using ignore unknown instances everywhere

this will end up really useful for me as the most tooling I do is Roblox LSP and a roblox snippet plugin
thank you :slight_smile:

4 Likes

Bookmarked. Don’t worry about the naysayers, thanks for a great resource.

2 Likes

Rojo is a bit confusing and a lot of process to do, but this resource helps compact and make everything a lot simplier to use and more hassle free then Rojo. I like this resource because it’s more simple and good.

1 Like

This is an amazing resource and will help with simpler smaller projects. Keep up the good work!

1 Like

I’m trying to use argon on a game with a lot of fairly large scripts and I’m getting this message:
image
this doesn’t happen in my smaller games.

1 Like

Thanks for letting me know! I will look into that after I come home. Also could you take slightly bigger screenshot so I can see in which line does this issue happen?

1 Like

There is nothing else to show, that’s all it said. “Argon: Number of requests exceeded limit”

Alright I’m gonna figure out by my own then. I will add error ids which will help me identify problem easier.

1 Like

This happens to me whenever my game is larger and I have more scripts then usual.

Got it. I will be home in like 3 hours. The reason you are getting this error is because http request payload has limited json length. So I will change method that data is being transferred between Roblox and VSC.

EDIT: What’s your longest script? That could be a reason too.

I think i know the reason, and i had the same one when making my resource. http requests have a URI limit, Therefore warns whenever it hits.

Like 100-500, but I have a lot of modules and values being childrens of scripts