-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[0.1.x] Syntax that needs to be implemented #40
Comments
Adding :
|
Already added! Check the Already added as well in the default ExprElement file (currently in a PR but it will be merged soon).
Don't know about this. Vectors currently have no purpose since there is no connection with Minecraft (yet). I don't think this is necessary until we use integration with vector support.
Reversed strings are already supported, what do you mean with case text exactly? Take a look at ExprStringCases. Can be useful, will consider.
Already added to the list!
Currently supported as well.
IP of server would be pretty redundant currently as we don't use anything IP-related. The other expressions can be useful indeed. Welcome to the project. I love your enthusiasm, but maybe try to look inside the project first before proposing. I don't blame you though, since everything is currently not documented, so it's hard to see if something was added or not. |
I am creating this list for others to see which syntax should be implemented but isn't already. This is the syntax that's present in vanilla Skript, but not yet in the skript-parser project. All Minecraft-related syntax is obviously skipped.
Furthermore, I added a section for syntax that is not available in vanilla Skript, but could be useful to have in this project. All those syntaxes are subject-to-change and open for debate.
If you want to implement any of these syntaxes, just fork the project and make a pull request. You should always look at how Skript implements the given syntax, and then adapt it to this project. Note that almost every syntax in vanilla Skript is very old and unoptimised and that with the fantastic tools this project gives you, you can easily simplify the implementation.
Vanilla syntax
General
Dates
Strings
Lists
New syntax
General
Classes
parse as
expression possibleType<?>
is also possible)Time
Strings
Numbers
Future syntax
All the syntax below has no priority and should not be implemented unless the majority of above-defined syntaxes have been implemented. Discussion about these syntaxes below is appreciated and suggestions are welcome.
General
Colors
"Normal <blue>Blue!
. This would need some changes to how strings are parsed, but I have some ideas for this)Regex
Queue
If you have any suggestions or requests for changes, just leave a comment and I'll update this list as soon as possible. Everything, except the Vanilla syntax section, is very subject-to-change.
I hope this makes the current missing syntax elements clear as I wanted to list them here in favour of the recent road map that was created. This road map stated that it wanted to add all the missing syntax from Skript to this project in two months. We won't make the deadline (which is not a big deal), but at least new developers and contributors know how they can help this project out!
The text was updated successfully, but these errors were encountered: