Yeah can do that. Do you have any ideas to make it look good tho?
Imo, maybe make the centered circle of the argon logo green when itâs connected.
(pls donât choose this color, itâs bad :< )
Or you could just make the entire logo green
Iâm not sure if Iâm a fan of changing the brand color, but I donât see a better way either.
How about when itâs connected the brand logo stays somewhat blurred and the github issue icon stays green which will be placed on top of the blurred brand logo.
This circle thing right here
What about simply updating the button name?
(or other emoji/symbol)
Actually you know what, didnât think of it. That looks nicer actually!
Emojis are unfortunately too big.
Iâm going to find other symbols to show other Argon statuses:
- changes to confirm
- error
- other warnings
char
Well thatâs unfortunate
â
ââłâ
(devforum completely destroyed the emojis :<<< )
Looks good! For warnings I will use this one: â
This error has been annoying me for quite a while now. I donât think it has anything to do with my file system but I have a folder called Types
.
WARN: Failed to execute code: [string "-- // Folder..."]:2: attempt to index nil with 'Types'
I guess you have require
s in your code which arenât supported. Argon simply runs the provided string using loadstring
.
This is still occurring for me, even after reinstalling, restarting PC, and forcefully removing the extension from the path you sent.
Bummer, because I was excited to try this outâŚ
(edit): Adding âopenMenuâ to the main,js exports still didnât fix the problem. I donât know if that code actually ran, though.
It was working all the time. This error comes up randomly and I canât reproduce it every time
More on this, it was my fault. I was running the wrong file.
Also another problem, after changing your code the Exec
method still runs the previous loadstring even though the code was updated in studio as well.
As I said itâs caused by the require
s. You canât import the same module twice in the same environment. To the see the changes you would have to reopen the place.
Just try it by ourself:
- Create a module
-
require
this module from the regular script - Update the module
Source
- See whether it changed from the regular script
Sorry for the late response but I totally missed your post.
Anyway, check if this solves your problem too:
Hmm⌠I saw in one of the images up there that Argon is in version 2.0.0+, but it will only let me install 1.7.3 or similar. So, should I run vscode as an admin or normally? I couldnât quite understand what he said.
Current minimum supported VS Code version is 1.87.0
. I will make it as low as possible in the new update as I think this is why some people couldnât update Argon in the first place.
OhâŚ
I was running as admin, so it did not update.
After restarting VSC, it shows that it has worked! It only works when you run VSC with admin, but running with admin makes it not update⌠lol.
I canât use Argon due to my organization of modules. It expects server modules to be directly in ServerScriptService, StarterPlayerScripts, and ReplicatedStorage. Theyâre under a âModulesâ folder in all of those services, so it cannot find them. Modifying the project json doesnât work either, and instead it finds a way to delete all my scripts when it syncsâŚ