Yes: Argon is reliable in most cases to sync, port instances to both studios and filtering.
No: As for right now, the chances of no is pretty much 5-10%. Argon is still in development stage, but the daily responses from the developer keeps it to a stable stage. As for right now, the bugs that may occur are syncing issues, porting issues or file checking issues from VSC to Roblox which causes the plugin to create extra folders.
But at the moment of v0.5.0 as the current version, I haven’t come across any issues. So, I will say it is 85% on an average that it is ready for production games as I’m getting the best possible services from Argon.
That’s because Argon was not tested in every scenario or is some edge cases. I’m not able to test these things alone, that’s why your feedback is so important! For now I think property syncing and two-way sync are most unreliable features.
So as long as Argon extension has flag “preview” (on VSC marketplace) you should not use that for game production!
not sure if this is reported or intended. my local scripts with children that are not scripts, frames etc, do not populate code in vscode when importing the roblox place to vscode.
I appreciate that this plugin is lightweight, is there any plans to integrate roblox LSP as well? I think the one thing stopping me from using this in production is that there’s no intellisense with the games directory and requiring modules in VS code. It’s unintuitive to develop with type any on modules
Nevermind what I said down below. I just don’t know how to use wally (just figured it out)
The past few updates has drastically changed my workflow speed and I just can’t express how fast I’ve done stuff without opening roblox studio and lagging. Though, it’s still missing a few things. Roblox LSP (okay, not gonna brag about that anymore), wally support etc. Wally support would be really epic. I do think it is hard, so it probably will take some time, but not going to push you on it. And yes, that was my suggestion
Btw, I’m also not sure if Argon already has this support so lemme know
For the past few days I was messing around with Roblox LSP’s source to integrate it with Argon. I found possible way of doing that but debugging this extension is nearly impossible because I can’ t print stuff to console.
So I decided to make some big changes to Argon itself. So first of all .argon.json will no longer be used. Instead data that has been stored in this file will now be stored in default.project.json, which is a Rojo file. So now by doing that almost every tooling that works on Rojo will work on Argon too.
Another change will be file naming. Instance names will no longer have classs inside it’s name. That’s necessary to make Roblox LSP and other tooling work with Argon. It will obviously break whole Argon project, tho to fix that you will simply have to port from Roblox again. Since Argon now supports properties, the class of an instance will be stored in the .properties.json file.
Last change will be 100% optional. It will be only required if you are interested in tooling. So the .source files will be named init and .properties files will be named meta. You will be able to change this setting inside VSC extension settings.
Probably the best idea (I think), because we have many-many packages which mostly follows the rojo formatting, so fixing it to work with Argon would be a pain. So, I probably like this idea of making it at least kind of similar to Rojo to make it support Roblox LSP and many other things. Good idea!
Nope. At the moment, it jumps to the very first line so you would have to go to that line manually unfortunately. You can go to the line either by scrolling (I don’t think I needed to remind you of that) or by opening up the command palette and replacing the > by : and then the line number (if the script’s too big).
Forgot to mention that in the update but unfortunately it’s not possible. That’s because LogService does not provide enough data - it only provides message, message type and timestamp.
If you know walkaround for that problem let me know and I will add this to Argon!
*In order to fix your project you have to delete literally everything from VSC and port from Roblox again.
**Currently .source files are not working, there is nothing I can do about it because my it requires to get my pull request merged. For now if you really need LSP support inside .source files you should enable “Compatibility Mode” inside Argon settings.
I think this is by far the best update for Argon, keep it up!
Bugs:
It… does not.
Porting folders with no children from VSC to roblox studio just keeps loading.
Edit: After some time it gave this error: Argon: HttpError: ConnectFail (ui4)
Edit2: I was connected but for some reason it disconnected, I connected again and it fixed it. Edit3: Okay, found out that when you try to port blank folders from VSC to roblox, it will load for some time and give a warning (stated above) and there will be a message in the status bar of VSC on the left saying something like: This extension closed unexpectedly or something like that and it disconnects. Also, you cannot open the argon quick pick menu while it is porting.
one thing, I notice that disabled scripts become enabled when sync from VS Code → Roblox
Haven’t read about what you are doing for properties, but is it possible there could be a separate way internally to store the state of a script being enabled or disabled?
