Parsed as (Default Skript feature) not highlighting correctly

[LudwigBooysen]

When writing: set {_item} to "stone" parsed as an item

IntelliSkript highlights as red, while it is valid Skript code. So yes, this does still work, just gets annoying seeing red all over the place 😂.
Skript Documentation (Default code from Skript 2.0.0+): https://skripthub.net/docs/?id=901

[JohnHeikens]

Hi! Intelliskript doesn't recognize that line, as seen on the left of your screenshot. Do you have some other highlighting extension? When it doesn't recognize a line, that line stays uncovered so clearly something is mingling with it.

[NTMDev-2]

Uh, why not just do:
set {_item} to stone? Making stone a string then putting parsed as item is redundant I think in this case.

Also I think set is a little weird with stuff like this because it has so many different expressions / patterns that uses it.

[LudwigBooysen]

• I have tested disabling other highlighting extensions, and noticed the red highlight still stays. I noticed that Intelliskript mostly only highlights Skript related code, and not any other Skript extensions.
• Also the code provided was only an example, but that does not change the exact problem. This occurs in my code base, everywhere I parse anything or use any skript-refelct java functions.

I am not sure if this problem is even worth opening an issue about, just thought it's would be a nice feature to have.

Note, I don't have a problem with the code, it's only when you have a large code base with lots of parsing and other commands, it's not fun to see red highlights everywhere.

@NTMDev-2 I use parse for values I read from a .yml file, that needs to be parsed as entity types.

[NTMDev-2]

Oh okay. I think set just expects a simple value, and then having parsed as ... just confuses it and thinks two expressions are in one.

[LudwigBooysen]

Oh okay. I think set just expects a simple value, and then having parsed as ... just confuses it and thinks two expressions are in one.

@NTMDev-2 Is there a better way I can set Skript variables? I simply used this example from SkHub Docs, where they show set {var::*} to message parsed as "buying %items% for %money%": https://skripthub.net/docs/?id=901

[NTMDev-2]

Well, I think your way is the best for what you're using it for. I think its just the highlighter being dumb lol.