There should still be enough information to set up the plugin with the configuration that you want.
What features are you trying to set up?
There should still be enough information to set up the plugin with the configuration that you want.
What features are you trying to set up?
These are mostly dostring settings for the type of tags and attributes, and I also have a few other questions. Can I save these settings and use them in any script I want without writing dostring?
Like half the features and settings are missing.
Oh, by the way, I noticed that some of the screenshots had UI Plugin settings, can I enable them?
Everything important is documented, average user will only really mess with ancestors, prefix, sorting, and maybe tag groups. (Although I still think it should get updated to be accurate)
I donât really mess with docstrings but the image in the post should show how they work?
SC shouldnât have anything related to UI, do you have an example?
No. Everything is important. It should all be documented.
https://devforum-uploads.s3.dualstack.us-east-2.amazonaws.com/uploads/original/5X/7/2/c/4/72c488338ac29a18ab6ad908be9dae4826c9e577.png maybe the translator killed the context a bit. but I meant exactly what is shown in the screenshot.
in general, could you tell me about all the features of SC, I only know about dostring and !Players
Those were removed and replaced with commands, you interact with SimpleComplete fully from the command line.
Directive Autocomplete - for stuff like --!strict or --!native
Imports
Selection Imports
Docstrings
Anonymous Function Complete (QOL)
Table Function Completion (QOL)
Snippets
Script Linter - isnât fully finished but will warn for things like unused variables in the future
by the way, you havenât answered the question: âIs it possible to save these settings and use them in any script without having to write a dostring?â
What do you mean by that?
The settings in SimpleComplete save, but you have to write docstrings manually each script.
Yes. You can set global settings like this in the command bar:
--sc setglobal: SETTING_NAME; VALUE
is it global for the place or in general?
In general. If you want to save settings for a specific place, youâd need to use -- sc setlocal:
instead.
I do not know why the post was deleted. Okay, so I tried to fully explore, but I didnât understand what these functions do: @num_overloads #number, @kind #string, @preselect #bool, @learn_more #string, @override_docstring #string
To be honest, there are not enough examples, it is more difficult to understand exactly what the author wants in a dry text.
Its just modifiers for the autocompletion item, with @kind #string
if you say did this
--[[<doc>
@kind Event
]]
local hi = 10
hi| -- | is cursor
It would show you âhiâ with the icon for an Event next to the name (usually a purple lightning symbol)
Tags are the same but you dont need to pass a 2nd value, like @deprecated
Found a bug with string-requires.
Here I am trying to require the âCrimeâ ModuleScript in the âpacketsâ folder from the âWantedHandlerâ script, but this is what it tried importing:
As seen on the image, it knows what I want to import, it just falsely put in a âParentâ instead of â.â or ââŚâ.
Thanks for reporting this, unfortunately I am kinda out of time today to do any more stuff but Iâll fix this first thing tomorrow. I have a strong feeling i know why this is happening which is in the InstancePath parser for string requires
Alright, no problem. Take your time.