Argon is a simple two-way sync plugin for Roblox and extension for Visual Studio Code allowing developers not only sync code with ease, but any other instance as well with no need to re-generate project. It also provides tons of tools and quality of life improvements Argon is an alternative for Rojo not its replacement!
Iām not trying to be that one guy, but Iām not seeing anything that would make me use this over Rojo ā Rojo is meant for both small and large teams, using Luau (TS isnāt officially supported by Rojo and is compiled to Luau)
Onto my next point here ā How do you manage properties for instances? I know you were able to create them, but you showed nothing regarding their properties, nor does this seem to really have documentation. Another thing that may be relatively minor is configuration (in this context) ā people might like to call a folder āsrcā or āsourceā, etc, but it seems like youāre only able to use āgameā here. I feel like itās something that would annoy me. Additionally, what about unknown instances (Rojo ā$ignoreUnknownInstancesā I believe)? Will Argon delete them immediately, or is there an option for its configuration?
Thatās fine I mainly created this for myself and just wanted make it public in case someone else will find that useful.
Good point. I did not plan to add such a feature because I usually adjust properties in Studio. Tho now when I think about it itās a good idea and Iām gonna add this in the near future. It will probably be done vie .properties file inside instance.
Actually itās already an option but I did not create configuration file yet.
At this time they are just ignored.
Thank you very much for your valuable feedback really appreciate it!
I think this should be fixed, Iām not sure exactly how the plugin works, but if you stop the extension, delete an old file, and then restart it, would the old file still exist? If so, that would be an issue.
Overall though, this is a decent plugin. I think itās a pretty cool thing to make and a good tool to help you and others.
Anything you do wile Roblox plugin is not connected to VS Code extension is added to queue on both sides. If you disable plugin or extension completely nothing is done. So yeah probably that will be an issue which I will fix in the future. Now I will focus on two way sync and exposing options to user.
I suggest you focus on Roblox to VS Code
I tend to use roblox studio with output and click on the output and click on errors as its easier to get to them that way
and also rojo whenever I tried to use it, it deleted my remote event under the scripts
will this have the same problem?
The issue is you didnāt specify that thereād be a remote event under the script. Rojo has .meta files that you could use to solve that problem. (also remote events should typically be in replicatedstorage anyway)
I suggest scripts adding to pre existing instances; ex: if I have a model in replicatedstorage or workspace i can specify the path and insert a script in it
You can already do that. When you create new instance inside VS Code and it already exists inside Roblox is will just get reference to that instance.
So in your example you would have to create (in VS Code) folder named name.Model inside folder named Workspace or ReplicatedStorage and then just create script inside of this folder e.g. Script.server.lua.
On my previous post I was taking about Roblox to VS Code scenario.
One big plus for this is the āeasier-nessā of working with UI and not having to create lots of Rojo meta files. In my experience, working with UI can be somewhat annoying in Rojo, because Rojo isnāt great at having code nested in non-folder/non-service locations (itās possible to set it up, but it feels clunky). Alternatively, Iāve taken to āinjectingā the relevant UI code from one location into designated UI via code that has to be specifically called in other situations. All told, I donāt mind this approach, because it does give me some flexibility that I otherwise wouldnāt have had, but with something like Argonās approach, I wouldnāt have had to spend the time creating it in the first place.
